tmailrDeliverability · Headers
Email header analyzer
Paste the raw headers from a message and see the delivery path, how long each hop took, and whether the message was authenticated. Nothing is stored: the text is parsed and thrown away.
What the analyzer reads
Everything an email header trace can tell you
An email header is the record of how a message actually travelled and whether it was who it claimed to be. This analyzer turns that raw block into the delivery path, the timing, and the authentication a receiver recorded, so you can see the cause of a delay or a spam flag instead of guessing.
The delivery path
Each Received line is one server the message passed through. The analyzer orders them, times the gap between each hop, and flags where a message sat for minutes, which is usually where a delay or a greylist happened.
Authentication results
SPF, DKIM and DMARC exactly as the receiving server recorded them, plus the DKIM signing domains. This is where you see whether a message was really authenticated or only claimed to be.
What stands out
Plain-English notes on anything worth a second look: a hop with no TLS, a long delay, a failing check, a missing one-click unsubscribe. The findings point at the cause, not a number out of ten.
Questions people actually ask
Straight answers
What is an email header?
Every email carries a block of headers above the message you read: the Received lines that trace each server it passed through, the From, To and Subject, and the Authentication-Results that record SPF, DKIM and DMARC. Reading them is how you find out why a message was delayed, filtered or flagged as spoofed.
How do I find the raw headers of an email?
In Gmail, open the message, use the three-dot menu and choose "Show original". In Outlook, open the message and use File then Properties, or "View message source". Copy everything from the first Received line down and paste it here.
Do you store the headers I paste?
No. The text is parsed in one request and thrown away. Nothing is saved, logged to a profile or shared, which is why there is no account.
What can headers tell me that a deliverability score cannot?
The exact path a message took, how long each hop took, whether each hop used TLS, and the real SPF, DKIM and DMARC results a receiver wrote down. If a message was slow or spoofed, the headers show where and why; a score never will.