SPF Sender Policy Framework
A DNS list of servers allowed to send for a domain. It checks the hidden bounce (Return-Path) domain, so it only helps DMARC when that domain is yours.
DMARC human reader · online
Upload the DMARC aggregate report you received from Google, Microsoft or Yahoo. We unpack it, read every record, and show who is sending as your domain, what passes, what fails — and what you can do about it.
Free · no signup · unpacked in a temporary folder and deleted immediately — nothing is stored
DMARC report
Each sender groups the IP addresses that belong to the same service. Open one to see every IP, its hostname, and how SPF and DKIM were evaluated.
Ordered by severity. Each problem says what we saw, why it usually happens, whether you as the domain owner can fix it, and the steps to take.
How it works
Drop the .zip or .gz you received at your rua address — no need to unpack it. Several reports at once are merged into one view.
The server unpacks it in a private temporary folder, reads every record, looks up who owns each sending IP, and deletes the folder.
Every sender is classified — authenticated, misconfigured service, forwarding, or spoofing — with the cause and the fix you can apply.
Reading the report
DMARC passes when either SPF or DKIM passes and its domain matches the domain people see in the From address. That matching is called alignment.
A DNS list of servers allowed to send for a domain. It checks the hidden bounce (Return-Path) domain, so it only helps DMARC when that domain is yours.
A cryptographic signature added by the sending server. It survives forwarding, which makes it the most reliable way to pass DMARC.
The SPF or DKIM domain must match the visible From domain. Relaxed (r) allows subdomains; strict (s) requires an exact match.
none only monitors. quarantine asks receivers to send failing mail to spam. reject asks them to refuse it.
What the receiver actually did with the message: delivered (none), sent to spam (quarantine) or refused (reject).
The daily XML summary receivers send to the address in your rua tag. It contains counts and results — never message content.
FAQ
It is an XML file that mailbox providers such as Google, Microsoft and Yahoo send to the address in your DMARC record's rua tag. It lists every IP address that sent mail using your domain during a period, how many messages each sent, and whether SPF, DKIM and DMARC passed.
The .zip files Google sends, the .gz (gzip) files Microsoft, Yahoo and others send, and plain .xml reports. Up to 10 files at once, 10 MB each.
No. The file is unpacked in a private temporary folder on the server, read, and the folder is deleted before the result is returned. Nothing is kept or logged. The exports are generated in your browser.
DMARC needs alignment. Services such as newsletter or CRM platforms send with their own bounce domain, so SPF passes for them, not for you. Set up custom DKIM signing (and ideally a custom Return-Path) in that service and DMARC will pass.
You cannot stop people from trying to forge your domain, but a policy of quarantine or reject tells receivers to junk or refuse those messages. Fix every legitimate sender first, then move from p=none to p=quarantine and p=reject.
This reader handles aggregate (rua) reports, which are what nearly all providers send. Forensic reports are individual message samples and are rarely sent today.
Run a full scan for SPF, DKIM, DMARC, SSL and blacklists — and get an A–F trust score.
Scan a domain