Email Header Analyzer
🔒 In your browserTrace an email's delivery path, hop delays and SPF/DKIM/DMARC results.
How it works
Paste the raw headers of an email to trace its delivery path hop by hop, see where time was lost, and read the receiving server's SPF, DKIM and DMARC verdicts. In Gmail use "Show original"; in Outlook, "View message source".
Try an example
🔒 Parsed entirely in your browser — the headers you paste are never uploaded.
🔒 Runs in your browser: records, keys and headers are processed locally and never uploaded — including DKIM private keys, which never leave this device.
About the Email Header Analyzer
Every email carries a trail of headers recording each server it passed through. This free email header analyzer turns that trail into a readable delivery path — showing each hop, how long it took, and the receiving server's SPF, DKIM and DMARC verdicts.
It's the fastest way to answer 'why was this email delayed?' or 'is this message really from who it claims?'. Headers are parsed entirely in your browser and never uploaded.
How to get the raw headers
- Gmail — open the message, ⋮ menu, then 'Show original'.
- Outlook — File, Properties, and copy the Internet headers box.
- Apple Mail — View, Message, then 'All Headers'.
Reading the result
Received headers are added by each server as the message travels, newest first — we reverse them so you read the journey in order. A large gap between two hops points at where the delay happened. The Authentication-Results header holds the receiver's own SPF, DKIM and DMARC verdicts, which is the definitive answer on whether the message was authenticated.
Frequently asked questions
How do I read email headers?
Paste the raw headers here and the tool reconstructs the delivery path in chronological order, with per-hop delays and the authentication results extracted for you.
How do I find where an email was delayed?
Look down the hop list for the largest delay. That hop is where the message sat, which usually identifies the responsible server.
Can I tell if an email is spoofed?
Check the SPF, DKIM and DMARC results. If DMARC fails, or the Return-Path domain doesn't match the visible From address, treat the message with suspicion.
Are my headers uploaded?
No. Parsing happens entirely in your browser — important, since headers contain your address and routing details.