Paste a raw email header to trace its full delivery route — every server hop, the delay between hops, TLS usage, and the SPF/DKIM/DMARC results recorded by the receiving provider.
Paste the complete header block or the full message source below.
Results will appear here after you analyze a header block.
Private by design: your pasted headers are parsed entirely in your browser and are never uploaded, logged or stored.
Copy the raw headers (or the complete message source) from your email client — in Gmail use “Show original”, in Outlook use “View message source” — and paste them into the box. You can also load our sample to see what a parsed result looks like.
The header block is unfolded and structured with an open-source MIME parser that runs entirely on your device. Nothing is uploaded, stored or sent to any server.
See every server hop with delays between them, the SPF/DKIM/DMARC outcomes the receiving provider recorded, sender-domain alignment observations and anything that looks inconsistent.
Validate the SPF record that authorizes which servers may send for a domain.
Open toolCheck a domain’s DMARC policy, reporting addresses and alignment modes.
Open toolScan subject and body copy for wording that commonly triggers spam filters.
Open toolCheck whether an email address is valid before you add it to a sequence.
Open toolIt turns a raw header block into a readable report: who the message claims to be from, every mail server that handled it (the Received chain), how long each handoff took, whether TLS was used between hops, and which SPF, DKIM and DMARC outcomes the receiving provider recorded.
No. It reads the Authentication-Results header that the receiving server wrote when the message arrived. Those values are that server’s recorded claims; they are not recomputed here, and they can be absent or misleading in a forged message. To validate the underlying DNS records, use our SPF, DKIM and DMARC checkers.
No. The analysis runs entirely in your browser with an open-source parser. Nothing you paste is transmitted, logged or stored, which makes the tool safe for headers that contain real addresses or internal server names.
That is often normal — mailing lists and email service providers route bounces through their own domains, and teams sometimes route replies elsewhere. We flag the mismatch as an observation, not a verdict, because the same pattern also appears in spoofed mail.
Yes. A sender controls everything in the message before it reaches your provider, including Received lines and even Authentication-Results headers from servers you do not control. Only the hops added by servers you trust — typically the top-most ones — are reliable.
In Gmail open the message and choose “Show original” from the three-dot menu. In Outlook, open the message and look under “View message source” or File → Properties. In Apple Mail, choose View → Message → All Headers. Copy the entire block and paste it here.
Automate Sales Outreach & Get Booked!
Start Free Trial(14 Day Free Trial, No CC Required)