Paste an email header to see its SPF, DKIM and DMARC results, the servers it passed through and signs of spoofing. Free, no sign-up.
The pasted text is analyzed only in this browser and is never sent to our server. To check the sender, only the domain names from From (and Reply-To), plus the sending server's IP address and domain for an SPF re-check, are sent. The same IP address is also looked up on our server to show its network operator and registered country (it is not sent to any outside service).
The Email Header Analyzer is a free tool that reads the header of a message you received and shows its authentication results (SPF, DKIM, DMARC), the servers it passed through and signs of spoofing. Use it when you are unsure whether an email is genuine.
The analysis runs in your browser. A header contains recipient addresses and IP addresses, but the pasted text is never sent to our server. Only the domain names and the sending server's IP address needed to check the sender and re-check SPF are sent. The IP address is also used to show the network (ASN), registered country and reverse DNS name, using data held on our own server; it is not sent to any outside IP-information service.
The verdict has three levels: strong signs of spoofing, possibly spoofed, and no clear signs. If there is not enough information, it says so. The main signals are:
| Signal | Meaning |
|---|---|
| DMARC fail | The sender's (From) domain could not be authenticated as genuine. The strongest signal. |
| SPF / DKIM pass, but not for From | Authentication passed, but for a different domain than From. The classic way attackers pass with a domain of their own. |
| Reply-To is an unrelated free-mail address | The sender is a company domain, but replies go to someone's free mailbox. |
| Display name and domain disagree | The display name shows another domain or a brand name to look genuine. |
| More than one From header | Sometimes used to slip past authentication. |
| SPF re-check disagrees with the recorded result | The receiving server recorded SPF as pass, but today's SPF record does not allow the sending IP. The header may have been altered, or the SPF record changed. |
| Timestamps go backwards in the route | Clock drift or forged routing information. |
We also re-check on the server whether the sending server's IP address is allowed by the sending domain's SPF record (SPF basics). This uses today's DNS, not the DNS at delivery time, so treat it as a hint.
The sender's domain is also checked with the same rules as the Phishing Check, together with its registration age and DMARC policy.
Is the pasted header stored?
No. The analysis runs entirely in your browser; the header is neither sent to nor stored by this site. Only domain names, and the sending server's IP address read from the header, are looked up to check the sender and re-check SPF. The IP address is also used to show its network and registered country, using data on our own server rather than an outside service.
It says "Not enough information".
That appears when no Authentication-Results header from the receiving server was found. Copy the full header via "Show original" or similar, not just the few fields shown when you open the message.
A legitimate email shows "Possibly spoofed — be careful".
Mail sent through a mailing service, a mailing list or a forwarder can have a Return-Path or SPF that does not match From. If DMARC passes, it is usually fine. Mail through a mailing list or forwarder can fail DMARC because the message was modified, but if ARC is pass the original authentication succeeded.
My own mail fails DMARC.
Typical causes are a sending service missing from SPF, or DKIM not set up for it. Check your domain with the DMARC Check.