metasystema.org
CurrentPROPOSED STANDARDIETF stream

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

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID
RFC9989
Published
May 2026
Authors
T. Herr; J. Levine
Status
PROPOSED STANDARD
Stream
IETF
Area
art
Pages
69
Also known as
—
Obsoletes:
RFC 7489, RFC 9091

Standards lineage

This document is one revision in a chain of 5 RFCs, each formally replacing the one before it.

  1. RFC 7489 (2015)
  2. RFC 9091 (2021)
  3. RFC 9989 (2026)
  4. RFC 9990 (2026)
  5. RFC 9991 (2026) ✓

Read the full history of Domain-Based Message Authentication, Reporting, and Conformance (DMARC) Failure Reporting →

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/9989-domain-based-message-authentication-reporting-and-conformance-dmarc