DMARC 1019 min read · Updated Jun 2026

RFC 7489: the DMARC specification, explained

DMARC is defined in RFC 7489, published in March 2015. This guide walks through what the specification actually says, in plain language, and what each part means for your setup.

What RFC 7489 is

RFC 7489, titled "Domain-based Message Authentication, Reporting, and Conformance (DMARC)," is an Informational document published by the Internet Engineering Task Force (IETF). It builds directly on two existing standards, SPF (RFC 7208) and DKIM (RFC 6376), and defines how a domain owner declares a policy, how receivers apply it, and how they report results back.

At a glance

RFC 7489 does not invent new authentication. It defines a policy and reporting layer on top of SPF and DKIM: the piece that decides what happens when authentication fails, and that gives domain owners visibility into who sends as them.

The three core concepts

  • Identifier alignment (§3.1): the heart of DMARC. The domain authenticated by SPF or DKIM must align with the domain in the visible From: header. Without this requirement, an attacker could pass authentication for their own domain while spoofing yours.
  • Policy (§6.3): the domain owner publishes a TXT record at _dmarc.example.com declaring how receivers should treat unaligned mail.
  • Reporting (§7): receivers send aggregate (RUA) and optionally forensic (RUF) reports back to the addresses the domain owner specifies.

The DMARC record, tag by tag

_dmarc.xmpl.example TXT
v=DMARC1; p=reject; rua=mailto:reports@xmpl.example; pct=100; adkim=s; aspf=r; fo=1
TagMeaning (RFC 7489 §6.3)
vVersion: must be DMARC1 and appear first. Required.
pPolicy: none, quarantine or reject. Required.
spSubdomain policy: overrides p for subdomains. Optional.
ruaAddress(es) for aggregate reports. Optional but essential.
rufAddress(es) for forensic/failure reports. Optional.
pctPercentage of failing mail the policy applies to. Useful for staged rollout.
adkimDKIM alignment mode: r (relaxed, default) or s (strict).
aspfSPF alignment mode: r (relaxed, default) or s (strict).

How a receiver evaluates DMARC

Per §6.6, a conforming receiver follows this sequence for every inbound message:

  1. Extract the domain from the From: header.
  2. Look up the DMARC record for that domain (or its organisational domain).
  3. Evaluate SPF and DKIM, then check alignment for each.
  4. DMARC passes if either SPF or DKIM passes and aligns.
  5. If neither aligns, apply the published policy (none/quarantine/reject) and record the result for the aggregate report.

The organisational domain concept

RFC 7489 §3.2 introduces the organisational domain (derived using the Public Suffix List) so that relaxed alignment can treat mail.xmpl.example and xmpl.example as the same entity. This is also how a receiver finds a policy for a subdomain that has no DMARC record of its own.

What RFC 7489 does not cover

It is worth knowing the boundaries. RFC 7489 does not address the mailing-list forwarding problem (later tackled by ARC, RFC 8617), does not mandate key rotation intervals, and leaves ruf forensic reporting largely optional, which is why most receivers send aggregate reports but not forensic ones.

How ClearDMARC implements the spec

ClearDMARC parses the RUA aggregate XML defined in §7.2 of the specification, validates your published record against every tag above, and models alignment exactly as §3.1 describes, so the readiness signals you see map directly to how real receivers will treat your mail.

You can read the full specification at rfc-editor.org/rfc/rfc7489.

Was this guide helpful?