metasystema.org
ObsoletedINFORMATIONALINDEPENDENT stream

RFC 7489: Domain-based Message Authentication, Reporting, and Conformance (DMARC)

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9989, RFC 9990, RFC 9991.

Current document in this lineage: RFC 9989 — Domain-Based Message Authentication, Reporting, and Conformance (DMARC); RFC 9990 — Domain-Based Message Authentication, Reporting, and Conformance (DMARC) Aggregate Reporting; 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 scalable mechanism by which a mail-originating organization can express domain-level policies and preferences for message validation, disposition, and reporting, that a mail-receiving organization can use to improve mail handling. Originators of Internet Mail need to be able to associate reliable and authenticated domain identifiers with messages, communicate policies about messages that use those identifiers, and report about mail using those identifiers. These abilities have several benefits: Receivers can provide feedback to Domain Owners about the use of their domains; this feedback can provide valuable insight about the management of internal operations and the presence of external domain name abuse. DMARC does not produce or encourage elevated delivery privilege of authenticated email. DMARC is a mechanism for policy distribution that enables increasingly strict handling of messages that fail authentication checks, ranging from no action, through altered delivery, up to message rejection.

Document record

Document ID
RFC7489
Published
March 2015
Authors
M. Kucherawy; E. Zwicky
Status
INFORMATIONAL
Stream
INDEPENDENT
Area
—
Pages
73
Also known as
—
Obsoleted by:
RFC 9989, RFC 9990, RFC 9991
Updated by:
RFC 8553, RFC 8616

Topics

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 →

Referenced by

5 later RFCs formally update or obsolete part of this document.

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/7489-domain-based-message-authentication-reporting-and-conformance-dmarc