Email header analyzer
Read the headers of an email to see where it came from, why it was late and whether the sender's checks passed.
More in Email · Reports
What the analyzer shows
Every server that handles an email adds a line called Received to the top of its headers. Read from the bottom up, those lines are the route of the message. The analyzer lists them oldest first, works out the time between each pair and marks the step where most of the wait happened.
The receiving server also writes an Authentication-Results line that says whether the message passed SPF, DKIM and DMARC. The analyzer shows those results as written, checks whether the sending domain matches the From domain (the alignment that DMARC needs) and compares the From, Return-Path and Reply-To addresses.
- The route: each server, its address, the protocol, whether the hop used TLS and the delay at each step.
- The checks: SPF, DKIM, DMARC and ARC as recorded by the receiver, with the alignment worked out from the header.
- The people: who the message claims to be from, where replies go, and whether the display name, the address and the reply address agree.
- The signs of forgery: a display name that names another address, a look-alike Reply-To domain, or a failed DMARC check that was delivered anyway.
What happens to what you paste
Headers hold names, addresses and the network addresses of people, so this page is built to keep them to itself. With JavaScript on, the headers are read inside your browser and nothing is sent anywhere. We do not store the header and we do not put it in the page address, a link or a statistic.
Some extras need our servers, so they are off until you ask. After the headers are read, a card lists exactly what each lookup would send: the public address of a mail server, or a domain name. Only the items you tick leave the page, and the header never does.
To check DKIM signatures themselves you need the whole message, because the signature covers the body. Drop the .eml file on the page and the check runs in your browser. It asks DNS for the public key of each signature and sends only that DNS name, for example s2026-11._domainkey.shop.example.com.
How to get the headers
Every mail program hides the headers by default. Look for the option called Show original, View source, Message details or Internet headers, and copy everything from the top down to the first blank line. You can paste the whole message too: only the top part is read.
- GmailOpen the message, choose the three dots next to Reply, then Show original. Choose Copy to clipboard and paste it here.
- Outlook on the webOpen the message, choose the three dots, then View, then View message details. Copy the text in the box.
- Outlook for WindowsDouble-click the message to open it, choose File, then Properties. Copy the text under Internet headers.
- Apple MailSelect the message, choose View, then Message, then All Headers or Raw Source. Copy the text at the top.
- Yahoo MailOpen the message, choose the three dots, then View raw message. Copy the lines at the top.
- ThunderbirdOpen the message, choose More, then View Source, or press Ctrl+U. Copy the lines at the top.
- Proton MailOpen the message, choose the three dots, then View headers. Copy the text.
Reading the result
The answer at the top is one sentence. "Looks normal" means the checks passed and nothing in the route stands out. "Worth a closer look" means a check failed or an address does not match. "Likely forged" means several signs point the same way; it is a reason to be careful, not proof.
A long delay at one hop usually means a scan or a greylisting wait at that server. The header shows when each server received the message but not why it waited, so the page says where the time went and never guesses the cause. Clocks that run slightly behind are counted as zero seconds.
Only the top Authentication-Results line is trusted, because it was written by the server that delivered the message to you. Lower ones were written by earlier servers and anyone in the chain can forge them. The analyzer says which server wrote the one it trusts.
Questions people ask
Is my email kept anywhere?
No. With JavaScript the headers are read in your browser and never sent. Without JavaScript they go to our server for that one request, are shown back to you and are not stored, logged or cached. There is no link to share a result, because a link would have to hold the header.
Where do I find the headers of an email?
Open the message and look for Show original, View source, Message details or Internet headers. The page lists the steps for Gmail, Outlook, Apple Mail, Yahoo Mail, Thunderbird and Proton Mail.
Why was my email delayed?
The route shows the time between each pair of servers. A big jump at one hop is typically a spam or virus scan or a greylisting delay at that server. The header cannot say which, so the page names the step and leaves the cause open.
How can I tell if an email is forged?
Look for a failed SPF or DMARC result, a Return-Path or Reply-To on a different domain, and a display name that claims a bank or brand the address does not belong to. One sign alone can be innocent. Several together are worth treating as a forgery: do not click links or reply.
What do SPF, DKIM and DMARC mean here?
SPF says the sending server is allowed to send for a domain. DKIM says a signature from the domain matches the message. DMARC asks for one of them to pass and to match the From domain. The analyzer shows the result the receiver wrote and whether the domains line up.
Why does it say DKIM is reported by the receiver?
A DKIM signature covers the body of the message, which a header paste does not include. To check the signature here, drop the whole .eml file on the page. The check runs in your browser and sends only the DNS name of each public key.
Can it check the sending server or domain further?
Yes, if you tick it after the result. You can look up the public mail server addresses (network, country, name and blocklists) and the domain checks (DMARC policy and DKIM keys). Only the addresses or names you tick are sent.
Use it from AI, the API or the command line
Every LookupOwl tool is also a free API and an MCP tool, with no key and no account. This one is email_header_analyze. Please be kind to the rate limits.
curl "https://lookupowl.com/api/v1/tools/email-header-analyze"claude mcp add --transport http lookupowl https://lookupowl.com/mcp