DMARC report viewer
Open the DMARC aggregate reports that email providers send you, and see every server sending email as your domain – and whether its email passes SPF, DKIM and DMARC.
Reports are read on your device, in your browser – they’re never sent to our servers. To name the sending servers, the viewer looks up their IP addresses with Google Public DNS.
Sending servers
| Source IP | Server name | Messages | DMARC pass | SPF | DKIM | Applied policy | From domain |
|---|
SPF and DKIM show the authenticated domain and result; DMARC passes when either one passes and matches (aligns with) the From domain.
Reading the results
- Your own services failing (for example, a CRM or newsletter tool): set up DKIM signing with your domain in that service, or add it to your SPF record – then check again with our DNS record checker.
- SPF passes but DMARC fails: the service uses its own envelope (bounce) domain, so SPF doesn’t align. Set up DKIM with your domain instead.
- Forwarded email (university or alias forwarding) often fails SPF but keeps DKIM – that’s expected.
- Unknown servers failing everything are usually spoofing. Once all of your real sources pass, move your DMARC policy to quarantine and then reject.
A free tool provided by Auth-Email
Auth-Email makes your Gmail, Outlook, or other OAuth 2.0 email account available to any IMAP, POP3, or SMTP email client — no app passwords or special configuration needed.
Frequently asked questions
What is a DMARC aggregate report?
Email providers such as Google, Microsoft and Yahoo send daily XML reports to the address in your DMARC record’s rua= tag. Each report lists the servers that sent email using your domain, how many messages they sent, and whether those messages passed SPF, DKIM and DMARC.
Are my reports uploaded?
No. Reports are opened and analyzed in your browser, and can be compressed (.gz or .zip) or plain XML. The only information that leaves your device is the sending servers’ IP addresses, which the viewer looks up with Google Public DNS to show their names.
Why does a message pass SPF but fail DMARC?
DMARC also requires alignment: the domain that passes SPF (the envelope sender) or DKIM (the d= domain) must match the domain in the From address. Email sent by a service using its own envelope domain passes SPF, but not for your domain.