Tool guide limitationsGuides explain the intended workflow but cannot cover every device, provider or operating condition.
Interfaces and external services can change. Follow the current on-screen controls, check dates and vendor documentation, and verify important results independently before acting on them.
Important: Do not rely on this result alone for purchasing, configuration, security, safety, compliance, contractual or fault-diagnosis decisions. Results can be incomplete, delayed, misleading or wrong. Verify important findings with the relevant provider, manufacturer documentation and an appropriate independent test or qualified professional.
DNS and email
DMARC Report Reader guide
Read aggregate DMARC XML reports locally and summarise authentication outcomes.
Open DMARC Report ReaderWhat you need
- DMARC XML, ZIP or GZIP aggregate report
How to use it
- 1Select the report file.
- 2Allow local parsing to finish.
- 3Review source counts and SPF/DKIM alignment.
- 4Export the summary if required.
Understanding the results
- Failures grouped by source help identify unauthorised or misconfigured senders.
Recommended next actions
- Correlate unknown sources with authorised platforms before changing DMARC policy.
Common problems
- Malformed archives, forensic reports or vendor-specific XML may not parse.
Privacy and security
- Reports are processed in the browser but can contain domains and source IP addresses.
Worked example
- Scenario
- Reviewing yesterday's aggregate report
- Example input
- example.com!receiver!date.xml.gz
- How to read it
- A source with high volume and DKIM alignment failure becomes a candidate for sender configuration review.
Limitations
- One report covers only its stated receiver and reporting period.
Do not rely on one result for a production, security, safety, purchasing or contractual decision. Verify important findings independently.