Home / Free tools / Email header analyzer
Email header analyzer: check SPF, DKIM and DMARC
Paste the headers of an email to see whether it passed SPF, DKIM and DMARC, whether the domains line up for DMARC, who signed it and the path it took, with the delay at each hop. Then look up the sender's SPF, DKIM and DMARC records in one click.
Where to find them: Gmail - open the message, More (three dots), Show original. Outlook - open the message, File, Properties, Internet headers (new Outlook and the web: More actions, View, View message source). Apple Mail - View, Message, All Headers. Pasting the whole message works too; only the headers are read.
How to read the result
| Check | What it proves | Counts for DMARC when |
|---|---|---|
| SPF | The sending server's IP is allowed by the envelope sender's domain (Return-Path). | The Return-Path domain matches the From domain (same organisational domain). |
| DKIM | A domain signed the message and the signed parts were not changed on the way. | The signing domain (d=) matches the From domain. |
| DMARC | SPF or DKIM passed and lined up with the From domain the reader sees. | - |
The result badges come from the Authentication-Results header that the receiving server added at the top: that
server did the checks when the message arrived. This page cannot check the DKIM signature itself, because that needs the full
message body as it arrived; it reads the receiving server's verdict and looks up the published records.
Common problems it finds
- SPF passes but DMARC fails. The mail service sends with its own Return-Path (bounce) domain, so SPF is not
aligned, and it signs DKIM with its own domain too. Set up DKIM for your domain in the service (a CNAME or TXT record at
selector._domainkey). - SPF permerror. More than 10 DNS lookups (
include,a,mx...), or twov=spf1records on one domain. The DNS check counts the lookups through every include. - No DKIM signature, or a revoked or 1024-bit key.
- DMARC
p=none: reports only, spoofed mail is still delivered. - A slow hop: the delay column shows where the minutes went (greylisting, a queue, a filter).
For the full go-live check with PowerShell commands, read the guide check SPF, DKIM and DMARC before go-live.
Questions
Are the headers I paste sent anywhere?
No. The headers are read by JavaScript in your browser and are not sent to our server, logged, stored or put in a URL or analytics. Only the optional DNS lookup goes out: your browser asks Cloudflare's public DNS resolver (Google's if that fails) for the TXT records of the domains, and only the domain names are sent.
Why does SPF pass but DMARC fail?
DMARC needs SPF or DKIM to pass for the same domain as the From address. Mail services often send with their own bounce domain (Return-Path), so SPF passes for their domain, not yours. Turn on DKIM signing for your domain in the service so DKIM is aligned.
Can this page verify the DKIM signature?
Not by itself: a DKIM signature covers the message body as it arrived, which headers alone do not contain. The page shows the receiving server's DKIM result from Authentication-Results, the signing domain and selector, and looks up the published key.
Which Authentication-Results header counts?
The top one, added by the server that delivered the message to your mailbox. Headers lower down were added by earlier servers or by the sender and can be forged, so the page uses the top one.
How many DNS lookups can an SPF record have?
Ten. include, a, mx, ptr, exists and redirect each count, including the ones inside included records. Past ten, receivers return permerror and SPF fails. The DNS check here counts them through every include.
How do I test the email my app sends before it goes live?
Send it to a test inbox instead of real customers and check it there, headers included. MailPier Inbox gives each test or staging environment hosted inboxes for that; the SPF, DKIM and DMARC guide covers the DNS side.
Something wrong or missing? Mail support@solutionsgroupunlimited.com. More free tools: SQL login script generator, cron expression builder, GUID / UUID generator. How-to articles: Guides.
Sources: RFC 8601 (Authentication-Results), RFC 7208 (SPF), RFC 6376 (DKIM), RFC 7489 (DMARC), Cloudflare DNS over HTTPS (JSON).