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

DNS tree walk

02

The current policy uses a bounded DNS tree walk rather than relying on one public-suffix-list interpretation.

Related RFCs and changes

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

RFC 9989 · § 4.10EXAMPLE
3 / 3
DNS tree walkThe current policy uses a bounded DNS tree walk rather than relying on one public-suffix-list interpretation.DNS tree walk_dmarc.a.mail.example.orgmail.example.orgexample.orgAuthor → Organizational → PSD preferenceDNS tree walk; not one assumed suffix list
03
Choose the effective record

Honor policy-location preference and the separately determined alignment context.

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

The tree walk supports policy discovery and alignment domain determination.

  • The tree walk supports policy discovery and alignment domain determination.
  • Policy discovery prefers the Author Domain, then its Organizational Domain, then its PSD.
  • A policy found at the Author Domain does not always establish the Organizational Domain used for alignment.
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

Drawing view

Scroll the drawing to see every part. Playback controls stay above it.

RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗