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

Minimize sensitive evidence

04

Failure feedback can contain private message content and therefore creates greater exposure than aggregate counts.

Related RFCs and changes

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

DIAGRAM§ 7 ↗
RFC 9991 · § 7EXAMPLE
3 / 3
Minimize sensitive evidenceFailure feedback can contain private message content and therefore creates greater exposure than aggregate counts.Minimize sensitive evidenceFrom: [minimized]Subject: [redacted]Body: [omitted]Controlled recipient · limited duration · secure channel
03
Limit and protect delivery

Restrict recipients and duration and use a secure channel.

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

Consider targeted diagnostic use with limited scope and duration.

  • Consider targeted diagnostic use with limited scope and duration.
  • Redact bodies and headers to reduce sensitive data exposure.
  • Carefully control reporting URIs and transmit over secure channels.
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 ↗