Guide ·
From RFC 7489 to RFC 9989: what to change in your DMARC record
By: Kemal Özleyen, Cybersecurity Engineer · Check Point Workspace Security Expert · Kinetik Bilişim
RFC 9989 (May 2026) is the new DMARC standard and obsoletes RFC 7489. If your record has ri, rf or pct=100, delete them; if you are testing with pct=0, keep it and add t=y next to it. Close off non-existent subdomains with np.
Correction (): An earlier version suggested replacing pct=0 with t=y. That can lead receivers working to RFC 7489 to enforce the policy in full; the right form is to keep pct=0; t=y together during the transition.
What changed
RFC 9989 was published in May 2026 and obsoletes RFC 7489 and RFC 9091. RFC 7489 was an independently published Informational document; RFC 9989 is on the IETF Standards Track. Aggregate reports are now defined separately in RFC 9990 and per-message failure reports in RFC 9991.
The changes that matter to a record owner fall under four headings: three tags were removed (pct, ri, rf), three were added (t, np, psd), the organizational domain is now found by a DNS Tree Walk instead of the Public Suffix List, and the size-limit suffix on report addresses was removed.
pct is gone; t replaces it
According to Appendix A.6 of RFC 9989, the pct tag was only applied consistently at 0 and 100 in practice; values in between behaved differently from one receiver to the next. Its replacement, t, has two values: t=y corresponds to the old pct=0 and t=n (the default) to the old pct=100.
t=y has the policy applied one level lower: p=reject; t=y gets quarantine and p=quarantine; t=y gets none (§4.7). Reports are not affected.
During the transition some receivers still work to RFC 7489. RFC 7489 ignores tags it does not recognise and treats a missing pct as 100 (§6.3). So if you delete pct=0 and write only t=y, an older receiver enforces your policy in full. In RFC 7489 pct=0 also has the policy applied one level lower (§6.6.4); written together, pct=0; t=y makes both kinds of receiver do the same thing.
- If you have
pct=100: delete it. 100 was already the default; nothing changes. - If you have
pct=0: keep it and addt=ynext to it (p=quarantine; pct=0; t=y). When testing is over, remove both at once. - If you have
pct=1–99: there is no equivalent. Either apply the policy in full or test it one level lower withpct=0; t=y.
ri and rf are gone too
ri, which requested an aggregate report interval, and rf, which requested a failure report format, are not in RFC 9989’s list of tags (Appendix C.5.2); their status in the IANA registry is “historic” (§9.3). If they are in your record, you can delete them.
The size limit appended to a report address (as in rua=mailto:dmarc@example.com!10m) was also removed (Appendix C.4). Write the address without it.
New: np and psd
np sets the policy for subdomains that do not exist in DNS at all. If it is absent, sp applies, and if that is absent too, p (§4.7). Since no legitimate mail comes from a domain that does not exist, writing np=reject does not affect your legitimate mail even while your main policy is not yet reject.
psd is only for Public Suffix Operators (for example, the body that runs a top-level domain). You do not need it for your own domain; writing psd=n stops the DNS Tree Walk at that point and explicitly declares your domain an Organizational Domain (§4.10).
Organizational domain: the DNS Tree Walk
If a subdomain has no record, the receiver no longer consults the Public Suffix List to find which record applies. It shortens the name label by label from the left and looks for a _dmarc record at each step, with at most eight queries (§4.10).
During the transition a receiver working to RFC 7489 may arrive at a different organizational domain. RFC 9989 gives the remedy: publishing an explicit DMARC record for every domain you send from, together with strict alignment, avoids the issue entirely (Appendix C.3).
Before and after
Mailskop reads your record against RFC 9989: it strikes through removed tags and shows the defaults that apply even when not written.
Example: a record carrying RFC 7489-era tags:
_dmarc.ornek.com.tr TXT "v=DMARC1; p=quarantine; pct=100; ri=86400; rf=afrf; rua=mailto:dmarc@ornek.com.tr!10m"
The same record, aligned with RFC 9989:
_dmarc.ornek.com.tr TXT "v=DMARC1; p=quarantine; np=reject; rua=mailto:dmarc@ornek.com.tr"
Frequently asked
Is it a problem if pct=100 stays in my record?
pct=100 stays in my record?It does not change behaviour: 100 was the old default and RFC 9989 no longer defines the tag. Deleting it simply tidies the record.
Do I need to wait for receivers to adopt RFC 9989?
No, with one exception. Deleting ri, rf and pct=100 and adding np changes nothing for a receiver still working to RFC 7489. Deleting pct=0 or pct=1–99, however, means an older receiver enforces the policy in full; while testing continues, keep pct=0; t=y together.
Related terms
Other guides
- DMARC from
p=nonetop=reject, step by step - The SPF 10 DNS lookup limit: why it is exceeded and how to fix it
- Setting up SPF, DKIM and DMARC for Microsoft 365
- Setting up SPF, DKIM and DMARC for Google Workspace
- Gmail, Yahoo and Outlook bulk sender requirements
- Email header analyzer comparison: Mailskop, MxToolbox, Microsoft and Google
- Where was an email sent from? Tracing its route and IP location from the header
- Measurement: Email security measurement, September 2026: DMARC, SPF and DKIM across 21,197 domains
Last updated: