# DMARC has no policy

Your DMARC record has no policy: the `p=` tag that tells receivers what to do with mail that fails is missing, or it's there with nothing after the `=`. Write one in, and every receiver reads your record the same way.

Until you do, receivers follow [RFC 9989 section 4.10.1](https://www.rfc-editor.org/rfc/rfc9989.html#section-4.10.1), and the result depends on the rest of the record:

- **With a valid report address** in `rua=`, receivers act as if the record said `p=none`. They send reports and refuse nothing from your domain itself. An `sp=` or `np=` tag in the record may still apply to subdomains, but a receiver that reads an empty `p=` as an invalid value drops them too. The result marks this "Watch".
- **Without one**, receivers apply no DMARC to your mail at all, as if the record weren't there. The result marks this "Fix".

A valid report address is a full address with its scheme, such as `rua=mailto:dmarc-reports@example.com`. A bare email address without `mailto:` doesn't count, and `mailto:` is the one kind every receiver supports.

Another mistake in the same record, such as a tag written twice, can make it unusable even with a report address. The result then marks it "Fix" too. Correct that mistake when you add `p=`; [Receivers ignore your DMARC record](/docs/findings/dmarc-record-ignored/) lists them.

## Add the policy

1. Read the record: open **Details →** on your result, or run `dig +short TXT _dmarc.example.com` with your domain in place of `example.com`.
2. If the record has `sp=` or `np=` set to `quarantine` or `reject`, check your subdomains' mail before you change anything: once `p=` is valid, every receiver applies those policies, and mail from a subdomain that fails is held or refused.
3. At your DNS provider, edit the TXT record at `_dmarc.` in front of the domain you checked. Many DNS providers want only the part before your main domain: `_dmarc` for `example.com`, `_dmarc.mail` for `mail.example.com`. Give the record `p=none`: if it has an empty `p=`, fill that one in; if it has none, add `p=none;` after `v=DMARC1;`. Never write a second `p=`: a tag written twice makes receivers [ignore the whole record](/docs/findings/dmarc-record-ignored/). If you couldn't confirm your subdomains' mail in step 2, change `sp=` and `np=` to `none` in the same edit. Save the record.
4. Make sure `rua=` holds a `mailto:` address that receives reports.
5. Once the reports show your services pass, and you've confirmed the ones that send rarely, change `p=none` to `p=quarantine`, then to `p=reject`.

## The text you'll see

On the result:

```
DMARC has no policy
Without a policy, receivers decide for themselves what to do with mail pretending to be you.
```

The check's JSON, at `/api/v1/check?domain=example.com`, names the case in its message, for example:

```
DMARC record has no p= policy tag and no valid rua= address, so receivers apply no DMARC policy.
```

For bulk senders, Gmail treats a record without a policy like no record ([Gmail SMTP errors](https://knowledge.workspace.google.com/admin/support/troubleshooting/gmail-smtp-errors-and-codes), updated 10 Nov 2026):

```
550 5.7.40 Your message was blocked because the sending domain doesn't have a DMARC record or the DMARC record doesn't specify a DMARC policy.
```
