How to add a DMARC record

Publish a monitoring-only DMARC record with a report address, then work towards enforcement.

Last reviewed

Why it matters

Without DMARC, anyone can send mail showing the domain in the From line and receivers have no instruction for mail that fails SPF and DKIM. You also get no reports on who sends as you, and Gmail and Yahoo require DMARC from bulk senders.

How to fix it

Make sure SPF and DKIM are in place for each system that sends as the domain first: Google asks for at least 48 hours between those and DMARC.

Replace the highlighted values: example.com with your domain, dmarc-reports@example.com with a mailbox that receives DMARC reports, reports.example.net with the domain of that mailbox, when it is not your own.

Any DNS host

  1. Add one TXT record. Name: _dmarc (most DNS hosts add the domain themselves; entering _dmarc.example.com there creates _dmarc.example.com.example.com). Type: TXT. TTL: 3600. Value:
v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com

The address receives daily aggregate reports as XML attachments, often zipped. Use a dedicated mailbox or a DMARC reporting service, not someone's inbox.

  1. If that mailbox is on another domain (a reporting service, or your agency's domain), that domain must authorise the reports or receivers will not send them. Most reporting services already publish this for their customers; otherwise the owner of reports.example.net adds:
example.com._report._dmarc.reports.example.net.  3600  IN  TXT  "v=DMARC1;"
  1. Publish only one DMARC record. With two, receivers apply none.

  2. Read the reports, then move to enforcement: see the guide on moving DMARC from p=none.

Sources: RFC 9989 (DMARC), RFC 7489, Microsoft: configure DMARC, Gmail sender guidelines.

Cloudflare

Add the TXT record above under DNS > Records. Or, when Cloudflare is the DNS host, let DMARC Management create the record and collect the reports:

  1. Select the account and domain.
  2. Go to Email > DMARC Management and select Enable DMARC Management.
  3. After the scan, select Add if no record was found, or Next if one exists.

Cloudflare adds its own report address; you can keep yours beside it. Check the policy in the record before saving.

Sources: DMARC Management, enable DMARC Management.

Google Workspace

There is no DMARC setting in the Admin console: add the record at the DNS host as above. Google's suggested first record is the same p=none record with your report address. Turn on Workspace DKIM first, and make sure SPF includes _spf.google.com.

Sources: Set up DMARC, recommended rollout.

Microsoft 365

For a custom domain there is no portal setting: add the record at the DNS host as above, after SPF (include:spf.protection.outlook.com) and DKIM are set up. For the onmicrosoft.com domain, add it in the Microsoft 365 admin center under Settings > Domains > the domain > DNS records > Add record, with TXT name _dmarc. Microsoft recommends v=DMARC1; p=reject there if you never send from that domain.

Source: Microsoft: configure DMARC.

Check that it worked

dig TXT _dmarc.example.com +short
dig @1.1.1.1 TXT _dmarc.example.com +short

A brand-new name can stay cached as "no record" for up to the zone's negative TTL (the last number of dig SOA example.com +short). Then run the Owl Keeper Email authentication check again. The first reports usually arrive within a day or two.

Test it now with the free DMARC checker. No account needed.

What can go wrong

  • p=none changes nothing yet. Delivery is the same and spoofing is still possible until you enforce.
  • A report address that does not exist, or is not authorised, loses the reports silently, and with them the evidence you need to enforce safely.
  • A second _dmarc record, added later by someone setting up a reporting service, disables DMARC entirely.