Topic · Authentication

DMARC aggregate reports

DMARC aggregate reports summarize sending sources, authentication results and policy outcomes.

Email Security Glossary·Practical guidance
Share this definition LinkedIn X WhatsApp Email
01 / How it works

How it works

Participating receivers periodically send XML reports to a published rua address.

02 / What can go wrong

What can go wrong

Counts may duplicate activity across receivers and do not represent an exact delivery ledger.

03 / What to check or do

What to check or do

Group reports by source IP, authenticated domain, alignment and disposition.

Practical scenario

Practical scenario

One reporting receiver sends XML records that show a source IP belonging to a cloud service. The raw report lists authentication passes and disposition counts, but does not identify which employee approved that sender. Business ownership must be established separately.

Verification checklist

  1. Normalize XML reports without assuming every receiver reports at the same cadence.
  2. Group by source IP, sending hostname, From domain and disposition.
  3. Map verified vendors to internal business owners.
  4. Investigate newly seen sources and elevated aligned failures before enforcement changes.
Practical diagnosis

How to investigate DMARC aggregate reports

Signal to investigate
An unfamiliar IP in aggregate XML may be a forwarded message, a partner or abuse rather than your own sender.
Evidence to collect
Group report records by source IP, Header From, DKIM/SPF results, policy disposition and receiver.
Common wrong conclusion
Aggregate counts are per reporting receiver and time window; summing files without deduplication inflates volume.

How to interpret the evidence

Aggregate reports summarize how participating receivers evaluated traffic claiming a domain. They often identify reporting receiver, date range, source IP, counts, SPF/DKIM results, evaluated alignment and applied disposition. These are evidence for identifying sender sources—not full-message logs or precise measures of what landed in the inbox.

What to change and how to verify it

Normalize provider time ranges and deduplicate reports before comparing periods. Separate known vendors, forwarders, misconfigurations and suspicious unknown sources. Confirm attribution with contract owners or message headers before making sender-authorization decisions.

NEXT STEP

Put this into practice

Run a focused check, then explore protection if your domain needs it.

Authoritative reference ↗