Skip to main content

Domain-Based Message Authentication, Reporting, and Conformance (DMARC)
RFC 9989

Revision differences

Document history

Date By Action
2026-07-08
(System) Update from RFC Editor: added verified-errata tag
2026-06-10
(System) Update from RFC Editor: added errata tag
2026-05-22
(System) IANA registries were updated to include RFC9989
2026-05-20
(System) Changed author "J. Levine": changed name from "John Levine" to "J. Levine", changed is_editor from "False" to "True"
2026-05-20
(System) Changed author "T. Herr": changed name from "Todd Herr" to "T. Herr", changed is_editor from "False" to "True"
2026-05-20
(System) Metadata update from RFC Editor
2026-05-19
(System)
Received changes through RFC Editor sync (created document RFC 9989, created became rfc relationship between draft-ietf-dmarc-dmarcbis and RFC 9989, set title to 'Domain-Based …
Received changes through RFC Editor sync (created document RFC 9989, created became rfc relationship between draft-ietf-dmarc-dmarcbis and RFC 9989, set title to 'Domain-Based Message Authentication, Reporting, and Conformance (DMARC)', set abstract to 'This document describes the Domain-based Message Authentication, Reporting, and Conformance (DMARC) protocol.

DMARC permits the owner of an email's Author Domain to enable validation of the domain's use to indicate the Domain Owner's or Public Suffix Operator's message handling preference regarding failed validation and to request reports about the use of the domain name. Mail-receiving organizations can use this information when evaluating handling choices for incoming mail.

This document obsoletes RFCs 7489 and 9091.', set pages to 69, set standardization level to Proposed Standard, added RFC published event at 2026-05-19, created obsoletes relation between RFC 9989 and RFC 7489, created obsoletes relation between RFC 9989 and RFC 9091)
2026-05-19
(System) RFC published