● Runs locally. Your headers never leave this page.

Email Header Analyzer

Paste the raw headers of an email to see the route it took, how long each hop took, the SPF, DKIM, DMARC and ARC results, and anything that looks off.

How to get the raw headers

  • Gmail: open the message → ⋮ menu → Show original → copy everything.
  • Outlook (web/new): open the message → ⋯ → View → View message details.
  • Outlook (classic desktop): open the message → File → Properties → Internet headers.
  • Apple Mail: View → Message → All Headers (or Raw Source).
  • Thunderbird: View → Message Source (Ctrl+U).

Reading the results

Received headers are added by each server the message passes through, newest on top. The analyzer reverses them so you read the path from the sender to your mailbox, and works out the delay between hops from their timestamps. Large delays usually mean greylisting, queueing or a slow filter. Timestamps that go backwards mean clock skew or forged headers.

Authentication-Results is written by the receiving server and holds its SPF, DKIM and DMARC verdicts. Only the topmost one, from your own provider, can be trusted. Anything below it could have been added by the sender.

Alignment matters. DMARC passes only if SPF or DKIM passes and the domain involved matches the visible From domain. That's why the analyzer flags a Return-Path or DKIM d= domain that differs from From.

FAQ

Is it safe to paste email headers here?

Yes. The analysis runs entirely in your browser with JavaScript, it's never sent anywhere, and the page's Content-Security-Policy blocks requests to any third party. Headers often include internal hostnames, IPs and addresses, which is why this tool never uploads them.

Why does SPF pass but DMARC fail?

SPF checks the envelope sender (Return-Path), not the From address you see. If the Return-Path domain doesn't align with the From domain and there's no aligned DKIM signature, DMARC fails even though SPF passed.

Which Authentication-Results header should I trust?

Only the topmost one added by your own mail provider. Any Authentication-Results lower down could have been inserted by the sender or an intermediate server, and shouldn't be trusted.

What does a large delay between hops mean?

Usually the message sat in a queue: greylisting, a busy outbound relay, spam or antivirus scanning, or a retry after a temporary failure. Delays of seconds are normal; minutes to hours point to the server shown in that hop.