Visual RFC.
ALL RFCs / RFC 9989
Read the RFC ↗
RFC 9989 / CURRENT DMARC

Policy tags and scope

03

The policy record expresses domain-owner preferences and alignment mode.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 4.7 ↗
RFC 9989 · § 4.7EXAMPLE
3 / 3
Policy tags and scopeThe policy record expresses domain-owner preferences and alignment mode.Policy tags and scopev=DMARC1; p=rejectadkim=r; aspf=sScope: author / subdomain / non-existent
03
Apply the relevant scope

Select policy for the actual author-domain context.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

The record uses registered tag-value syntax; unknown tags must be ignored.

  • The record uses registered tag-value syntax; unknown tags must be ignored.
  • p= expresses policy; adkim and aspf choose strict or relaxed alignment.
  • Subdomain and non-existent-domain handling have their own tags and scope rules.
DETAILS

Examples are illustrative. Read the exact policy, reporting, and privacy rules in the linked current specification.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. Aligned authentication
  2. DNS tree walk
  3. Policy tags and scope
  4. Receiver handling
  5. Deployment and feedback
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗