DMARC (Domain-based Message Authentication, Reporting and Conformance) lets the owner of a domain publish a policy for mail that uses that domain in its From address. The policy tells receiving servers how to treat mail that fails authentication and where to send reports about it. DMARC builds on SPF and DKIM and adds the check they lack: whether the authenticated domain matches the domain the reader sees.
RFC 9989, published in May 2026, is the current DMARC specification. It replaces RFC 7489 and moves DMARC onto the IETF standards track.
How DMARC Works
The Pass Rule
A message passes DMARC when at least one of these is true:
- SPF passes and aligns: The return-path domain passed SPF and aligns with the From domain.
- DKIM passes and aligns: A DKIM signature is valid and its
d=domain aligns with the From domain.
Alignment
- Relaxed (the default): The two domains share the same organizational domain.
em.example.comaligns withexample.com. - Strict: The two domains are identical.
The aspf= and adkim= tags choose the mode for SPF and DKIM. DKIM alignment is usually the one that holds when a sending service owns the return path.
Finding the Policy
The receiver looks for a TXT record at _dmarc. plus the From domain. If none exists, it walks up to the parent domains. A host with more than one DMARC record has no valid policy, so publish exactly one.
DMARC Record Syntax
_dmarc.example.com. IN TXT "v=DMARC1; p=none; rua=mailto:[email protected]"
Common Tags
- v=DMARC1: Required, and must come first.
- p=: The policy for the domain:
none(monitor only),quarantine(treat as suspicious, usually the spam folder) orreject(refuse the message). - sp=: The policy for subdomains, if it differs from
p=. - np=: The policy for subdomains that do not exist in DNS. RFC 9989 adds this tag.
- rua=: The address that receives daily aggregate reports.
- adkim= / aspf=:
rfor relaxed orsfor strict alignment. - t=y: Marks the policy as in testing. RFC 9989 adds it and retires the older
pct=tag.
Rolling Out a DMARC Policy
- Start at p=none: Publish a record with a report address. Nothing changes for delivery, and you start to receive aggregate reports.
- Read the reports: Find every service that sends as your domain. Fix SPF or DKIM for the legitimate ones.
- Move to quarantine: Once legitimate mail passes, change the policy to
p=quarantine. - Move to reject: When quarantine causes no losses, change to
p=reject.
Build the record with the DMARC record generator. A domain that never sends mail can publish p=reject from the start.
DMARC and Bulk Sender Rules
Gmail, Yahoo and Microsoft all require bulk senders to publish DMARC with at least p=none, and to align the From domain with SPF or DKIM. Gmail and Microsoft apply the rule at about 5,000 messages a day. Microsoft rejects non-compliant mail with 550 5.7.515 (Gmail sender guidelines, Outlook.com 550 5.7.515). A policy of quarantine or reject is also a requirement for BIMI.
DMARC for an ESP’s Customers
DMARC is judged on the customer’s From domain, not on the ESP’s domain. Each customer publishes its own record or a CNAME to a record the ESP hosts, and the ESP signs each customer’s mail with DKIM on that customer’s domain so it aligns. The sender domain authentication guide covers both options. For how DMARC relates to the other two standards, read SPF vs DKIM vs DMARC, and test SPF and DKIM with the SPF and DKIM checker.
DMARC turns SPF and DKIM results into a policy the receiver can act on, and gives the domain owner reports on who sends as their domain. Start at p=none, use the reports to fix every legitimate sender, then move to enforcement.