Free DMARC report guide and PDF
How to read a DMARC report: who is sending as you, and what to do next
For: anyone with DMARC set up who has a pile of report attachments they cannot read, a sender in them they do not recognise, or no reports at all and no idea why.
- Read your own report with our free DMARC report parser.
- Six steps and a field table to read any report yourself.
- The steps and the table of the report's parts as a PDF.

The 60-second answer
You set up DMARC, and now XML files turn up in your inbox every day. Drop one in, or paste it, tick the senders you know, and the row that matches lights up below. It is read in your browser only. Every row is on this page, and the guide under it shows you how to read any report yourself.
A DMARC report is a daily file from the mailbox providers. It lists every source that sent email as your domain, how many messages each sent, and whether SPF and DKIM passed with alignment.
Ask each source two questions. Do you know it? Does it pass with alignment? A source you cannot explain that fails is either a tool you forgot or someone spoofing you.
Only one of SPF or DKIM has to pass and align. When every source you know passes, week after week, with no strangers, you are ready to tighten your policy.
Every explanation on this page comes from the Email Almanac, our own library of more than 4,000 answers about email. You do not have to buy anything to read it.
- You get one email.It comes from Review My Emails, with the PDF link inside.
- Your PDF is the whole guide.The steps and the table of the report's parts, ready to print.
- Nothing else, unless you ask.No newsletter unless you tick the box. Unsubscribe in one click, any time.
Free tool
Check yours with our free tool.
Drop your report into our free DMARC report parser to see who sends as your domain and how much passes. Then read what to do in the steps on this page.
Open the free DMARC report parserThe guide
How to read any DMARC report, in 6 steps
One line each. Tick them as you go. Open a step for the full explanation.
- 1
Why:it comes compressed, gzip or zip, and usually covers 24 hours.
Check your DMARC record asks for reports
Read the full explanation
Each day, the mailbox providers that support DMARC send a report to the address in the
ruatag of your DMARC record. It comes as a compressed XML file, gzip or zip, and you unzip it before anything can read it. The file name says who sent it and for which domain, in a pattern likereceiver.example!yourdomain.example!1700000000!1700086400.xml.gz, and one report usually covers 24 hours. It is a summary of totals, not a log of messages. It holds no individual messages and no recipient details. - 2
Why:each record names the IP, how many messages, and whether SPF and DKIM passed.
Read the full explanation
The file is a list of records, one per sending source. Each one names the server's IP, how many messages it sent, whether SPF and DKIM passed, and what the receiver did with the mail. The table below shows the parts you will see. Take the Almanac's own example: 1,240 messages from one IP passed DKIM, failed SPF, and show the disposition
none, so they were delivered as normal, because the policy only asks for monitoring. - 3
Why:an IP you cannot explain is a tool you forgot or someone spoofing your domain.
The DMARC p=none to p=reject guide
Read the full explanation
Most sources will be your email marketing tool, the service that sends your receipts, and perhaps your help desk or your CRM. An IP you cannot explain, above all one that fails, is either a sending service you forgot or someone trying to spoof your domain, and the two need very different responses. Look into each unknown IP before you decide to add it to your SPF record or to block it. A large count from an IP that is not yours is a spoofing attempt worth flagging.
- 4
Why:only one of SPF or DKIM has to align for DMARC to pass.
The authentication failures guide
Read the full explanation
Alignment means the domain that passed SPF or DKIM matches the From address your readers see. Only one of the two has to align for DMARC to pass. A tool can pass SPF for its own domain and still fail alignment for yours, which is why a report can show failures from a sender you trust. The usual fix is DKIM: your email marketing tool gives you records to add to your DNS, and from then on it signs with your domain.
- 5
Why:forwarding breaks SPF. DKIM survives as long as nothing in the message changes.
Read the full explanation
When a reader forwards your mail on, the forwarder sends it from its own server, so SPF fails. DKIM survives as long as nothing in the message changes, and then DMARC still passes on DKIM. Mailing lists add subject tags and footers, which can break both. Your reports show how many failures are list-related, and that tells you how urgent this is for you.
- 6
Why:a source that keeps failing has something set up wrong.
Read the full explanation
Watch the pass rate of each source over time. A source that keeps failing has something set up wrong. Weekly is usually enough while you monitor, and daily while you tighten your policy or chase a problem. Not every mailbox provider sends reports, so they are a real but incomplete picture of your mail.
See every row of the table
What your report means
| Your report | Do this first |
|---|---|
| No reports at all. Nothing has arrived since you set up DMARC, or you are not sure you asked for any | Check your record with the free DMARC checker. Without an rua tag you get no data at all. The record must sit at _dmarc with the underscore. The address needs mailto: in front of it, and an outside address must accept reports for your domain or they vanish without an error. Two DMARC records can count as no DMARC record at all. A domain that sends very little may get few reports |
Your own mail is being stopped. A source you know fails DMARC, and the report shows quarantine or reject | Fix this sender first. At quarantine its failing mail goes to spam, and at reject it is refused with a bounce. Get the tool signing with your domain. Stuck on it? Ask the free SOS line |
| A source you do not know fails. An IP you cannot place, failing DMARC | Find out whose it is before you act. It is a tool you forgot or someone spoofing your domain, and those need very different fixes. Do not add it to your SPF record until you know. If it is not yours, p=none lets it through, and only quarantine or reject stops it. Read our guide "DMARC from p=none to p=reject" |
| A source you do not know passes. An IP you cannot place passes SPF with alignment | Your own SPF record lists the servers allowed to send for you, so something you allowed is sending as you. Ask who set up a new tool. If no one did, treat it as a misused account: change your email marketing tool's password, check its sending logs and talk to its support team |
A source you know fails alignment. Your email marketing tool, your shop or your help desk shows fail, and the policy is still none | A setup fix, not an attack. Ask the tool for its DKIM records so it signs with your domain. SPF often passes for the tool's own domain and still fails alignment. If one tool fails DKIM while others pass, check its selector and key. Fix it before you tighten your policy |
| SPF fails, DKIM passes. Rows from servers you do not know, where DMARC still passes | This is what forwarding looks like. The forwarder sends from its own server, so SPF fails, and DKIM survives an unchanged message, so DMARC passes on DKIM and the mail goes through. Mailing lists can break both, so watch how many failures are list-related |
| Every source passes. All the sources are yours, and all of them pass with alignment | Keep reading reports for two to four weeks. When every legitimate source passes and no unknown IPs appear, you are ready for p=quarantine. Read our guide "DMARC from p=none to p=reject". A pass proves the mail is yours. It does not decide the inbox |
| Reports arrive, but you cannot read them. An attachment that will not open, or a wall of XML | Drop the file in the box above just as it came, or unzip it and paste the XML. It arrives compressed, and nobody reads it by eye. Then work through the steps above, one source at a time |
What each part of the report means
| Field | What it means |
|---|---|
receiver.example!yourdomain.example!start!end.xml.gz | The file name: the provider that sent the report, your domain, and the time window it covers |
<record> | One sending source, with everything below inside it |
<source_ip> | The IP address of the server that sent the mail |
<count> | How many messages came from that IP in the window |
<disposition> | What the receiver did with the mail: none, quarantine or reject |
<dkim> | Whether DKIM passed and aligned with your domain |
<spf> | Whether SPF passed and aligned with your domain |
<header_from> | The From domain the row is about, so you can see results for each sending domain |
| The other parts of the file | Not in the Almanac yet |
See how it plays out for a real business
Worked example. Skipper Mako runs Barnacle & Bloom, a florist, and sends the weekly offers from news@barnacle-bloom.example. A week after DMARC went up at p=none, the first report arrives as a zipped attachment. Skipper drops it into the box, still zipped, and it shows two sources. The first sent 1,180 messages, passed DKIM and failed SPF. That is the shop's email marketing tool: it uses its own domain for SPF, so SPF does not align with Barnacle & Bloom's, but DKIM is signed with the shop's domain, and one aligned pass is enough. Skipper ticks it as known. The second, 203.0.113.7, sent 38 messages and failed both, with the disposition none, so those 38 were delivered as normal. It is not the shop's order emails or its booking calendar either. The row that lights is "A source you do not know fails". Skipper does not add the stranger to the SPF record. When the same IP turns up again the next week, Skipper follows the guide "DMARC from p=none to p=reject", because only quarantine or reject stops mail like that.
Who we are
About Review My Emails
Review My Emails is email list cleaning and validation that tells you which addresses to keep, which to watch and which to stop sending to, and why.
Most checkers answer one question: does this address exist? We answer the next one: should you send to it? An address can be perfectly valid and still be quietly damaging your sender reputation. Valid is not safe.
The company was founded in 2020 and is based in Bolton, United Kingdom. Our founder is Yanna-Torry Aspraki, an email deliverability specialist who has worked in deliverability since 2015.
Your next step. Check that your record asks for reports with the free DMARC checker at reviewmyemails.com/tools/dmarc-checker. See each tag of your record in plain English with the free DMARC parser at reviewmyemails.com/tools/dmarc-parser. To check one message, paste its headers into the free email header analyzer at reviewmyemails.com/tools/email-headers. A source you cannot place, or a failure you cannot fix? Ask the free SOS line at reviewmyemails.com/sos. A real person answers, with no pitch. Cleaning a list does not fix DMARC, so this one is a setup question, not a list question.
List cleaning does not fix SPF, DMARC, MX or blocklist problems. Those live in your sending setup, and they are a different job. A blocklist listing measures your sending, so it is never a reason to suppress anyone on your list. And nobody can promise you the inbox, so we do not.
Yanna-Torry Aspraki, Review My Emails
Email SOS Hotline, free
Stuck? We are here.
For those problems there is the Email SOS Hotline, our free help line. Tell Yanna-Torry what is going on and she will tell you what she would do. She reads every message herself and replies within 48 to 72 hours, with no pitch.
Ask the free SOS lineWords used
- DMARC aggregate report (RUA)
- the daily summary a mailbox provider sends you of the mail it saw from your domain
ruatag- the part of your DMARC record that says where the reports go
- Alignment
- the check that the domain which passed SPF or DKIM matches the From address readers see
- Disposition
- what the receiving server did with the mail:
none,quarantineorreject p=none- monitor mode. Failing mail is delivered as normal, and the reports keep coming
- Spoofing
- faking the sender details so a message looks like it came from you
- Forensic report (RUF)
- a copy of one failing message, sent close to real time. Gmail and most big providers no longer send them
Where this came from: the Review My Emails Email Almanac.
- What are the DMARC policies (p=none, p=quarantine, p=reject)?
- Where do I publish a DMARC record?
- What is the rua tag in DMARC (aggregate reports)?
- What is a DMARC aggregate report (RUA)?
- What is a DMARC forensic report (RUF)?
- What is DMARC alignment?
- When should I move to p=quarantine or p=reject?
- How do I read DMARC reports?
- How to read and visualize DMARC XML reports?
- What happens when DMARC fails?
- How often are reports sent?
- How do third-party senders authenticate under DMARC?
- What are common errors in DMARC records?
- Why DMARC “pass” doesn’t guarantee inboxing?
- How does DMARC interact with mailing lists?
- Why does alignment sometimes fail even if SPF/DKIM passes?
- How can I fix alignment issues?
- How does email forwarding break SPF?
- Can email forwarding break DKIM?
- How do mailing lists affect authentication?
- What happens with alias addresses under DMARC?
- How do I parse and analyze DMARC aggregate reports effectively?
- How do authentication failures affect DMARC aggregate scores?
- Can you have multiple DMARC records?
- How to detect hacked ESP or phishing abuse?
- What is DMARC Aggregate Reporting (RUA)?
- How do domain owners protect their reputation from spoofing?
- What is email spoofing?
- How can DMARC prevent domain spoofing?
- How can you identify a compromised sending domain?
Founded in 2020, based in Bolton, United Kingdom.
reviewmyemails.com/resources/how-to-read-a-dmarc-report?c=web-p10-r14pdf · v1