Free tool · Message analysis

Free Email Header Analyzer

Paste the raw headers of any email to see the route it took, where it was delayed, and whether it passed SPF, DKIM and DMARC. The analysis runs in your browser and nothing you paste is uploaded.

Your headers stay in your browser. The analysis runs on this page. Nothing you paste is sent to InboxSure or to any other server, and nothing is stored.

You can paste a whole raw message: everything after the first blank line is ignored.

The example is made up: it uses reserved example domains and documentation IP addresses.

How to get the raw headers

Mail apps hide the full header by default. These are the menu paths for the common ones; the complete walk-through, with every app and a worked example, is in how to read email headers.

Mail appWhere to find the headers
Gmail (web)Open the message, click More (three dots) next to Reply, then Show original.
Outlook.com, Outlook on the web, new Outlook for WindowsOpen the message, select More actions, then View, then View message details.
Classic Outlook for WindowsDouble-click the message to open it in its own window, click File, then Properties, and copy the Internet headers box.
Apple Mail (Mac)Select the message, then choose View, Message, All Headers.
Yahoo Mail (web)Open the message, click the More icon, then View Raw Message.

Copy everything from the first line down to the blank line before the message text and paste it into the box above. If you paste the whole raw message, the analyzer stops at that blank line by itself.

How to read the result

Summary

The From, To, Subject, Date, Message-ID, Return-Path and Reply-To lines. The Return-Path is the address that receives bounces and the domain SPF is checked against. A Reply-To on a different domain from the From address is pointed out because it is worth noticing, not because it is wrong: support desks and newsletters do it all the time.

Route

Every Received line becomes a numbered hop, oldest first, with the server that handed the message over (from), the server that accepted it (by), the protocol and the timestamp. The gap between two hops shows where time was lost. A gap of more than five minutes is flagged and usually means a server deferred the message and the sender retried. A negative gap is clock skew between two servers. Received lines do not follow one fixed format, so a line the analyzer cannot split is shown exactly as it was written.

Authentication

The Authentication-Results header records what the receiving server decided about SPF, DKIM, DMARC and ARC. Only the topmost copy, written by your own mail provider, can be trusted: a sender can add copies of their own lower down, which is why the analyzer shows the server name on each one. Below it you will find every DKIM-Signature with its domain and selector, which you can look up in the DKIM checker.

The alignment box answers the question DMARC asks: does the domain that passed SPF or DKIM belong to the same organization as the From domain? To decide that, the analyzer compares the last two labels of each domain, or the last three for a short built-in list of suffixes such as co.uk and com.au. That is a heuristic. Receivers use the full Public Suffix List, so treat the alignment verdict for an unusual suffix as a hint.

Provider details

When the headers include Microsoft 365's X-Forefront-Antispam-Report, the analyzer shows the fields Microsoft documents, with Microsoft's own wording. SpamAssassin's X-Spam-Status score, the List-Unsubscribe headers and the number of ARC sets are listed when present. Headers that start with X- are not standardised, so the analyzer does not guess at fields the vendor has not described.

Privacy

Email headers contain addresses, server names and IP addresses, and sometimes more than you intended to share. This page parses them with JavaScript in your browser. The text you paste is not uploaded, logged or stored, and it is gone when you close or reload the page. If you are going to forward the result to someone, remove recipient addresses first when the message is not yours to share.

What a header cannot tell you

A header is a delivery record for one message that arrived. It does not show whether a message is honest, so this tool does not label anything as phishing or safe. It also says nothing about messages that bounced, because a rejected message never reaches a mailbox and leaves no header to read. If test messages look clean here but campaigns still bounce, the cause is usually the list and not authentication: addresses that no longer exist. Verifying a list before sending removes those addresses.

Frequently asked questions

Verify your list before you send

InboxSure checks every address with syntax, MX and SMTP mailbox checks, and flags catch-all, role-based and disposable addresses. Free to start.