An email message carries a hidden record of its journey: every server it passed through, the authentication checks it underwent, and the addresses it claims to come from. The Email Header Analyzer reads that record and turns it into a readable summary, an authentication section, a delivery path, and a full header table, all processed locally in your browser with nothing uploaded. It is the essential tool for checking a suspicious message, debugging a delivery problem, or learning how email really works.
Email headers look intimidating because they are long, technical, and full of unfamiliar field names. The analyzer does the tedious work: unfolding wrapped lines, extracting the fields that matter, and presenting the Received chain in order. This article explains how to get the raw headers from your mail app, how to use the analyzer, how to read each section, and what the results can and cannot prove about a message.
What Is the Email Header Analyzer Tool?
The Email Header Analyzer is a free online tool that parses raw email headers pasted into a text area and presents the findings in four parts. First, a summary table shows the key fields: From, Reply-To, To, Subject, Date, Return-Path, Message-ID, and the sender application from X-Mailer or User-Agent, where present. Second, an authentication section lists any Authentication-Results headers, which record the SPF, DKIM, and DMARC verdicts, with guidance on reading pass, fail, and none results. Third, a delivery path section lists the Received headers in order, newest first, with an explanation of how to read the chain. Fourth, a full table lists every header found, with a count, so nothing is hidden from inspection.
All analysis happens in your browser. The tool field help states this explicitly: nothing is uploaded, and analysis happens locally. That privacy property matters, because headers can contain addresses and server details you may not want to send to a third-party service. The tool also handles the technical detail of unfolding: headers that wrap across multiple lines, with continuation lines starting with a space or tab, are joined back into single logical lines before parsing, so wrapped values are read correctly. Lines without a colon are ignored, and if no headers are found at all, the tool explains that you may have pasted the message body instead of the header block.
Headers are metadata, not the message body. They record who the message claims to be from, who should receive replies, when it was sent, which servers handled it, and what authentication checks the receiving server performed. They do not include the message text, attachments, or images. Understanding headers is therefore about understanding provenance and handling, not content, and the analyzer is designed around exactly that distinction.
How to Use the Email Header Analyzer Tool
- Get the raw headers from your mail app. In most mail apps, open the message and choose “Show original,” “View source,” or “View message source” from the message menu. Copy the header block, which is the text at the top, before the blank line that separates headers from the body. The tool help text gives this guidance on the page.
- Paste the headers into the text area. In the “Raw email headers” field, paste the full header block. The area is large, with room for long header sets, and you can paste the whole original view; the tool will parse the header lines and ignore lines that do not form headers.
- Press Analyze Headers. If the field is empty, the tool asks you to paste headers first. If no headers are found, it explains that the pasted text may be the body rather than the header block, and reminds you what header lines look like, such as “From:” and “Subject:”.
- Read the summary table. The “Email header summary” table shows each key field that was present, with its value. Compare From, Reply-To, and Return-Path: in legitimate mail they usually align, while in phishing they often diverge, with replies directed to a different address than the displayed sender.
- Read the authentication results. If Authentication-Results headers exist, they are listed with guidance to look for spf=pass, dkim=pass, and dmarc=pass, and a caution that a single fail or none does not by itself prove fakery, but combined fails are a warning sign. If no such header exists, the tool says so and explains that SPF, DKIM, and DMARC results cannot be shown.
- Read the delivery path. The Received chain is listed newest first, as an ordered list. The last entry is usually the first server that handled the message, closest to the real sender. Compare its domain with the From address: a mismatch is a common phishing sign, as the tool explains.
- Review the full header table. The final table lists all headers found, with the total count in its heading. Use it to check fields the summary omits, such as X-Originating-IP where present, content-type details, or unusual custom headers.
Because nothing is uploaded, you can safely analyze headers containing sensitive addresses on a shared computer, with the usual caution that the pasted text remains visible on screen until you clear it or leave the page. The tool keeps no history and sends no data anywhere.
Key Features of the Email Header Analyzer Tool
- Key-field summary. From, Reply-To, To, Subject, Date, Return-Path, Message-ID, and sender application are extracted into one readable table, so the essential facts do not require scanning the raw text.
- Authentication results display. SPF, DKIM, and DMARC verdicts are shown exactly as the receiving server recorded them, with plain guidance on interpreting pass, fail, and none.
- Received chain in order. The delivery path is presented as an ordered list, newest first, with an explanation of how to find the originating server and what a mismatch suggests.
- Complete header table. Every parsed header is listed with its name and value, and the count is shown, so the analysis is transparent and auditable against the raw input.
- Header unfolding. Wrapped continuation lines are joined correctly before parsing, so long values split across lines are read as single values.
- Fully local and private. No upload, no server, no storage. The analysis runs entirely in your browser, which is the right design for potentially sensitive header data.
- Helpful error messages. Empty input and body-only pastes produce specific guidance about what to paste and where to find it, rather than a generic failure.
Practical Use Cases
Checking a suspicious or phishing message
A message claiming to be from a bank, a delivery service, or a colleague deserves a header check before any link is clicked or any reply is sent. The analyzer lets you compare the From display name with the actual From address, check whether Reply-To points elsewhere, read the authentication verdicts, and trace the Received chain to the originating server. A message claiming to be from a known company but originating from an unrelated server, failing authentication, and directing replies to a free mailbox is almost certainly fraudulent. The header evidence is far more reliable than the message appearance, which attackers can copy perfectly.
Debugging delayed or missing email
When a message arrives hours late, the Received chain shows the timestamp at each hop, revealing where the delay occurred: at the sender server, at an intermediate relay, or at the receiving server. When a message never arrives, the sender headers from a test message show how far delivery progressed. Support teams use these timestamps to identify the slow or failing hop, and the Message-ID provides the reference to search server logs.
Verifying authentication setup
Domain owners who configure SPF, DKIM, and DMARC need to confirm the records work in practice. Sending a test message to a mailbox, viewing its headers, and checking the Authentication-Results section shows the real verdicts from a receiving server. A DKIM fail may indicate a signing problem, an SPF fail may indicate a missing sending server in the record, and a DMARC fail with both underlying fails indicates an alignment problem. The analyzer makes these verdicts readable without searching raw text.
Investigating spoofed sender addresses
Attackers can forge the From address easily, because the original email design trusted the sender claim. Authentication and the Received chain are the checks that expose forgery: a forged message usually fails SPF or DKIM, or originates from a server unrelated to the claimed domain. The analyzer presents both pieces of evidence together, which is what makes the spoofing visible. A message that passes all three authentication checks and originates from the claimed domain servers is very likely genuine, although no check is absolute.
Learning how email delivery works
Students and junior administrators learn more from one real header set than from many diagrams. The Received chain shows the actual path a message took, the timestamps show real transit times, the authentication section shows real verdicts, and the full table shows the variety of headers modern mail systems add. Analyzing headers from several providers side by side shows how implementations differ while following the same standards.
Tips and Best Practices
- Always check headers before trusting a suspicious message. Display names, logos, and formatting are trivially faked. Headers and authentication verdicts are much harder to fake convincingly.
- Compare From, Reply-To, and Return-Path together. Legitimate bulk mail sometimes uses a different Return-Path, but a Reply-To pointing to an unrelated free mailbox, combined with a mismatched origin server, is a strong warning.
- Read the last Received entry for the origin. The chain is newest first, so the last entry is the first hop. Its domain and address are the closest evidence to the real sender, although the earliest entries can themselves be forged by the sender.
- Treat combined authentication fails seriously. One fail can have innocent causes, such as forwarding breaking SPF, but combined SPF, DKIM, and DMARC fails on a message claiming to be from a major sender are a strong fraud signal.
- Do not reply or click while investigating. Keep the suspicious message isolated, analyze its headers, and report it through your mail provider phishing report function if the evidence points to fraud.
- Preserve the original for reporting. When reporting phishing to an abuse team, include the full original headers, because the team needs the same evidence you analyzed. Forwarding as an attachment preserves headers better than forwarding inline.
Limitations
The analyzer parses and presents headers; it does not verify them independently. It does not re-run SPF, DKIM, or DMARC checks against DNS, does not look up the reputation of the sending servers, and does not inspect links or attachments in the body. The authentication verdicts it shows are those recorded by the receiving server, which are trustworthy only if that server itself is trustworthy, and the earliest Received entries can be forged by a malicious sender, since each server adds its own entry and the first entry is written by the sender infrastructure.
The tool also cannot prove a message is safe. A message can pass authentication and still be a scam, for example if the attacker controls the sending domain, and a legitimate message can fail a check because of forwarding or misconfiguration. Headers are evidence to weigh, not a verdict machine. For a complete assessment, combine header analysis with link inspection, sender verification through a separate channel, and your mail provider spam and phishing filters, and treat any single signal with appropriate caution.
Frequently Asked Questions
Where do I find the raw headers in Gmail, Outlook, or Apple Mail?
In Gmail, open the message, click the three-dot menu, and choose Show original. In Outlook, open the message and use the message options or View message source command, depending on the version. In Apple Mail, choose View, then Message, then Raw Source or All Headers. In each case, copy the header block at the top.
Is it safe to paste headers into this tool?
Yes, because the analysis runs entirely in your browser and nothing is uploaded. The tool states this on the page. Headers can contain email addresses and server names, so avoid pasting them into tools that upload data, but this tool keeps everything local.
What do SPF, DKIM, and DMARC mean?
SPF checks whether the sending server is authorized by the domain DNS record. DKIM checks a cryptographic signature proving the message was signed by the domain and not altered. DMARC ties the two together with alignment rules and a policy for failures. Together they make sender forgery much harder.
Why is there no Authentication-Results header?
Some mail systems do not add one, especially older systems, internal relays, or messages that bypassed authentication. Its absence means the verdicts cannot be shown, not that the message failed. The Received chain and sender comparison remain useful in that case.
Can headers prove an email is fake?
They can provide strong evidence, such as a forged origin, failed authentication, and a mismatched Reply-To, but no single header proves fakery on its own. Weigh the combined evidence, and verify important claims through a separate channel, such as contacting the supposed sender directly.
What is a Message-ID?
It is a unique identifier assigned to the message by the sending system, used to track the message in logs and to thread replies. Support teams use it to find a specific message in server logs, and duplicate Message-IDs across supposedly different messages can indicate forgery or a mailing fault.
Related Tools
These tools help investigate the domains and servers named in headers.
- DNS Lookup – check the SPF, DKIM, and DMARC records for a domain.
- Website IP Finder – find the addresses behind a domain in the headers.
- Whois Lookup – planned tool for domain registration details.
- What Is My IP Address – see your own address for comparison.
- DNS Propagation Checker – compare DNS answers for a sender domain.