What does my DMARC record tell receivers to do?
DMARC says what receivers should do with mail that fails SPF and DKIM alignment, and where to send reports. We check it the way RFC 9989 (May 2026) says receivers must: by walking up the DNS tree, not with the Public Suffix List.
What RFC 9989 changed
- Receivers find the policy and the organizational domain with the DNS tree walk (§4.10) instead of the Public Suffix List.
- The pct= tag is gone (Appendix A.6). Its useful value, pct=0, became t=y: “testing, apply one level less”.
- New np= sets a policy for subdomains that don’t exist, a favourite of spoofers.
- New psd= lets registries mark public suffixes; domain owners can use psd=n to pin their organizational domain.
- A record with no valid p= but a valid rua= is treated as p=none, so reporting still works.
Start safely
Begin with p=none and a rua address you read. Watch the daily reports for a few weeks, fix any service that fails alignment, then step to p=quarantine with t=y, then quarantine, then reject.
Sources
- RFC 9989: DMARC (Standards Track, May 2026) · checked 5 Oct 2026
- RFC 9990: DMARC aggregate reporting, §4 external destinations · checked 5 Oct 2026
- Google: Email sender guidelines (5,000 a day rule) · checked 5 Oct 2026
Related tools
Domain Health Report Everything at once, graded, with the fixSPF checker Include tree and the 10-lookup limitDKIM checker Common selectors or yoursMTA-STS and TLS-RPT Policy file and reportsDMARC report reader Parsed in your browserDNS lookup Any record, with TTLs explainedWHOIS / RDAP Registrar, expiry, status codes