Once your DMARC record has an rua= address, mailbox providers send a report roughly once a day. It arrives as an email with a
compressed XML attachment (.xml.gz or .zip), named like google.com!example.com!1727654400!1727740799.xml.gz.
What's inside
After some metadata (who sent the report, which period) and your published policy, there's one <record> per sending IP address:
<record>
<row>
<source_ip>209.85.220.41</source_ip>
<count>312</count>
<policy_evaluated>
<disposition>none</disposition>
<dkim>pass</dkim>
<spf>pass</spf>
</policy_evaluated>
</row>
<identifiers><header_from>example.com</header_from></identifiers>
<auth_results>
<dkim><domain>example.com</domain><selector>google</selector><result>pass</result></dkim>
<spf><domain>example.com</domain><result>pass</result></spf>
</auth_results>
</record>
source_ipandcount: which server sent how many messages.policy_evaluated: the DMARC verdict.dkimandspfhere mean aligned pass or fail.dispositionis what the receiver did.auth_results: the raw SPF and DKIM results, with the domains they were checked for. This is where you see why alignment failed.
Turning it into answers
- Group the records by who owns the IP address: look up its reverse DNS or the network owner.
- Mark each group as yours (your mail provider, CRM, newsletter tool), forwarding (a mailbox provider relaying mail on), or unknown.
- For your own services with failures, fix DKIM or SPF alignment.
- Unknown sources with high volume and 0% pass are usually spoofing.
Reports contain no message content, subjects or recipients. ruf= (failure reports) is a different kind: few providers send them,
and those that do may include personal data, so most domains don't request them.