DKIM Record Checker
Validate a DKIM public key and read its real key size.
Read a message header: route, delays and auth results.
The Email Header Analyzer lays out raw message headers: the Received chain reversed into travel order with the delay at each hop, the SPF, DKIM and DMARC verdicts, and every other header listed.
Raw headers are where the answer is when a message was slow, went to spam, or was not from who it said it was — and they are unreadable until something lays them out.
Paste them and the Received chain is reversed into the order the message actually travelled, hop by hop, with the server at each end and the delay between them, so a message that sat somewhere for four minutes shows exactly where.
The Authentication-Results header is read out separately: SPF, DKIM and DMARC each with their verdict, which is the first thing to check when mail is being filtered. Every other header is listed as well, with the ones that matter — From, Return-Path, Reply-To, Message-ID, List-Unsubscribe — pulled out first.
Headers can contain a great deal about who you correspond with, which is a good reason to read them in a tool that cannot send them anywhere. This one runs entirely in your browser.
Received headers reversed, so it reads the way the mail went.
Find the server that sat on the message for four minutes.
SPF, DKIM and DMARC verdicts pulled out on their own.
Continuation lines are unfolded before parsing, as the RFC requires.
Headers say who you correspond with, and stay in the tab.
In Gmail: the three-dot menu, then Show original.
The whole block — folded lines are joined for you.
Each hop in travel order, with the delay at each one.
SPF, DKIM and DMARC verdicts, read out separately.
In Gmail, open the message, click the three-dot menu and choose Show original. In Outlook, File then Properties, and read the internet headers box. In Apple Mail, View, Message, then Raw Source.
Because each server adds its own to the top as the message passes through. The last one added is the final hop, so reading them bottom-up gives the route the message actually took — which is the order this tool shows them in.
That the receiving server confirmed the message came from a server the domain authorises, that its signature verified, and that the authenticated domain aligned with the visible From address. All three passing is what you want to see.
No. They are parsed in your browser, which matters because headers carry a lot about who you correspond with and through what.
What people who use the Email Header Analyzer think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the Email Header Analyzer. It takes half a minute and no account.
Write the first reviewValidate a DKIM public key and read its real key size.
Find the info@, admin@ and sales@ addresses in a list.
Compare two lists: in both, only in one, only in the other.
Check a mailto: link and every address and field in it.
Remove duplicates, including the ones Gmail hides.
Check any address for syntax, typos and risk.
Flag the addresses that look like traps before you send.
Score any address out of 100 and see what moved it.