RFC 9991: Domain-Based Message Authentication, Reporting, and Conformance (DMARC) Failure Reporting
In plain English — editorial summary, not part of the RFC
Domain-based Message Authentication, Reporting, and Conformance (DMARC) is a mechanism by which a Domain Owner can request feedback about email messages using their domain in the From: address field. This document describes "failure reports", or "failed message reports", which provide details about individual messages that failed to authenticate according to the DMARC mechanism. This document updates RFC 6591 and obsoletes RFC 7489.
Document record
- Document ID
- RFC9991
- Published
- May 2026
- Authors
- S. Jones; A. Vesely
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 13
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 5 RFCs, each formally replacing the one before it.
- RFC 7489 (2015)
- RFC 9091 (2021)
- RFC 9989 (2026)
- RFC 9990 (2026)
- RFC 9991 (2026)
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8617The Authenticated Received Chain (ARC) ProtocolCurrent
July 2019
- RFC 7960Interoperability Issues between Domain-based Message Authentication, Reporting, and Conformance (DMARC) and Indirect Email FlowsCurrent
September 2016
- RFC 9091Experimental Domain-Based Message Authentication, Reporting, and Conformance (DMARC) Extension for Public Suffix DomainsObsoleted
July 2021
- RFC 8601Message Header Field for Indicating Message Authentication StatusCurrent
May 2019
- RFC 7601Message Header Field for Indicating Message Authentication StatusObsoleted
August 2015
- RFC 7001Message Header Field for Indicating Message Authentication StatusObsoleted
September 2013
- RFC 7073A Reputation Response Set for Email IdentifiersCurrent
November 2013
- RFC 7072A Reputation Query ProtocolCurrent
November 2013
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?