✓OutboundAuth
← All tools
Free tool · DMARC

DMARC report analyzer

DMARC aggregate reports are the XML files receivers send to your rua address every day. They name every server that sent mail as your domain — and which of it passed or failed. Paste one below and read it in plain English: legitimate senders, forwarders, and sources you should investigate.

Private by design. Your report never leaves your browser — the analysis runs entirely on this page. Nothing is uploaded, stored, or sent to any server, the same as every other OutboundAuth tool.

Analyse a report

Drop .xml or .xml.gz report files here
or use the file picker — you can select several reports at once.

Where do these reports come from?

If your DMARC record has a rua=mailto:… address, receivers like Google and Microsoft email you a zipped XML report roughly once a day for every day mail claims to be from your domain. Unzip the attachment (you'll get an .xml or .xml.gz file) and drop it above. No rua in your record? Add one and wait a day or two — the DMARC rollout guide shows the safe sequence.

How to read the results

  • Passing — legitimate sender. SPF or DKIM passes and lines up with your domain. These are your real senders — keep them.
  • Forwarding / mailing-list pattern. The mail authenticates as a different domain, so DMARC fails on alignment. Usually real mail being passed on — but it will be quarantined once you enforce, so decide if you accept it.
  • Failing both — suspicious, investigate. Neither SPF nor DKIM passes. A service you use with broken authentication — or someone spoofing your domain. This is the list to work through before moving from p=none to p=reject.

One report covers a day. Read a week or two of them before changing your policy — a sender that only mails on Mondays won't appear in a single day's file.

Don't want to read these yourself?

Monthly Monitoring includes your DMARC aggregate reports read for you — see who is sending as your domain, with alerts when something breaks.

WhatsApp Saqib See packages