Free tool · 04 / SEND
DMARC report reader.Who sends as your domain, and why they fail, no signup.
Reads a DMARC aggregate report: who sends as your domain, and why each one fails.
Runs in your browser. Nothing you type is sent to us.
An example: a made-up day of reports for a made-up domain. Reports arrive as .xml.gz or .zip attachments: open one and paste the .xml inside.
- Messages
- 1,066
- Passed DMARC
- 76.2%
- Failing sources
- 2
google.com saw 1,066 messages from 3 sources using yourcompany.example: 76.2% passed DMARC, 254 failed.
| Source IP | Messages | DMARC | Why | Receiver did |
|---|---|---|---|---|
| 192.0.2.10 | 812 | Pass | DKIM aligned and SPF aligned | none |
| 198.51.100.7 | 240 | Fail | DKIM passed for sendgrid.net, not yourcompany.example; SPF passed for em123.sendgrid.net, not yourcompany.example | none |
| 203.0.113.50 | 14 | Fail | Neither SPF nor DKIM passed | none |
- Policy p=none. RFC 9989: "The Domain Owner offers no expression of preference."
- What the receiver did: none for 1,066.
- One source passed SPF or DKIM, but for another domain, so DMARC failed (240 messages). If it's a service that sends for you, set it up to sign with DKIM, or send, as your own domain.
- One source passed neither SPF nor DKIM (14 messages). If you don't recognise it, someone else may be sending as your domain.
The report is read in your browser. Naming the senders sends only their IP addresses to our reverse DNS lookup, which keeps nothing.
Valley sends from your own Gmail or Microsoft inbox, so its mail shows up in these reports as your own. See how Valley does it ↗
NEXT STEP
Fed up with fixing authentication instead of filling the pipeline.The other half is who, and what you say.
Book a demo ↗$500 a month for your first seat, $200 for each seat after that.
Inside a report
What's in a DMARC aggregate report?The XML elements, as RFC 9990 defines them.
A DMARC aggregate report is an XML file a receiving mail system sends a domain owner. It names the reporting organization and the period covered, repeats the domain's published policy, and lists each sending IP with how many messages it sent, how DMARC, DKIM and SPF evaluated, and what the receiver did.
| Element | What it holds |
|---|---|
| report_metadata / org_name | Name of the Reporting Organization |
| date_range / begin, end | The reporting period, in seconds since the epoch, UTC |
| policy_published | The domain's published DMARC policy: domain, p, and optional sp, adkim, aspf |
| row / source_ip | The connecting IP address |
| row / count | Number of messages for which the policy_evaluated was applied |
| policy_evaluated / disposition | The result of applying the DMARC policy |
| policy_evaluated / dkim, spf | The DKIM and SPF results that count for DMARC: aligned with the From domain |
| identifiers / header_from | The RFC5322.From domain from the message |
| auth_results / dkim, spf | The raw DKIM and SPF results, with the domain each one was for |
From RFC 9990: DMARC Aggregate Reporting ↗ · RFC 7489, Appendix C: DMARC XML schema (the earlier format) ↗, read 16 Nov 2026
How it works
How this tool works.And what it can't see.
Paste the XML from one aggregate report. It's read in your browser, whichever format it uses: RFC 9990's or the earlier RFC 7489's, with or without a namespace. Nothing is sent anywhere.
Each sending IP is listed by message count with its DMARC result. A message passes when its aligned DKIM or aligned SPF result passed, which the report gives under policy_evaluated. For each failing source, the raw results say why: SPF or DKIM passed for another domain, so it didn't align with yours, or nothing passed at all.
Name the senders, if you like: it sends up to ten IP addresses to our reverse DNS lookup, which returns each one's host name, the quickest clue to which service it is. It keeps nothing.
What it can't see: messages from receivers that don't send reports, and the content of any message. Aggregate reports carry counts and results only.
Built by Valley.
Sources
- RFC 9990: DMARC Aggregate Reporting ↗read 16 Nov 2026
- RFC 9989: Domain-Based Message Authentication, Reporting, and Conformance (DMARC) ↗read 16 Nov 2026
- RFC 7489, Appendix C: DMARC XML schema (the earlier format) ↗read 16 Nov 2026
DMARC reports
Turn DMARC reports into fixes.Who's sending, and what each one needs.
Every receiver that reports sends you a daily list of who used your domain. Here's how to read it.
- 01
Passing means aligned
RFC 9989 says a message passes DMARC if one or more of its authenticated identifiers align with the author domain, the one in the From line. So SPF or DKIM passing isn't enough: it has to pass for your domain. The report's policy_evaluated results are the aligned ones; auth_results shows what passed for which domain.
From RFC 9989: Domain-Based Message Authentication, Reporting, and Conformance (DMARC) ↗ · RFC 9990: DMARC Aggregate Reporting ↗, read 16 Nov 2026
- 02
Two kinds of failing source
A source that passed SPF or DKIM for another domain, such as a mail service's own, didn't align: if it's a service you use, set it up to sign with DKIM, or send, as your domain. A source that passed nothing at all is either something misconfigured or someone sending as you without permission.
From RFC 9989: Domain-Based Message Authentication, Reporting, and Conformance (DMARC) ↗, read 16 Nov 2026
- 03
From p=none to reject
RFC 9989 describes p=none as the domain owner offering no expression of preference, quarantine as considering such mail suspicious, and reject as a clear indication that use of the domain name is not valid. The reports show what each policy would catch before you tighten it.
From RFC 9989: Domain-Based Message Authentication, Reporting, and Conformance (DMARC) ↗, read 16 Nov 2026
- 04
Getting at the XML
RFC 9990 says the aggregate data must be an XML file that should be compressed with GZIP, with the file extension xml or xml.gz. Many receivers send .zip files instead. Open the attachment, and paste the .xml file's contents here.
Once every source passes, the mail lands. Who it goes to, and what it says, decides the rest. See how Valley does it ↗
From RFC 9990: DMARC Aggregate Reporting ↗, read 16 Nov 2026
Questions
Questions people ask.
- What is a DMARC aggregate report?
- An XML file a receiving mail system sends a domain owner, listing every IP that sent mail as the domain, how many messages, and how they did on DMARC, DKIM and SPF.
- How do I read a DMARC report?
- Open the .xml.gz or .zip attachment and paste the XML here. You'll see each source, its DMARC result and why it passed or failed.
- Why does DMARC fail when SPF passes?
- SPF passed for a different domain from the one in the From line, so it doesn't align. DMARC needs SPF or DKIM to pass for your domain.
- What does p=none mean in a DMARC report?
- RFC 9989 says it means the domain owner offers no expression of preference: receivers report failures but aren't asked to act on them.
- Why are DMARC reports compressed?
- RFC 9990 says the XML should be compressed with GZIP, so reports usually arrive as .xml.gz files; some receivers send .zip files.
- Who sends DMARC aggregate reports?
- Receiving mail systems that support DMARC reporting, to the address in your DMARC record's rua tag. The reporting organization is named in each report.
- Is this DMARC report reader free?
- Yes. It's free, needs no signup and reads the report in your browser.
Keep going
Try one of these next.
- DMARC record generatorEmail outreachWrites a DMARC record to RFC 9989, with report addresses, alignment and test mode.Open the tool
- SPF, DKIM and DMARC checkerEmail outreachChecks a domain's SPF, DKIM and DMARC records against Gmail and Yahoo's sender rules.Open the tool
- Reverse DNS lookupEmail outreachFinds an IP's PTR record and checks it resolves back to the same IP, as Gmail requires.Open the tool
- WHOIS lookupEmail outreachAny domain's registration record: registrar, dates, status, name servers and owner.Open the tool
- Cold email domain finderEmail outreachSending domain ideas close to your brand, each checked against its registry.Open the tool