Domain-based Message Authentication, Reporting, and Conformance (DMARC)
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 73
- 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.
- Publication Date
- 2015-03-01
- Status Note
- Informational
- DOI
10.17487/RFC7489- Link
- https://doi.org/10.17487/RFC7489
- Author(s)
- Murray KucherawyElizabeth Zwicky
- Keyword(s)
- Domain, Email, Security, DKIM, SPF, Authentication, Reporting, Conformance
Latest version of IETF RFC 7489
Document Versions — IETF RFC 7489
-
▶ IETF RFC 7489 (2015-03-01)THIS DOC [SUPERSEDED] [LATEST VERSION]
Superseded by:
- RFC9989 NOT IN REGISTRY
- RFC9990 NOT IN REGISTRY
- RFC9991 NOT IN REGISTRY
Normative Reference(s)
- IETF RFC 1035 [Active, Amended*]
- IETF RFC 2045 [Active*]
- IETF RFC 2119 [Active*]
- IETF RFC 3986 [Active, Amended*]
- IETF RFC 4343 [Active*]
- IETF RFC 4949 [Active*]
- IETF RFC 5234 [Active, Amended*]
- IETF RFC 5321 [Active*]
- IETF RFC 5322 [Active, Amended*]
- IETF RFC 5890 [Active*]
- IETF RFC 6376 [Active*]
- RFC6591 — ARF-AUTHFAIL EXTERNAL
- RFC6651 — AFRF-DKIM EXTERNAL
- IETF RFC 6652 [Active*]
- RFC6713 — GZIP EXTERNAL
- IETF RFC 7208 [Active*]
Bibliographic Reference(s)
- Kitterman, S., "Sender Policy Framework: Best guess record (FAQ entry)", May 2010, < http://www.openspf.org/FAQ/Best_guess_record >. EXTERNAL
- IETF RFC 2142 [Active*]
- IETF RFC 3464 [Active*]
- IETF RFC 4033 [Active*]
- IETF RFC 4686 [Active*]
- IETF RFC 5226 [Superseded*]
- RFC5585 — RFC5585 EXTERNAL
- IETF RFC 5598 [Active*]
- IETF RFC 5617 [Active*]
- RFC5863 — RFC5863 EXTERNAL
- RFC5965 — ARF EXTERNAL
- RFC6377 — RFC6377 EXTERNAL
- RFC7001 — RFC7001 EXTERNAL
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC7489.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 7489, Domain-based Message Authentication, Reporting, and Conformance (DMARC). Available at https://doi.org/10.17487/RFC7489
Snippet:
IETF RFC 7489, Domain-based Message Authentication, Reporting, and Conformance (DMARC). Available at https://doi.org/10.17487/RFC7489
HTML (ISO 690 compliant)
Preview:
IETF RFC 7489, Domain-based Message Authentication, Reporting, and Conformance (DMARC). Available at https://doi.org/10.17487/RFC7489
Snippet:
<span class="citation"><cite>IETF RFC 7489</cite>, Domain-based Message Authentication, Reporting, and Conformance (DMARC). Available at <a href="https://doi.org/10.17487/RFC7489" target="_blank" rel="noopener">https://doi.org/10.17487/RFC7489</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 7489, Domain-based Message Authentication, Reporting, and Conformance (DMARC)
doi: 10.17487/RFC7489
url: https://doi.org/10.17487/RFC7489
doi: 10.17487/RFC7489
url: https://doi.org/10.17487/RFC7489
Snippet:
<li> <cite id="bib-rfc7489">IETF RFC 7489</cite>, Domain-based Message Authentication, Reporting, and Conformance (DMARC) <span class="doi">10.17487/RFC7489</span> </li>
Referenced By
- IETF RFC 8553 [Active*]
- IETF RFC 8616 [Active*]
- IETF RFC 9788 [Active*]