Read reports, not a live mailbox
Make your DMARC reports readable
Choose local files or paste one XML report. Nothing is sent to a server for analysis.
Choose XML, GZ or ZIP files
One XML report per ZIP. No nested or encrypted archives, additional files or extraction to disk.
Up to 10 UTF-8 reports, 4 MiB per source file and per expanded XML, 16 MiB per batch before and after expansion. All size, row and XML-structure limits apply together.
Processing limits
At most 64 ZIP entries including directories; 5,000 rows per report and 10,000 across the batch. XML depth is limited to 24 and the combined parser-node/event count to 150,000. Each leaf text value, comment, attribute value and element local name is limited to 4,096 UTF-16 units. The local job has a twelve-second deadline.
Choose reports you want to understand.
Count the evidence in the reports
Totals use the message counts declared in the included records. They are not a count of unique emails sent or proof of delivery.
No API, DNS lookup, signature verification, IP reputation lookup or mailbox connection is performed.
No history, saving, copy or export. Hiding or leaving this page clears its working files, text and analysis. This does not erase your original files, clipboard or every browser-memory copy.
Keep authentication and alignment separate
Understand the reported outcome
Analyze reports to see weighted alignment totals, dispositions and the source IPs behind them.
Load the public example first to explore the report without private files.
Reported disposition
Disposition and alignment answer different questions. Neither proves that a message reached an inbox.
A report is a receiver's observation
The reader summarizes supplied files. It does not prove who owns an IP, whether a report is authentic or whether your current DNS settings are correct.
Equal repeated report identities are counted once when their parsed content matches. Conflicting copies stop the batch; overlapping periods remain visible as a warning.
Inspect the rows behind the totals
Source IPs and reported records
View a supplied XML report
Plain source text, not an editable report or an independent schema certificate. Report metadata may be private.
The whole batch is interpreted locally. A report's coverage, overlapping observations and policy declarations must remain part of your investigation.