The DMARC you deployed is obsolete. Meet RFC 9989.
In May 2026, the IETF published RFC 9989, 9990 and 9991: the specification the industry spent years calling DMARCbis. Together they replace RFC 7489 and, for the first time in DMARC’s eleven-year life, make it a real Standards Track protocol. Your record probably still works. Your assumptions might not.
One RFC becomes three
The old specification crammed policy, discovery and two reporting formats into one document. The new set splits the protocol along its natural seams:
RFC 9989the core protocolPolicy publication, alignment, policy discovery, and enforcement. This is the document that obsoletes RFC 7489. It also absorbs RFC 9091’s psd= extension, so PSD DMARC is no longer a bolt-on.
RFC 9990aggregate reportingThe daily XML feedback loop gets its own specification, with an updated schema that adds optional fields such as discovery_method and generator, so reports can say how a verdict was reached, not just what it was.
RFC 9991failure reportingPer-message failure (forensic) reports, separated so their privacy trade-offs can evolve independently of the core protocol.
What actually changed
The DNS Tree Walk replaces the Public Suffix List
RFC 7489 depended on the browser-world Public Suffix List to find a domain’s organizational domain. RFC 9989 replaces it with the Tree Walk: receivers walk up the DNS hierarchy itself to discover policy. Discovery now lives entirely in DNS, where DMARC lives, instead of in a text file maintained for a different purpose.
pct=, rf= and ri= are deprecated
Percentage-based rollout never worked reliably in practice, so it’s gone. Remove these tags at your next DNS edit. Receivers will simply ignore them. Testing intent is now expressed explicitly with the new t= tag, and subdomain-tree policy gains np= for non-existent subdomains.
Honest guidance on indirect mail flows
The new core spec is candid about DMARC’s oldest wound: forwarding and mailing lists still break alignment. It now explicitly discourages p=reject for domains whose users post to mailing lists, unless the organisation has measured the risk and put controls in place.
A real conformance section
For the first time, the spec defines what full participation means for domain owners and receivers alike: clearer definitions, better examples, and one canonical answer where vendors used to improvise. Fewer ambiguities mean fewer mysterious rows in your aggregate reports.
DMARC finally carries the weight everyone assumed it had
For eleven years the entire ecosystem (mailbox providers, compliance frameworks, bulk-sender mandates) was built on an Informational document with no standards authority behind it. RFC 9989 moves DMARC to Proposed Standard: interoperability disputes are now settled by IETF consensus, the text has an accountable working group behind it, and "compliant with the DMARC standard" is finally a precise, testable claim. What the industry treated as law is now actually law.
What you should do
- Don’t panic: your record stays valid.
v=DMARC1is unchanged, andp=,rua=,adkim=/aspf=andfo=all keep their meaning. There is no "DMARC2" version bump. - Clean out deprecated tags. Drop
pct=,rf=andri=at your next DNS edit. Adoptnp=ort=only where they solve a real policy problem. - Re-check organizational-domain assumptions. If your domain architecture relied on PSL quirks (private-section entries, unusual delegation boundaries), verify the Tree Walk reaches the same organizational domain before receivers converge on it.
- Let the data lead, as always. Adoption is early. Receivers will migrate gradually. Watch your aggregate reports before and while tightening enforcement. That is exactly the workflow DMARC was designed around.
ClearDMARC parses both report generations side by side and flags deprecated tags in your record, so the RFC 7489 → 9989 transition shows up as recommendations in your dashboard, not surprises in your mail flow.
- RFC 9989: DMARC core protocol (Proposed Standard, May 2026). Obsoletes RFC 7489, incorporates RFC 9091.
- RFC 9990: DMARC Aggregate Reporting (Proposed Standard, May 2026).
- RFC 9991: DMARC Failure Reporting (Proposed Standard, May 2026).
- RFC 7489: DMARC (Informational, 2015), obsoleted.