Every email carries a hidden trail: the headers record each server it passed through, who it claims to be from, and whether the sending domain's SPF, DKIM and DMARC checks passed. A spoofed email often looks perfect in the inbox but fails those checks or shows a Reply-To address that points somewhere else entirely. This analyzer reads that trail and explains what it means — without uploading anything.
How to use
- In your mail app, open the suspicious message and choose “Show original” (Gmail) or “View message source” (Outlook, Apple Mail, Thunderbird).
- Copy the header block — the lines at the top, before the message body.
- Paste it here and press “Analyse headers”.
- Read the authentication results, the hop trace and the warnings.
About this email header analyzer
The analyzer parses the header block line by line, joining folded lines, then extracts the sender fields (From, Reply-To, Return-Path, Subject, Date), the Authentication-Results line that your mail provider added (SPF, DKIM and DMARC pass/fail), and every Received hop with its sending server, receiving server, IP address and timestamp. It then cross-checks the domains: if replies would go to a different domain than the claimed sender, or the bounce address does not match, it warns you. All of this happens locally in your browser — the headers never leave your device.
How do I use this tool?
- Paste the raw headers into the box (or press “Load sample headers” to see how a clean result looks).
- Click “Analyse headers”.
- Check the SPF/DKIM/DMARC line first, then the warnings, then the hop list.
- Use “Clear” to wipe the headers when you are done.
Where is this tool used?
On an email claiming to be from your bank, a delivery company or a government office; on an invoice you were not expecting; on a message whose sender name looks right but whose address looks wrong; and when reporting a phishing email — the hop trace and authentication results are exactly what an IT team or abuse desk asks for. Pair it with the phishing link checker before touching any link in the message.
What are the limitations?
Headers show what servers recorded, and a determined attacker can forge some header lines — only the Authentication-Results added by your own mail provider and the DKIM signature are hard to fake. A passing SPF/DKIM/DMARC result means the message really came from that domain, but a genuine domain can still be abused (a compromised account, or a lookalike domain that passes its own checks). And headers cannot judge the message content: a perfectly authenticated email can still carry a malicious link, so check links separately.
Frequently asked questions
How do I get the raw headers of an email?
In Gmail, open the message, click the three dots and choose “Show original”. In Outlook, open the message and choose “View message source”. In Apple Mail, choose View → Message → Raw Source. Copy the header block at the top — not the body.
What do SPF, DKIM and DMARC actually check?
SPF checks whether the sending server is authorised by the domain. DKIM checks a cryptographic signature proving the message was not altered in transit. DMARC ties the two together and states what should happen when they fail. A pass on all three means the message genuinely came from the claimed domain.
What is the biggest red flag in headers?
A Reply-To address on a different domain than the From address — replies, and often your trust, go to the attacker. A DMARC failure on a message claiming to be from a bank is a close second.
Is it safe to paste headers here?
Yes — headers are parsed entirely in your browser and nothing is uploaded or stored. Paste headers only, not the message body or attachments, and do not click links in the suspicious email while you check it.
The headers pass but the email still feels wrong. What now?
Trust the feeling. Check any link with the phishing link checker, verify the request through the service's real app or website, and call the organisation on a number from its official site — never one printed in the email.
Updated November 2026 · Built and tested by Sharjeel Tahir · How our tools are tested