Email Header Analyzer — Trace Every Hop
Paste the full headers of an email to see the route it took, how long each hop took and whether it passed SPF, DKIM and DMARC. Analysis runs entirely in your browser.
How to get the full email headers
- Gmail: open the message → ⋮ menu → Show original → Copy to clipboard.
- Outlook (web): open the message → … → View → View message source.
- Outlook (desktop): double-click the message → File → Properties → copy Internet headers.
- Apple Mail: View → Message → All Headers (or Raw Source).
- Yahoo Mail: open the message → … → View raw message.
What the analyzer shows
- Delivery path — every
Received:header in order, from the sender’s server to your inbox, with the delay at each hop. Long delays point to greylisting, queues or throttling. - Authentication — SPF, DKIM and DMARC results from the receiving server’s
Authentication-Resultsheader, plus the DKIM selector and signing domain. - Key fields — From, Return-Path, Reply-To, Message-ID, subject and date, with warnings when From and Return-Path domains differ.
- Spam scores — X-Spam and Microsoft anti-spam headers when present.
Private by design
Headers can contain email addresses and internal server names, so this tool never uploads them. Everything is parsed by JavaScript in your browser; close the tab and it’s gone.
Reading the results
If SPF fails, check your record with the SPF checker. If DKIM fails, verify the key with the DKIM checker using the selector shown. If the first hop shows your own server and it is slow or rejected, test your SMTP server directly.
Frequently asked questions
Read Received: headers from the bottom up: the lowest one is the first server that handled the message, the top one is your mail provider. The analyzer does this for you and lays the hops out in order with timings.
Yes. The analyzer runs entirely in your browser and the headers are never sent to our server. You can disconnect from the internet after the page loads and it will still work.
Look for the hop with the largest delay. A delay at the first receiving server often means greylisting (a deliberate temporary rejection). Delays inside one provider usually mean queueing or spam scanning. Clock differences between servers can also show small negative or odd delays.
Check the Authentication-Results: a genuine message from a domain with DMARC should show dmarc=pass. Also compare the From domain with the Return-Path and DKIM d= domains, and look at the first external Received hop — it should belong to the sender’s known mail provider.