RFC7489 — Domain-based Message Authentication, Reporting, and Conformance (DMARC)
RFC7489: Domain-based Message Authentication, Reporting, and Conformance (DMARC)
⚠️ Obsoleted. This RFC has been superseded by RFC9989, RFC9990, RFC9991. Read the successor before relying on this document.
IETF Request for Comments
| Status | INFORMATIONAL |
| Publication status | INFORMATIONAL |
| Published | March 2015 |
| Stream | INDEPENDENT |
| Obsoletes | — |
| Obsoleted by | RFC9989, RFC9990, RFC9991 |
| Updated by | RFC8553, RFC8616 |
Abstract
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.
Official sources
- Info page: https://www.rfc-editor.org/info/rfc7489
- Full text: https://www.rfc-editor.org/rfc/rfc7489.txt
- HTML: https://www.rfc-editor.org/rfc/rfc7489.html
Abstract and metadata are reproduced from the public RFC index; the full text is linked, not copied.