RFC 9091: Experimental Domain-Based Message Authentication, Reporting, and Conformance (DMARC) Extension for Public Suffix Domains
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9989.
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), defined in RFC 7489, permits a domain-controlling organization to express domain-level policies and preferences for message validation, disposition, and reporting, which a mail-receiving organization can use to improve mail handling. DMARC distinguishes the portion of a name that is a Public Suffix Domain (PSD), below which Organizational Domain names are created. The basic DMARC capability allows Organizational Domains to specify policies that apply to their subdomains, but it does not give that capability to PSDs. This document describes an extension to DMARC to fully enable DMARC functionality for PSDs. Some implementations of DMARC consider a PSD to be ineligible for DMARC enforcement. This specification addresses that case.
Document record
- Document ID
- RFC9091
- Published
- July 2021
- Authors
- S. Kitterman; T. Wicinski
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- art
- Pages
- 14
- Also known as
- —
- Obsoleted by:
- RFC 9989
Topics
Standards lineage
This document is one revision in a chain of 5 RFCs, each formally replacing the one before it.
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8617The Authenticated Received Chain (ARC) ProtocolCurrent
July 2019
- RFC 9991Domain-Based Message Authentication, Reporting, and Conformance (DMARC) Failure ReportingCurrent
May 2026
- RFC 7960Interoperability Issues between Domain-based Message Authentication, Reporting, and Conformance (DMARC) and Indirect Email FlowsCurrent
September 2016
- RFC 8375Special-Use Domain 'home.arpa.'Current
May 2018
- RFC 6382Unique Origin Autonomous System Numbers (ASNs) per Node for Globally Anycasted ServicesCurrent
October 2011
- RFC 4697Observed DNS Resolution MisbehaviorUpdated
October 2006
- RFC 9090Concise Binary Object Representation (CBOR) Tags for Object IdentifiersCurrent
July 2021
- RFC 9074"VALARM" Extensions for iCalendarCurrent
August 2021
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?