Question 1

What's a DMARC aggregate report?

Accepted Answer

An aggregate (RUA) report is an XML file that mailbox providers like Google, Yahoo, and Microsoft send you every 24 hours. It summarizes which messages claiming to be from your domain reached their servers, where they came from, and whether they passed SPF, DKIM, and DMARC.

Question 2

Is this DMARC report parser free?

Accepted Answer

Yes. Paste or upload an aggregate XML report and the parser returns a sender map, alignment diagnosis, remediation list, and live DNS posture check at no cost. There's no signup to use it.

Question 3

What does the live DNS check actually do?

Accepted Answer

When you submit a report, the parser also looks up the current DMARC, SPF, and DKIM records for the policy domain (the one inside the policy_published block), plus MTA-STS, TLS-RPT, and BIMI presence. That lets us flag the difference between what the report saw at the time and what's published now, and surface things the XML alone wouldn't tell you, like an SPF record over the 10-lookup limit.

Question 4

How does the parser identify my senders?

Accepted Answer

For each source IP in the report, the parser does a reverse-DNS lookup and matches the result against a list of known email service providers (Google Workspace, Microsoft 365, Mailchimp, SendGrid, Amazon SES, and others). Where there's a match, you'll see the sender by name. Where there isn't, you'll see the IP and PTR record so you can investigate it yourself.

Question 5

Is my report data private?

Accepted Answer

Your report XML is parsed and discarded. We don't store the contents, the source IPs, or any of the data inside the file. The only thing cached is the result of the DNS lookups for the policy domain, for 60 seconds, so popular domains stay fast. That cache is shared across all our DNS tools, not specific to your report.

Question 6

What's the difference between aggregate (RUA) and forensic (RUF) reports?

Accepted Answer

Aggregate reports are 24-hour summaries grouped by source IP, sent daily by most major providers. Forensic (RUF) reports are per-message failure samples, much rarer, and most providers don't send them at all because of privacy concerns. This parser is built for aggregate XML.

Question 7

Can I parse a .xml.gz or .zip file?

Accepted Answer

Yes. Use the upload tab and drop the file directly. We decompress in your browser before sending the XML to the parser.

Question 8

How big can my report be?

Accepted Answer

Up to 10 MB after decompression. Most aggregate reports are well under 1 MB, even for high-volume domains. If yours is larger, you may have a multi-day report or a report from an unusually busy provider.

Question 9

What's a good DMARC pass rate?

Accepted Answer

For a domain at p=quarantine or p=reject, aim for 95% or higher across at least 30 days, with zero unauthorized sources passing. Below 95% means at least one legitimate sender isn't aligned, or you have a misconfiguration. The verdict at the top of the parser tells you whether your current pass rate is good enough to advance to the next policy.

Question 10

Why are DMARC reports in XML format?

Accepted Answer

The XML format is defined in RFC 7489 so any tool can parse aggregate reports the same way. It's a machine-to-machine format. The cost is that humans need a parser to read them. The benefit is that every provider sends the same structure, so once you've decoded one, you've decoded them all.

Question 11

I don't have a DMARC report. How do I get one?

Accepted Answer

You need to publish a DMARC record with a rua= tag pointing at a mailbox you can read. Reports start arriving within 24 to 72 hours. See our guide to setting up DMARC reporting.

Free DMARC Report Parser

What you'll see

Most free parsers show

This parser also shows

What a DMARC aggregate report is

Related free tools

DMARC Checker

SPF Checker

DKIM Checker

Email Auth Health Check

Learn more about DMARC reports

How to Read DMARC XML Reports

DMARC Alignment Explained Simply

Why Domains Get Stuck at p=none

The Complete DMARC Policy Guide