Analyze DMARC aggregate reports

Open several files at once: .xml, .xml.gz and .zip as sent by Google, Microsoft, Yahoo and others, or the report emails (.eml). Up to 50 MB in total.

Your reports are unpacked and analysed in your browser. Nothing is uploaded; sending IP addresses stay on your device unless you start the optional lookup.

How it works

Files are recognised by their content (ZIP, GZIP, XML or email), unpacked with size and compression-ratio limits and parsed by a strict XML parser without DTD or entity support — all in your browser. Each record keeps the receiver’s own DMARC evaluation; alignment of the reported SPF and DKIM results with the header-from domain is computed to explain it. Sources, organisations, policy and findings are aggregated from the records only.

What the analyzer reads

  • DMARC aggregate reports (RUA, RFC 7489 Appendix C): one XML document per receiver and day, with counts per sending IP and the SPF, DKIM and DMARC results the receiver saw. Not individual failure reports (RUF) — use the AFRF analyzer for those, the ARF analyzer for complaints, and the APRF analyzer for performance reports.
  • The DMARC result per record is the receiver's own evaluation (policy_evaluated). The analyzer does not re-verify SPF or DKIM; it computes alignment of each reported result with the header-from domain to explain why mail passed or failed.
  • Aggregate reports say nothing about inbox placement: a disposition of “none” means no DMARC action was taken, not that the message reached the inbox.

Inspect reports on the command line

unzip -l report.zip                 # list the XML files in a Google-style ZIP
unzip report.zip -d extracted/      # extract them
gunzip -k report.xml.gz             # keep the .gz, write report.xml
xmllint --format report.xml         # pretty-print (package: libxml2-utils / libxml2)
grep -n '<source_ip>' report.xml    # list sending IPs with line numbers
xmllint --xpath '//record' report.xml               # print every record
xmllint --xpath 'sum(//record/row/count)' report.xml # total message count

On Windows, tar -xf report.zip extracts ZIP files; xmllint ships with libxml2 (e.g. via WSL, Git for Windows or MSYS2).

Safeguards & responsible use

  • Your reports are processed locally in your browser. Nothing is uploaded to NetTools servers.
  • The optional host / network lookup sends only IP addresses, and only when you start it.
  • ZIP and GZIP bombs, path traversal in archives and XML entity attacks are blocked; DTDs and entities are never processed.

Frequently asked questions

Which files can I open?

DMARC aggregate reports as .xml, .xml.gz or .zip (also several at once, and ZIPs with several reports or folders), and the report emails themselves (.eml).

Does SPF pass mean DMARC pass?

No. DMARC needs SPF or DKIM to pass and to align with the domain in the From header. A third-party service can pass SPF for its own bounce domain and still fail DMARC.

Does disposition “none” mean the mail reached the inbox?

No. Aggregate reports only state the DMARC action a receiver applied. They say nothing about spam-folder placement or delivery.

Are failing sources attackers?

Not necessarily. Forwarders, mailing lists and services you have not configured yet also fail. The analyzer never labels a source malicious on its own; you can classify sources yourself.