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

Structured ARF fields

02

The augmented failure-report format includes alignment and authentication-specific fields.

Related RFCs and changes

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

DIAGRAM§ 4 ↗
RFC 9991 · § 4EXAMPLE
3 / 3
Structured ARF fieldsThe augmented failure-report format includes alignment and authentication-specific fields.Structured ARF fieldsIdentity-Alignment: requiredDKIM failure: domain / identity / selectorSPF failure: SPF-DNSARF report structure + permitted context
03
Package diagnostic feedback

Keep structured report fields distinct from optional original-message data.

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

Identity-Alignment is required.

  • Identity-Alignment is required.
  • Aligned DKIM failures require DKIM-Domain, DKIM-Identity, and DKIM-Selector.
  • An aligned SPF failure requires SPF-DNS; other fields have their specified requirement levels.
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. An individual failure report
  2. Structured ARF fields
  3. External failure recipients
  4. Minimize sensitive evidence
  5. Abuse and recipient controls

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 ↗