Email Auth Check › Guides

How to set up DMARC (step by step)

DMARC tells receiving mail servers what to do with mail that claims to be from your domain but fails SPF and DKIM alignment, and where to send reports about it.

Set up DMARC

  1. Make sure SPF and DKIM pass. DMARC builds on them. Each service that sends as your domain needs to pass SPF or DKIM with an aligned domain.
  2. Publish a p=none record. Add a TXT record at _dmarc.yourdomain.com with v=DMARC1; p=none; and a rua address for aggregate reports.
  3. Read reports for 2–4 weeks. Find every legitimate source sending as your domain and fix any that fail.
  4. Tighten the policy. Move to p=quarantine (optionally with pct=25 at first), then to p=reject.

A safe starting record

TypeHost / NameValue
TXT_dmarcv=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com

p=none changes nothing about delivery; it just turns on reporting. Once reports show all your legitimate senders passing, move to p=quarantine, then p=reject.

Is DMARC required?

Since February 2024, Google and Yahoo require bulk senders (roughly 5,000+ messages a day to their users) to publish DMARC, at minimum p=none, along with SPF and DKIM. Microsoft announced similar requirements for Outlook.com in 2025. Smaller senders aren’t strictly required to, but it still improves deliverability and blocks spoofing.

See exactly what your domain’s SPF, DKIM and DMARC look like, free.

Check my domain

Frequently asked questions

Where do DMARC reports go?

To the address in rua=. Reports are XML files, so most people use a free or paid DMARC report reader. If the address is on another domain, that domain must publish an authorization record.

Will p=reject block my own email?

Only mail that fails both SPF and DKIM alignment. That’s why you start with p=none and check the reports first.

More guides