TL;DR: DMARCbis puts DMARC, aggregate reporting and failure reporting onto the IETF Standards Track, with Red Sift pointing to clearer policy semantics and reporting rules. Email authentication now needs a plan for retiring monitoring mode and partial enforcement instead of treating them as permanent states.
Editorial analysis by NHI Mgmt Group, based on content published by Red Sift: “DMARCbis is now an IETF Proposed Standard: What that means today”.
By the numbers:
- In May 2026, the IETF published RFC 9989, the updated DMARC specification.
- RFC 9990 defines aggregate reporting as a standard, including XML schema and delivery requirements.
- RFC 9991 covers failure reporting as near-real-time, per-message reports for DMARC failures.
Key questions
Q: Why does removing partial DMARC enforcement matter for email security teams?
A: Partial enforcement creates uneven protection because some failing mail is still allowed through, which leaves room for inconsistent receiver behaviour and long-lived exceptions.
Q: How can security teams use DMARC reporting to diagnose authentication failures?
A: Use aggregate reports to spot trends in sending sources, alignment failures and policy changes over time, then use failure reports for message-level troubleshooting when a specific failure needs diagnosis.
A: Start by inventorying every authorised sender, including marketing, support, and transactional platforms, then validate SPF and DKIM for each one.
Practitioner guidance
- Audit long-lived pct usage Identify any DMARC records still relying on pct as more than a short transition mechanism, then plan a move to full policy enforcement.
- Revisit indefinite p=none monitoring Confirm whether monitoring mode is still justified, and if not, establish a path to rejection or quarantine with clear ownership.
- Validate reporting pipelines against the new RFC split Check that your tooling and processes can consume aggregate and failure reporting as separate operational inputs, not one blended feed.
Bottom line: DMARCbis tightens email authentication governance by making policy semantics and reporting more explicit across the ecosystem.
Glossary terms: DMARC, Aggregate Report, Failure Reporting, Public Suffix Domain
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
DMARCbis closes an authentication governance gap, not just a technical one. The article shows that the original DMARC model left enough room for different receiver interpretations that policy enforcement could vary in practice. That is a governance problem as much as a protocol problem because identity assurance depends on consistent receiver behaviour across the ecosystem. Practitioners should treat the update as a signal to standardise policy meaning, not merely to reformat records.
A question worth separating out:
Q: What changes when public suffix domains are handled through DNS rather than a maintained list?
A: DNS-based handling reduces dependence on a manually updated list and makes public suffix identification part of the live domain structure. That improves consistency across receivers, but it also means teams must recheck how organisational domains and subdomain inheritance are interpreted. The practical issue is scope accuracy, not just parsing logic.
👉 Read our full editorial: DMARCbis changes enforcement, reporting and testing for email