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

Privacy and untrusted reports

05

Even aggregate reports can disclose traffic metadata, and report content is untrusted input.

Related RFCs and changes

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

DIAGRAM§ 7 ↗
RFC 9990 · § 7EXAMPLE
3 / 3
Privacy and untrusted reportsEven aggregate reports can disclose traffic metadata, and report content is untrusted input.Privacy and untrusted reportssource IP + count + outcomesdestination: third-party consumerretention and access policyMetadata can reveal traffic patternsValidate untrusted XML with resource limits
03
Parse defensively

Treat received report data as untrusted, not as authenticated truth.

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

Third-party report recipients can perform traffic analysis.

  • Third-party report recipients can perform traffic analysis.
  • Internal privacy policy may constrain transmission and retention.
  • Consumers need safe XML handling, validation, and resource limits for reports.
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 ↗