Reading DMARC aggregate reports
Aggregate (RUA) reports are raw XML sent by mailbox providers. They hold the truth about who sends as you, once you can read them.
What a report contains
Each report covers a time window from one receiver (Google, Microsoft, Yahoo…) and lists, per sending IP: the email count, the SPF result, the DKIM result, and the DMARC disposition (none / quarantine / reject) that was applied.
Reading the XML by hand
Key elements: <source_ip> identifies the source, <count> the volume, and the <policy_evaluated> block shows the SPF/DKIM alignment outcome. It is accurate but unreadable at scale: a single domain can receive hundreds of reports a day.
No one can read thousands of XML files a week. This is exactly why most domains never leave p=none. The data exists but is unusable.
Reading them in ClearDMARC
ClearDMARC ingests every report and collapses them into one view: a compliance percentage, volume trends, and a per-source breakdown of pass/fail/forwarded. Forwarded mail (where SPF breaks but DKIM survives) is separated out so you do not mistake it for an attack.
What to look for
- A high compliance percentage from your known sources (your baseline).
- Unknown IPs with failing SPF and DKIM: likely spoofing or shadow IT.
- Legitimate sources that fail alignment. Fix these before enforcing.