Skip to content
YHP DMARC

Knowledge base

Reading DMARC aggregate reports

What is inside the XML reports receivers send you, and how to make sense of them.

Aggregate reports (the ones sent to your rua= address) are XML files, usually zipped or gzipped, sent by each receiver once a day. Each one covers the mail that receiver saw from your domain in that period.

What is inside

  • Report metadata: who sent the report (Google, Microsoft, Yahoo, and many smaller receivers), the date range and a report ID.
  • Policy published: the DMARC record the receiver found for your domain.
  • Records: one row per sending IP address and result combination, with a message count.

Each record shows:

  • source_ip and count: which server sent how many messages.
  • policy_evaluated: the DMARC verdict. dkim and spf here are the aligned results, and disposition is what the receiver did (none, quarantine, reject).
  • auth_results: the raw SPF and DKIM results, with the domains that were checked. These can pass while the aligned result fails, when the domain is not yours.
  • reason: present when a receiver overrode your policy, for example for forwarded mail.

Making sense of them

One report is easy to read. Dozens a day from many receivers are not, which is what a reporting service is for: it combines them, identifies the organisation behind each IP, and groups rows by sender so "Microsoft 365" is one line however many IPs it used.

To read a single report by hand, upload it to the DMARC report reader, which explains each row in plain English.

Failure reports

Failure (forensic) reports, sent to ruf=, describe individual failing messages. Few large receivers send them now, mainly for privacy reasons, so aggregate reports are the main source of data.

See it on your own domain.

Check your DMARC, SPF and DKIM setup in seconds, then let us watch your reports for you.

Start free