DMARC XML Report Analyzer
Import an aggregate report locally to identify reporting receivers, observed sources and authentication outcomes.
Run a diagnostic
Accepted: DMARC aggregate XML (.xml) or gzip-compressed XML (.xml.gz). ZIP is not supported.
Report files remain in your browser; no reports are uploaded by these workflows.
Email headers stay in your browser. Public DNS results may be cached for 5 minutes. Public DNS TXT checks may use Google Public DNS when the server resolver returns no TXT records. Email headers are not sent to that DNS service.
How to interpret this result
Import an aggregate report locally to identify reporting receivers, observed sources and authentication outcomes.
No. Reports cover only participating receiving systems and their reporting intervals; enforcement estimates are illustrative.
No sample results are used for your scan.
Evidence this tool can evaluate
Import receiver-generated DMARC aggregate XML to inspect message counts, source IPs, reported authentication results and published policies. Missing evaluation evidence stays unknown rather than being counted as failure.
What to do with the findings
Verify report dates and reporting organizations, identify legitimately used senders, and investigate alignment failures before moving from monitoring to quarantine or reject. Reports are not a complete inventory.
Need continuous authentication protection?
Method and limitations
Read real DMARC aggregate XML and examine source IPs, authentication alignment and quarantine or reject scenarios. Public DNS checks cannot prove inbox delivery or message-level authentication.
Frequently asked questions
Does a DMARC report include every message sent?
No. Reports cover only participating receiving systems and their reporting intervals; enforcement estimates are illustrative.
Educational diagnostics, not a guarantee of deliverability or provider approval.