# No DMARC policy

The domain you checked has no DMARC record. Anyone can send mail that shows your domain as the sender, receivers have no policy of yours to apply, and nobody sends you reports about it.

Checked a subdomain, such as `mail.example.com`? Read [On a subdomain](/docs/findings/dmarc-missing/#on-a-subdomain) first: its parent's policy may already cover it, and a new record would replace that policy.

DMARC is one TXT record at `_dmarc.` in front of your domain, such as `_dmarc.example.com`. The check asked your domain's own nameservers for that name and found no record starting `v=DMARC1`. The value `DMARC1` is case-sensitive, so a record starting `v=dmarc1` doesn't count; spaces around the `=` and a capital `V` do no harm.

Gmail and Yahoo require a DMARC record from bulk senders, and Outlook.com from domains that send more than 5,000 messages a day. For that part of their rules, a record at `p=none` is enough. Their other rules, SPF and DKIM passing for your domain, still apply.

## Look it up

**Details →** on your result shows what the check found. To look it up yourself, put your own domain in place of `example.com`:

```
dig +short TXT _dmarc.example.com
```

On Windows, run `nslookup -type=TXT _dmarc.example.com`. No line containing `v=DMARC1` means no record.

## Publish one

1. At your DNS provider, add a TXT record named `_dmarc.` followed by the domain you checked, such as `_dmarc.example.com`. Many DNS providers want only the part before your main domain: `_dmarc` for `example.com`, `_dmarc.mail` for `mail.example.com`. Give it the value `v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com`, using an address of yours that can receive reports.
2. Read the reports for a few weeks and fix any service of yours that fails.
3. Confirm the services the reports may miss, such as one that sends once a month.
4. Change `p=none` to `p=quarantine`, then to `p=reject`.

[Connect DMARC reports](/docs/connect-reports/) shows how to send the reports to MailGlo, which lists each service that sends as you and whether it passes.

## On a subdomain

A subdomain such as `mail.example.com` with no record of its own follows its parent's policy. The result names the parent and says which case applies:

```
No DMARC record of its own
Receivers apply the policy example.com publishes for its subdomains: reject.
```

This one needs nothing from you when the policy it names is `quarantine` or `reject`. If it names `none`, open the parent's result: its record says `sp=none`, or it says `p=none` and lacks `sp=`, or it has a mistake in `p=`, `sp=` or `np=` that the parent's result names. Before you change any of these, check that mail from the parent domain and from your subdomains passes: a corrected or raised value takes effect at once, for the parent's own mail too. If you can't check yet, correct a mistake with every policy at `none` (`p=none`, `sp=none`, `np=none`). Once the mail passes, raise `sp=` to `quarantine`, then `reject`, to protect subdomains.

In every case, don't add a record to the subdomain: a record there replaces the parent's policy for it, and a new `p=none` record would switch protection off.

```
No DMARC policy here or at example.com
```

Neither has a record. Publish one at the parent, `example.com`, as in the steps above. It covers the subdomain too.

```
No DMARC record of its own
If example.com publishes a DMARC policy, receivers apply it here. This check couldn't read it.
```

The check couldn't read the parent's record. Open the result for the parent, which says what went wrong, before adding anything here.

```
No usable DMARC policy here or at example.com
```

The parent has a record receivers can't use. Correct the parent's record; the result for the parent names the mistake.

## Bounces you may see

On a result for the domain itself:

```
No DMARC policy
Anyone can send mail that looks like yours, and you get no reports about it.
```

Gmail, refusing bulk mail ([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. Gmail requires all bulk email senders to add a DMARC record to their sending domain.
```

The same page gives `421 4.7.40` when Gmail delays the mail instead. Google's [FAQ for email senders](https://support.google.com/mail/answer/14229414) (read 14 Nov 2026) gives `4.7.31` for that case.

Outlook.com, for domains that send more than 5,000 messages a day ([Microsoft, 30 Apr 2025](https://techcommunity.microsoft.com/blog/microsoftthreatprotectionblog/strengthening-email-ecosystem-outlook%E2%80%99s-new-requirements-for-high%E2%80%90volume-senders/4399730)):

```
550; 5.7.515 Access denied, sending domain [SendingDomain] does not meet the required authentication level.
```

From 5 to 9 November 2026, Outlook.com also refused mail from small senders with no DMARC record:

```
550 5.7.1 Message rejected: Message lacks SPF/DKIM/DMARC Auth Records (AS9031519)
```

Mail administrators reported it, and Microsoft rolled it back on 9 November ([MailRoute, 6 Nov 2026, updated 10 Nov](https://mailroute.net/blog/outlook-rejecting-email-without-dmarc)). Microsoft has published no such rule for small senders.
