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

Aggregate counts into rows

01

An aggregate report summarizes observed message streams rather than attaching individual message contents.

Related RFCs and changes

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

DIAGRAM§ 3.1 ↗
RFC 9990 · § 3.1EXAMPLE
3 / 3
Aggregate counts into rowsAn aggregate report summarizes observed message streams rather than attaching individual message contents.Aggregate counts into rowspass: 4fail: 2aggregate rows: counts, not message bodies
03
Report the summary

Keep the aggregate distinct from a per-message failure report.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
WHAT CHANGED
RFC 7489DMARC aggregate reports

Aggregate reporting is now a standalone Standards Track document replacing its portion of RFC 7489, alongside separate policy and failure-report specifications.

Read the updated RFC section ↗
KEY POINT

Report records include source IP, count, policy evaluation, identifiers, and authentication results.

  • Report records include source IP, count, policy evaluation, identifiers, and authentication results.
  • Aggregate feedback helps domain owners understand legitimate and abusive streams.
  • Counts and authentication outcomes are not a guarantee of user delivery.
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 ↗