DMARC Report Analyzer
Those daily emails with an unreadable .xml, .gz or .zip attachment are DMARC aggregate reports. Drop one here and see, in plain English, every server that sent email as your domain, whether it passed, and what to fix.
or click to choose them. .xml, .xml.gz, .gz and .zip, several at once.
What the four verdicts mean
What is a DMARC aggregate report?
When your domain publishes a DMARC record with an rua address, the big mailbox providers send that address a summary, usually once a day, of every message they received that claimed to be from your domain. The summary is an XML file, normally compressed, and it lists each sending IP address, how many messages it sent, and whether those messages passed SPF, DKIM and DMARC.
That makes the aggregate report the only way to see mail sent in your name that you never see yourself, including mail from services a colleague signed up for years ago, and mail from people pretending to be you. The trouble is the format. A single report can hold dozens of records, nested several levels deep, and a week of reports from Google, Microsoft and Yahoo is a lot of reading. This DMARC report analyzer turns the files into one list, grouped by sender, with a verdict and a fix for each.
How to read your DMARC report
- Start with the senders that fail and send the most. Tick Only show senders that fail. The list is sorted by message count, so the top entries matter most.
- Look at the service name and the domains. When the DKIM signature or SPF check names a known service, such as SendGrid, Mailchimp or Amazon SES, the analyzer says so. If it says Authenticated, not aligned, open that service's settings and turn on sending with your own domain (often called domain authentication, custom DKIM or a branded return-path).
- Identify the unknowns. Press Look up IP host names. A host name like
mail-sor-f41.google.comora8-12.smtp-out.amazonses.comtells you who owns the server. If a sender fails everything and belongs to nobody you use, it is most likely spoofing your domain. - Fix, wait, and read the next reports. DNS changes take effect within hours, but reports arrive a day behind. Give each change a few days before you judge it.
To check the DNS side of the same problem, the SPF record, the DKIM keys and the DMARC policy itself, use the SPF, DKIM & DMARC Checker. To trace one suspicious message, paste its headers into the Email Header Analyzer.
Not getting reports yet? Turn them on
Reports only arrive if your DMARC record asks for them. Add an rua tag with a mailbox you can read. A good starting record looks like this, published as a TXT record at _dmarc.yourdomain.com:
v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com
p=none means receivers report but do not block anything yet, which is exactly what you want while you find your senders. Use a dedicated mailbox or alias: a busy domain can receive dozens of reports a day.
If the reports go to a mailbox on a different domain, that domain has to agree to receive them, by publishing a TXT record of v=DMARC1 at yourdomain.com._report._dmarc.otherdomain.com. Without it, receivers that follow the standard (RFC 7489, section 7.1) will not send the reports. Not sure what your record currently says? The DMARC checker shows it.
From p=none to reject, using your reports
The point of reading reports is to reach a policy that actually stops impersonation. A domain at p=none is only watching. The usual path:
- Run at
p=nonefor two to four weeks and read the reports. Fix every real service until it shows as Passing. - Move to
p=quarantine. Failing mail now goes to spam rather than being delivered normally. Keep reading reports for a week or two. - Move to
p=rejectonce the only failures left are senders you do not recognise. Spoofed mail is now refused outright.
Do not skip the reading step. Turning on reject before every invoicing, newsletter and help-desk tool passes is the classic way to make your own invoices disappear. And keep reading after you get there: new tools get added, and a service you rely on can change how it sends.
Why this DMARC report reader works in your browser
A DMARC report is a list of the servers and services your business uses to send email, along with your domain name and your mail volumes. That is useful information to an attacker planning a convincing fake invoice, and most report services ask you to point your reports at their mailbox or upload them to their servers to read them.
This analyzer reads the files on your own device. Compressed reports are unpacked with the decompression built into your browser, and the XML is read with the browser's own parser. Nothing in the file is sent to StashGrid or anyone else. The one optional exception is the host-name lookup, which sends the sending IP addresses, never the file or your domain, to Cloudflare's public DNS. The page itself loads ads and analytics like every StashGrid page; the analytics event records only counts, such as how many reports were read, never your domain or IP addresses. Read the StashGrid privacy policy.
Two limits are worth knowing. Reports only come from receivers that send them, so mail to small providers and private servers will not appear. And this tool reads aggregate (rua) reports only, not forensic (ruf) failure reports, which are rarely sent any more.
Frequently asked questions
Is my DMARC report uploaded anywhere?
No. The report file is opened and read by your browser; it is not sent to StashGrid or anyone else. The only exception is the optional reverse-DNS button, which sends the sending IP addresses (not the file) to Cloudflare's public DNS so it can look up their host names. The page itself loads advertising and analytics; the analytics event records only counts, never your domain or IP addresses.
How do I start receiving DMARC aggregate reports?
Add an rua tag to your DMARC record, for example v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com. Mailbox providers such as Google, Yahoo and Microsoft then email you a report, usually once a day, listing the IP addresses that sent mail using your domain and whether each one passed.
What does authenticated but not aligned mean?
The mail passed SPF or DKIM, but for a different domain than the one in the visible From address, so DMARC still counts it as a failure. It almost always means a real service, such as a newsletter or invoicing tool, is sending as you with its own domain. Turning on that service's custom DKIM or custom return-path for your domain fixes it.
Why are there IP addresses in my report that I do not recognise?
Usually they are either a service you forgot sends as you, or someone putting your domain in the From address. If an IP fails both SPF and DKIM and its host name does not belong to any service you use, it is most likely spoofing, which is exactly what a quarantine or reject policy stops. Forwarded mail can also show up from a mailbox provider's IP with SPF failing and DKIM passing.
When is it safe to move my DMARC policy from p=none to reject?
When a few weeks of reports show that every service you actually use passes DMARC, and the only failures left are senders you do not recognise. Go to p=quarantine first, keep reading reports for another week or two, then move to p=reject.
Does this read DMARC forensic (ruf) reports?
No. It reads aggregate reports, the XML summaries sent to the rua address. Forensic or failure reports are copies of individual failing messages in a different format, and few large mailbox providers send them any more.