When you publish a DMARC record with an rua= address, mailbox providers start sending you a daily XML file for every domain they saw. Those files are the only place where you can see every system that sends mail with your domain in the From header, including the ones you forgot about and the ones you never authorised.
The DMARC Aggregate Report Analyzer opens these files in your browser, as XML, .xml.gz, .zip or the original report emails, and turns them into sending sources, alignment results, findings and advisory policy guidance. Nothing is uploaded.
What is a DMARC aggregate report?
In simple terms
A DMARC aggregate report is a receipt from a mailbox provider such as Google, Microsoft or Yahoo. It says: during this day, this many messages claiming to be from your domain came from these IP addresses, and this is how SPF, DKIM and DMARC turned out for each group.
Technical background
The format is defined in RFC 7489, Appendix C. Each report is one <feedback> XML document with report_metadata (who reports, report ID, date range), policy_published (the DMARC record the receiver found: p, sp, pct, adkim, aspf, fo) and one record per combination of source IP and results. A record holds the message count, the receiver's policy_evaluated (disposition and the DMARC verdict for DKIM and SPF), the identifiers (header from, often envelope from and envelope to) and the raw auth_results, which can include several DKIM signatures. Google sends reports as ZIP files; Microsoft and Yahoo send gzip-compressed XML.
RUA reports are aggregate reports. RUF reports, requested with ruf=, are individual failure reports for single messages; they use a different format, which the AFRF analyzer reads.
Why use a DMARC report analyzer?
Raw reports are hard to read: one XML file per provider per day, IP addresses without names, and results that look contradictory until you separate authentication from alignment. An analyzer combines many reports, sums the counts correctly, and answers the questions that matter: who sends as you, which of those senders fail, and why.
Who should use it?
- Domain and email administrators who have just published a DMARC record with p=none.
- Teams preparing to move from p=none to p=quarantine or p=reject.
- Consultants and MSPs auditing a client's email authentication.
- Anyone who receives the reports and wants to read them without sending them to a third-party service.
How the DMARC report analyzer works
Files are recognised by their content, not by their names: ZIP archives (including folders and several reports per archive), gzip files, plain XML and report emails with attachments. Unpacking is capped in size and compression ratio, which stops ZIP and gzip bombs. Archive paths are used only as labels.
The XML is read by a strict parser that rejects DTDs and entities, so external entity (XXE) attacks are impossible. Each report is validated. Missing or invalid fields produce warnings, and elements outside the standard are kept as extensions instead of being thrown away.
For every record, the DMARC outcome is the receiver's own evaluation. The analyzer then computes whether each reported SPF and DKIM pass aligns with the header-from domain under the published aspf and adkim modes. That explains why a record passed or failed; it does not replace the receiver's verdict. Identical files are detected by fingerprint and counted once. Reports with the same report ID but different content are flagged, and you choose whether to include them.
How to use the NetTools.tech DMARC Report Analyzer
- Save the report attachments from your rua= mailbox, or the report emails themselves.
- Open the DMARC Aggregate Report Analyzer and select all files at once, or drag them onto the input.
- Press Analyze DMARC Reports. Check the file-processing table for errors or duplicates.
- Read the overview cards and findings, then work through the sending-sources table, worst first.
- Classify sources you recognise, and optionally look up host names and network owners. The lookup sends only IP addresses.
- Export the result as PDF, CSV, JSON or a short text summary with the toolbar.
Understanding the results
DMARC pass means that at least one mechanism passed and aligned. SPF authentication says whether the envelope sender's SPF record allowed the IP. SPF alignment says whether that envelope-sender domain matches the header-from domain. DKIM authentication says whether a signature verified. DKIM alignment says whether the signing domain (d=) matches the header-from domain. Relaxed alignment (r) accepts subdomains of the same organizational domain; strict alignment (s) requires an exact match.
The disposition is the action the receiver applied: none, quarantine or reject. Receivers may apply local policy and report an override reason such as forwarded, mailing_list or local_policy. A disposition of none therefore does not prove your policy was p=none. Aggregate reports never show inbox placement.
Example: a third-party newsletter service
A report shows 2,400 messages from an IP of a newsletter provider. SPF passes for bounce.provider.example and DKIM passes for provider.example, yet DMARC fails. Both mechanisms authenticate a domain that is not yours, so neither aligns with your header from. The fix is in the provider's settings: enable DKIM signing with your own domain, and a custom return-path if the provider offers one. In the next reports the source turns green.
Common use cases
- Building an inventory of every service that sends mail as your domain.
- Finding legitimate senders that will break when you enforce DMARC.
- Spotting unknown sources that use your domain in the From header.
- Checking that a DKIM key rotation or a new email provider kept mail aligned.
- Producing a PDF or CSV report for a client or a change request.
Troubleshooting
A file is reported as unsupported
The content is not XML, gzip, ZIP or an email. Some mail clients save attachments with the wrong extension; the analyzer reads the content, so the file itself is damaged or of another type.
Invalid XML
The error names the line. Reports cut off during download or copied partially are the usual cause; save the attachment again.
SPF fails for my own mail server
The server's IP is not in the SPF record of the envelope-sender domain. Check the record with the SPF checker and add the server or the provider's include.
Forwarded mail fails
Forwarding changes the envelope sender, so SPF fails at the next receiver. DKIM survives plain forwarding, so sign all mail with your own domain. Mailing lists that modify messages can break DKIM too; that is expected.
Common mistakes
- Counting SPF pass as DMARC pass without checking alignment.
- Treating every failing IP as an attacker.
- Reading disposition none as delivered to the inbox.
- Enforcing p=reject after a few days of reports.
- Adding every failing IP to SPF instead of fixing DKIM for real services.
Limitations
The analyzer shows what receivers report and cannot verify SPF or DKIM itself. Relaxed alignment is computed with an approximation of the organizational domain (a list of common public suffixes); the receiver's own verdict is always shown as authoritative. Inputs are limited to 50 MB per analysis, 50 MB per XML document and 200,000 records per report. ZIP64 and encrypted archives are not supported. Classifications and notes last only for the browser session.
Security & privacy
Reports reveal your mail infrastructure and IP addresses, so they are processed locally in your browser. Nothing is uploaded or stored, and the data is dropped when you reset or leave the page. The optional lookup is started only by you, and it sends IP addresses, never report contents.
Related tools
- DMARC Checker — the record the reports refer to.
- SPF Checker — which servers your SPF record authorises.
- DKIM Checker — the keys behind the reported selectors.
- AFRF Analyzer — individual DMARC failure reports (ruf=).
- MIME Report Inspector — any report email, with a link to this analyzer.
Summary
DMARC aggregate reports show who sends mail as your domain and whether that mail authenticates and aligns. The NetTools.tech DMARC Aggregate Report Analyzer reads them from any common format and keeps the receivers' verdicts intact. It explains every failure, and its policy guidance is clearly advisory. All of this happens in your browser.
Frequently asked questions
What is the difference between RUA and RUF reports?
RUA reports are daily aggregate XML summaries with counts per sending IP. RUF reports are individual failure reports for single messages, sent in the AFRF format and supported by far fewer receivers.
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 sending service can pass SPF for its own bounce domain and still fail DMARC.
Does disposition none mean the message reached the inbox?
No. The disposition is the DMARC action the receiver applied. Aggregate reports say nothing about spam-folder placement or delivery.
Is every source that fails DMARC a spoofer?
No. Forwarders, mailing lists and services you have not configured yet fail too. Investigate a failing source before you decide whether it is legitimate.
Are my report files uploaded?
No. Files are unpacked and analysed in your browser. Only the optional host and network lookup sends data, and it sends IP addresses only.
How long should I collect reports before enforcing?
At least two to four weeks, from several large receivers, until all legitimate sources pass with aligned SPF or DKIM. One day of reports is never enough.