Back to feed
Dev.to
Dev.to
7/6/2026
DMARC Just Got 3 New RFCs. Your DNS Record Doesn't Need to Change.

DMARC Just Got 3 New RFCs. Your DNS Record Doesn't Need to Change.

Short summary

DMARC's specification has been formally updated and split from RFC 7489 into three separate Standards Track RFCs (9989, 9990, 9991), covering core policy, aggregate reporting, and failure reporting respectively. Existing DMARC records remain fully compliant with zero syntax changes required. If you're still using p=none, this is a good opportunity to review aggregate reports and move toward quarantine or reject enforcement.

  • •DMARC split from RFC 7489 into three new Standards Track RFCs (9989, 9990, 9991)
  • •No changes needed to existing DMARC records — syntax remains unchanged
  • •Consider moving from p=none to p=quarantine/reject if you haven't already

Generated with AI, which can make mistakes.

Read full article at Dev.to

Is this a good recommendation for you?

Comments

Failed to load comments. Please try again.

Explore more

The Hidden Dangers of DMARC p=none: Why It's Undermining Your Email Security (Not Just Deliverability)
Dev.to
How to Configure DMARC Forensic Reports (RUF): A Technical Step-by-Step Guide for Postmaster Debugging
Dev.to
The original title is 10 words: "The DMARC enforcement gap: 64.6% publish it, only 22.7% enforce it"
Dev.to
The original headline is about DMARC p=reject not being sufficient for email deliverability, and mentions what else is needed.
Dev.to