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

Request and recipient consent

03

rua identifies aggregate report destinations, and external destinations require verification.

Related RFCs and changes

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

DIAGRAM§ 4 ↗
RFC 9990 · § 4EXAMPLE
3 / 3
Request and recipient consentrua identifies aggregate report destinations, and external destinations require verification.Request and recipient consentrua: mailto:reports@external.exampleDNS consent checkNo consent → stop external delivery
03
Deliver only when permitted

A missing authorization stops the external reporting path.

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

Discover rua from the applicable DMARC policy.

  • Discover rua from the applicable DMARC policy.
  • Verify external destinations under the defined DNS authorization procedure.
  • Do not deliver an unauthorized external report merely because a sender’s policy named it.
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. Aggregate counts into rows
  2. XML report anatomy
  3. Request and recipient consent
  4. Delivery and duplicates
  5. Privacy and untrusted reports
RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗