Free DMARC report viewer
Turn DMARC aggregate XML reports into a readable list of sending sources, authentication results and receiver actions. Upload the files you already receive. No account required.
Files are read in memory on our server while you wait, and nothing from them is kept.
No report handy? Download a synthetic DMARC XML report and upload it above. It uses example domains and documentation IP addresses, with no customer data.
Where do I find DMARC reports?
Look in the mailbox your DMARC record’s rua= address points to. Participating receivers commonly send daily reports as .xml.gz or .zip attachments after receiving mail that uses your domain. Timing and coverage vary.
What the XML analyzer shows
Review sending sources, message counts, SPF and DKIM alignment, and the actions reported by receivers. SecureMark names recognized services and shows unfamiliar sources for investigation. A report contains observed activity, not proof that every source is authorized.
No reports yet?
Your domain may not request aggregate reports, or they may go to another mailbox or monitoring service. Check your DMARC record and confirm the reporting destination with your DNS administrator.
An example: SPF passes, but DMARC fails
A message from example.com might pass SPF using a return-path domain owned by its sending provider. That SPF result does not align with example.com. If there is no passing, aligned DKIM signature either, the message fails DMARC.
The synthetic sample contains 125 messages: 100 pass through aligned DKIM, 20 pass SPF for an unaligned domain and fail DMARC, and 5 fail both checks. Its policy is p=none, so a failing message can have a reported disposition of none. That disposition does not mean authentication passed or that the message reached the inbox.
How to read the results
- Check the domain and dates. Reports cover a particular receiver and period. Use a range that includes regular and occasional sending services.
- Identify legitimate sources. Confirm unfamiliar senders with your team or client. Forwarding and shared infrastructure can complicate the picture.
- Investigate alignment failures. Compare the authenticated SPF and DKIM domains with the From domain, then review that service’s setup.
- Review policy carefully. Resolve legitimate failures before requesting quarantine or reject. Historical results cannot guarantee future delivery.
Files, privacy and ongoing monitoring
The viewer accepts aggregate XML reports directly or inside gzip and ZIP files. It identifies duplicate reports so uploading the same report twice does not double its message counts. Unsupported files and parsing problems are listed in the results.
Aggregate reports describe sending IPs, message counts and authentication outcomes, not message bodies. Files are processed in memory on our server and are not retained. See our privacy policy for the wider service’s data handling.
For ongoing monitoring, SecureMark collects reports over time and helps you follow changes in sending sources and authentication. Compare monitoring plans, or see how agencies manage reports for client domains.