Skip to main content
InboxkitSign up free

Free tool

Free Email Header Analyzer

Paste raw message headers to check them. The analyzer reads the Authentication-Results line for SPF, DKIM and DMARC, rebuilds the route from every Received header in order with the timestamp at each hop and the total delivery time, and pulls out the From, To, Subject, Date and Message-ID. Free, instant, and nothing you paste is stored.

In Gmail: Open email → Three dots menu → Show original → Copy headers

How to use the email header analyzer

  1. 1

    Copy the raw headers

    Open the message in your mail client and copy the full header block. In Gmail that is the three-dot menu, Show original, Copy to clipboard. The table further down covers Outlook, Apple Mail and Yahoo.

  2. 2

    Paste them into the Email headers box

    Paste the complete header block, including every Received line: the route is rebuilt from those. Click Load Example to see a sample first.

  3. 3

    Click Analyze Headers

    The headers are parsed in a single request and the results replace the form. Nothing is saved.

  4. 4

    Read the results top to bottom

    Authentication Results shows SPF, DKIM and DMARC. Email Routing Path lists each hop with the total delivery time. Email Metadata, Security Warnings and Recommendations follow. Click New Analysis to check another message.

What this header analyzer checks

Every result comes straight from the header lines you paste. The analyzer does not look anything up in DNS, so it tells you what the receiving server decided, not what your records say today.

CheckWhat it readsWhat you see
SPF, DKIM and DMARCThe spf=, dkim= and dmarc= results in the Authentication-Results headerThe result word for each (pass, fail, softfail, neutral, none and so on). Pass is green, anything else is red, and a missing result shows Not found
Routing pathEvery Received header, reordered oldest first so hop 1 is where the message startedNumbered hops with the server that handed the message on, its timestamp and protocol (ESMTPS, ESMTP, SMTP or HTTP)
Delivery timeThe timestamps on the first and last hopTotal time in seconds next to the routing path heading
Encryption in transitTLS or ESMTPS in each Received lineA TLS badge on each encrypted hop, and a warning if no hop was encrypted
Message detailsFrom, To, Subject, Date and Message-IDThe Email Metadata panel
Warnings and recommendationsThe checks above, the hop count and any X-Spam-Score headerA warning for each failed or missing SPF, DKIM or DMARC result, a note when there are more than 10 hops (usually forwarding or relays), and a flag when X-Spam-Score is above 5

Example: email header analysis of a message that passed

Here is a trimmed header block from a cold email sent by sam@example.org to jane@example.com. The Received lines read newest first, the way every mail client shows them.

Received: from mx.example.com (mx.example.com [192.0.2.25])
        by mailstore.example.com with ESMTP id 8kQ2Ff1n7mY;
        Tue, 14 Oct 2025 16:12:09 +0000
Received: from mail.example.org (mail.example.org [198.51.100.24])
        by mx.example.com with ESMTPS id 4mB7cT0xQz
        (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384);
        Tue, 14 Oct 2025 16:12:06 +0000
Received: from laptop.local (unknown [203.0.113.7])
        by mail.example.org with ESMTPSA id 4F2C81A0B2;
        Tue, 14 Oct 2025 16:12:04 +0000
Authentication-Results: mx.example.com;
        spf=pass smtp.mailfrom=example.org;
        dkim=pass header.d=example.org header.s=s1;
        dmarc=pass header.from=example.org
From: Sam Lee <sam@example.org>
To: jane@example.com
Subject: Quick question about Q4 hiring
Date: Tue, 14 Oct 2025 16:12:03 +0000
Message-ID: <4F2C81A0B2@mail.example.org>

What the analyzer reports

HopServerTimestampProtocolWhat happened
1laptop.local16:12:04ESMTPS, TLSThe sender's mail client submits the message to its own server over an authenticated, encrypted connection (ESMTPSA)
2mail.example.org16:12:06ESMTPS, TLSThe sending server hands off to the recipient's MX over TLS 1.3. This is the hop SPF is checked against
3mx.example.com16:12:09ESMTPAn internal hand-off inside the recipient's system to the mailbox store

How to read authentication failures in a header

The same message, passed through a forwarder that added a footer to the body and relayed it from its own IP, comes out like this:

Authentication-Results: mx.example.com;
        spf=softfail (domain of example.org does not designate 192.0.2.80 as permitted sender) smtp.mailfrom=example.org;
        dkim=fail (body hash did not verify) header.d=example.org header.s=s1;
        dmarc=fail (p=QUARANTINE) header.from=example.org

The analyzer shows all three cards in red with the results softfail, fail and fail, adds a warning for each, and recommends reviewing SPF, DKIM and DMARC. Here is what each result means and where to look.

spf=softfail

The IP that delivered the message is not listed in the SPF record for the smtp.mailfrom domain, and the record ends in ~all, so the receiver accepted it but marked it as suspect.

Usual causes: a new sending tool that was never added to SPF, or a forwarder or list relaying from its own IP. If the IP belongs to you, add its include to the record and confirm it with the SPF checker. The SPF softfail guide walks through the fix.

dkim=fail (body hash did not verify)

The signature was found, but the body that arrived no longer matches the body hash (bh=) in the DKIM-Signature. Something changed the message after it was signed.

Usual causes: a list footer, a security gateway rewriting links, or a disclaimer added on the way out. The Received chain shows which servers touched it after the signing hop. A result such as signature verification failed instead points at the key, usually a rotated selector; see DKIM setup.

dmarc=fail

DMARC passes only when SPF or DKIM passes and its domain aligns with header.from. Fail means neither did. Here both failed outright; just as often SPF passes for a sending platform's bounce domain and DKIM is signed with the platform's d=, so nothing aligns with your From.

Compare header.from with smtp.mailfrom and header.d in the same line. The p= value is the policy the receiver applied: QUARANTINE usually means the spam folder. Set up a custom return-path or DKIM signing on your own domain to fix alignment.

What each email header field means

A full header block has thirty or more lines. These are the ones that answer the questions people bring to a header analyzer: who really sent this, did it authenticate, and where did the delay happen.

HeaderWhat it tells you
ReceivedOne line per server hop, newest at the top. The chain is the route, and the timestamp gap between lines is the delay at that hop
Return-PathThe envelope sender that bounces go to. SPF is checked against this domain, not the From address
From and Reply-ToThe visible sender and where replies go. A Reply-To on a different domain is a common phishing tell
Authentication-ResultsThe receiving server's verdict on SPF, DKIM and DMARC, with the domain each check used
Received-SPFThe SPF result and the IP it evaluated, written by the first receiving server
DKIM-SignatureThe signing domain (d=), selector (s=), signed headers (h=) and the signature itself
ARC-Seal and ARC-Authentication-ResultsAuthentication results carried across forwarders and mailing lists so DMARC can still pass
Message-IDA unique ID set by the sending system. Use it to find the message in provider logs
X-Mailer, X-Originating-IP and other X- headersNon-standard headers added by clients and filters. Useful hints, never proof

The analyzer reads Authentication-Results, the Received chain and the From, To, Subject, Date and Message-ID lines; the rest are worth reading by eye in the raw block. A message that passed SPF and DKIM but failed DMARC almost always has an alignment problem, which the DMARC checker confirms on the domain; a missing DKIM result points to the DKIM checker.

How to find email headers in Gmail, Outlook and Apple Mail

Every client hides the raw headers somewhere different. Copy the whole block, including the blank line at the end, and paste it into the analyzer above.

ClientWhere the headers are
Gmail (web)Open the message, click the three-dot menu, choose Show original, then Copy to clipboard
Outlook (web)Open the message, click the three-dot menu, choose View, then View message source
Outlook (desktop)Open the message in its own window, then File, Properties. The headers are in the Internet headers box
Apple MailOpen the message, then View, Message, All Headers. Raw Source shows the full message
Yahoo MailOpen the message, click More, then View raw message
iPhone and Android mail appsNot exposed in the apps. Open the same message in webmail or a desktop client

If the result shows an authentication failure on your own domain, the fix is in DNS, not in the message: the SPF, DKIM and DMARC guide explains which record to repair, and the 550 5.7.1 guide decodes the bounce that usually arrives with it.

FAQ

Frequently asked questions

It turns a raw header block into something readable. This one pulls the SPF, DKIM and DMARC results from the Authentication-Results header, lists every Received hop in order from first server to last with its timestamp, protocol and TLS status, works out the total delivery time, and shows the From, To, Subject, Date and Message-ID.

In Gmail, open the message, click the three-dot menu and choose Show original. In Outlook on the web, use the three-dot menu, View, View message source. In Outlook desktop, open the message in its own window and go to File, Properties. In Apple Mail, choose View, Message, All Headers. Mobile mail apps do not show headers, so open the message in webmail instead.

Find the Authentication-Results header, which the receiving server adds. It contains spf=, dkim= and dmarc= followed by the result, plus the domain each check used: smtp.mailfrom for SPF, header.d for DKIM and header.from for DMARC. Paste the headers into the analyzer and it shows the three results side by side, with a warning for any that failed or are missing.

The IP that delivered the message is not authorized in the SPF record of the envelope sender domain, and that record ends in ~all, so the receiver accepted the message but treated it as suspect. It usually means a sending service was never added to SPF, or the message was forwarded and arrived from the forwarder's IP.

The body that arrived does not match the hash stored in the DKIM signature, so something changed the message after it was signed. Mailing list footers, security gateways that rewrite links, and disclaimers added by an outbound server are the usual causes. Check the Received chain for servers that handled the message after the signing server.

The sending server was authorized for the envelope domain, but the DKIM signature did not verify. The usual causes are a message modified in transit (a mailing list or security gateway rewriting the body), a rotated key whose DNS record was removed, or a selector that never published. If DMARC still passes, SPF alignment carried it; if not, fix DKIM first.

Each server that handles a message adds a Received line at the top, so the bottom line is where the message started and the top line is the last hand-off. Each line names the server it came from, the server that received it, and a timestamp after the semicolon. The analyzer reverses the list so hop 1 is the origin. A hop shows Unknown when its Received line has no from part, which is common for the final internal hop at Gmail.

Some can. A sender controls every header they write, including From, Reply-To, Date and any Received lines added before the message is handed off. What cannot be faked are the headers your own provider adds after that point: its Received line, Received-SPF and Authentication-Results. Read from the top down and trust only the hops you recognise.

It is free with no signup and no limit on checks. The headers you paste are sent to Inboxkit's server, parsed in memory and returned as the analysis. They are not saved.

Need complete email infrastructure?

Inboxkit provides everything you need for guaranteed deliverability and security monitoring