Skip to content
Glossary · Authentication

DMARC aggregate report

The daily XML summary a receiver sends to a domain's rua address, counting messages by sending IP address with their SPF, DKIM and DMARC results.

What it means

Receivers that support DMARC reporting send one report per domain per reporting period, normally daily. The XML file, usually gzip-compressed and attached to an email, lists the policy the receiver found and rows grouped by source IP address: message count, the disposition applied, the SPF and DKIM domains and results, and whether each aligned.

These reports are the main tool for reaching enforcement. They show every service sending as the domain, legitimate or not, and which ones fail alignment. They contain no message content. The format is now defined by RFC 9990, which replaced the reporting part of RFC 7489.

Raw XML is hard to read at volume; a parser or reporting service turns it into a list of sources.

Example

<record><row><source_ip>192.0.2.10</source_ip><count>412</count><policy_evaluated><disposition>none</disposition><dkim>pass</dkim><spf>fail</spf></policy_evaluated></row>...</record>

On this site

Sources

What this definition rests on. The wording is ours; the facts are theirs.

All 432 terms in the glossaryThe wiki: blocklists and bounce codes

Beat · paid monitoring

A heartbeat for your email.

Beat runs every check on this site on a schedule: 41 checks, 25 blacklists and real inbox placement. The moment something breaks, it tells you what broke, why it matters, and the exact fix.

example.comWatching
  • SPFpass
  • DKIMpass
  • DMARCp=none
  • Blacklists0 of 25

Illustrative. Your domain, every few hours.

Also from us:Pulse: your own sending infrastructureConsulting: $65/hr, no retainer