DMARC Email Authentication Explainer
DMARC—Domain-based Message Authentication, Reporting, and Conformance—is a system that helps a domain owner limit fraudulent email that claims to come from that domain. A receiving mail service checks whether a message passes Sender Policy Framework, known as SPF, or DomainKeys Identified Mail, known as DKIM. DMARC then asks whether the domain authenticated by at least one successful method aligns with the domain visible to a reader in the message’s From field. If either SPF or DKIM both passes and aligns, the message can pass DMARC. This connection to the visible From domain is what turns two lower-level authentication methods into a practical anti-spoofing policy.
The domain owner publishes a DMARC record in the Domain Name System at a designated name beneath the domain. The record can request a policy of none, quarantine, or reject for messages that fail DMARC. None is primarily a monitoring policy: receivers still evaluate the message and can send reports, but the DMARC record does not request special handling solely because of failure. Quarantine asks participating receivers to treat failing mail as suspicious, while reject asks them not to accept it. The current IETF specification, RFC 9989, published in 2026, replaced the original 2015 DMARC document while preserving this central policy-and-reporting model.
SPF and DKIM contribute different evidence. SPF checks whether the server that delivered the message was authorized for a domain used during SMTP delivery. Forwarding can break that relationship because the forwarding server becomes the apparent sender. DKIM places a cryptographic signature in the message, allowing a receiver to verify selected headers and body content with a public key published in DNS. Mailing-list footers or other changes can break a signature. DMARC does not require both methods to survive; one successful, aligned result is enough. Alignment matters because an attacker could otherwise authenticate a domain they control while placing someone else’s domain in the visible From field.
Reporting makes DMARC useful as an operational tool rather than only an enforcement switch. Domain owners can request aggregate reports that summarize which sources sent mail using their domain and how SPF, DKIM, alignment, and policy evaluation turned out. Those reports help identify legitimate services, forgotten systems, configuration errors, and suspicious traffic. A cautious rollout usually begins with monitoring, fixes authentication and alignment for every approved sender, and then moves toward quarantine or reject. Publishing a strict policy before understanding all mail streams can block invoices, newsletters, support systems, or messages sent by third-party platforms.
DMARC is not a verdict that an individual message is safe. A phisher can use a newly registered domain and authenticate it correctly, a legitimate account can be compromised, and harmful content can arrive from infrastructure that passes every technical check. Receivers therefore combine DMARC with reputation, content analysis, user reports, and other defenses. Indirect mail creates additional complications: forwarders and mailing lists may change the path or content in ways that disrupt SPF or DKIM. Techniques such as careful DKIM signing and Authenticated Received Chain can preserve more evidence, but they do not eliminate the need for receiver judgment.
For ordinary readers, DMARC’s value is mostly invisible: it makes simple impersonation of a protected domain harder and gives receivers clearer instructions when authentication fails. For domain owners, the difficult part is inventory and maintenance. Every service that sends mail must be known, authenticated, aligned, and monitored as vendors and infrastructure change. The policy lives in DNS, but successful protection depends on mail-server configuration, key rotation, reporting review, and gradual enforcement. Used with SPF and DKIM, DMARC narrows a common avenue for domain spoofing; used alone or deployed carelessly, it cannot guarantee trustworthy mail and can interfere with legitimate delivery.
A message passes when SPF or DKIM succeeds and the authenticated domain aligns with the domain shown in the visible From field. Both methods do not have to pass.
Alignment prevents a sender from authenticating an unrelated domain while impersonating a different one in the address readers see.
A policy of none supports monitoring. Quarantine asks receivers to treat failing mail as suspicious, and reject asks them not to accept it.
Receivers still make their own delivery and security decisions, so the policy is a strong signal rather than a complete spam filter.
Aggregate reports reveal which services send mail using the domain and whether their authentication aligns correctly.
Monitoring first lets an organization fix approved senders before stronger enforcement accidentally blocks legitimate messages.
Explore more "Explainers"
Discover additional explainers across politics, science, business, technology, and other fields. Each explainer breaks down a complex idea into clear, everyday language—helping you better understand how major concepts, systems, and debates shape the world around us.
