Visual RFC.
ALL RFCs / RFC 7489
Read the RFC ↗
RFC 7489 / MECHANISM GUIDE

Aggregate and failure reports

04

Reports help domain operators see authentication and disposition results.

This guide explains the 2015 publication. Superseded by RFC 9989, RFC 9990, RFC 9991.

Related RFCs and changes

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

DIAGRAM§ 7 ↗
RFC 7489 · § 7EXAMPLE
3 / 3
Aggregate and failure reportsReports help domain operators see authentication and disposition results.Aggregate and failure reportsrua → aggregate countsruf → individual failure detailsExternal destination → verify consent
03
Send requested feedback

Reporting is subject to recipient capabilities and applicable privacy policy.

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

rua requests aggregate reports; ruf requests failure reports under their respective rules.

  • rua requests aggregate reports; ruf requests failure reports under their respective rules.
  • Reports can contain sensitive information; privacy and consent matter.
  • External reporting destinations require authorization verification.
DETAILS

Examples are illustrative. Consult the linked RFC and its errata for implementation details.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. Visible author and alignment
  2. Discover domain policy
  3. Pass and policy disposition
  4. Aggregate and failure reports
  5. Mailing lists and limitations
RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗