Map Extract
Free tool

Email header analyser

Paste the raw headers of a message and read them as a timeline. Every server hand-off is shown in order with its delay and whether it was encrypted, the authentication results are pulled into a table, and the tool explains in plain words whether SPF and DKIM lined up with the From address.

Runs in your browser. Nothing you enter is uploaded.

Analysing a message

  1. Get the headers

    In Gmail open the message, then More and Show original. In Outlook on the web choose View message details; in desktop Outlook use File, Properties and Internet headers.

  2. Paste them into the box

    Paste everything from the first Received line down. Three example sets (delivered and passing, failing DMARC, a slow unencrypted hop) are there if you want to see the output first.

  3. Read the four figures

    Total delivery time, number of hops, the SPF, DKIM and DMARC results, and whether each one aligned with the From domain.

  4. Check the warnings

    Anything worth acting on is listed above the timeline. If there is nothing, the page says no problems were found in these headers.

  5. Save a report

    Download a text or JSON report, or copy the text version to paste into a support ticket for your mail provider.

Example: a referral email that failed DMARC

A dog groomer (fictional) sent a referral offer to a vet practice through a bulk mail platform without setting up her own domain in the platform. The receiving server quarantined it.

SPF and DKIM both passed, but for the platform's domain, not hers, so neither aligned and DMARC failed. The delay warning comes from the 33 minutes the message spent inside the platform before leaving.

Input
Received: from mx-out.sendwave.example ... by mx.harbourvets.example with ESMTPS; Wed, 12 Nov 2025 10:04:51 +0000
Received: from app.sendwave.example ... by mx-out.sendwave.example with SMTP; Wed, 12 Nov 2025 09:31:12 +0000
Authentication-Results: mx.harbourvets.example; dkim=pass header.i=@sendwave.example; spf=pass smtp.mailfrom=bounces@sendwave.example; dmarc=fail (p=QUARANTINE) header.from=pinecrestgroom.example
From: Jess Moran <jess@pinecrestgroom.example>
Result
Delivery time: 33 min 46 s   Hops: 2   SPF, DKIM, DMARC: pass, pass, fail
Alignment: SPF not aligned, DKIM not aligned
Warning: DMARC failed: neither an aligned SPF pass nor an aligned DKIM pass was recorded for the From domain.
Warning: SPF passed for sendwave.example, which does not match the From domain pinecrestgroom.example.
Warning: One hop took more than five minutes, which usually means queuing or greylisting at that server.

Header lines the analyser reads

Received
Added by each server that handles the message, newest at the top. The analyser reverses them so the timeline reads from sender to recipient.
Authentication-Results
Written by the receiving server with its SPF, DKIM and DMARC verdicts. Results from an ARC-Authentication-Results line, added by forwarders, are shown but not used for the headline.
DKIM-Signature
The signature itself. The analyser lists each one's d= domain, s= selector and algorithm, which you can look up with the DKIM checker.
smtp.mailfrom
The envelope sender, also called Return-Path. SPF is checked against this domain, not the visible From.
header.from
The domain in the From address the reader sees. DMARC requires SPF or DKIM to pass for a domain that matches it.

Using headers to diagnose your own outreach

When a prospect says your email went to junk, ask them to forward it as an attachment, or send a test to a Gmail and an Outlook.com address you control. The receiving server's Authentication-Results line is the only first-hand record of how it judged the message, and it settles most arguments about whether a DNS change has taken effect.

The timeline helps with delays. A long gap between two hops points to the server that held the message: inside your sending platform it is usually queueing or throttling, at the recipient's side it is often greylisting, which retries resolve on their own.

Questions people ask

How do I view full email headers in Gmail?

Open the message, click the three dots next to Reply and choose Show original. Gmail shows a summary of SPF, DKIM and DMARC at the top and the full raw message below. Copy from the first header line down to the blank line before the body, or use Copy to clipboard, and paste it into the analyser.

What does DMARC fail mean if SPF and DKIM passed?

It means they passed for a different domain from the one in the From address. Sending platforms often use their own domain for the envelope sender and signature unless you set up custom domain authentication. DMARC needs at least one of the two to pass for your domain, or its organisational domain under relaxed alignment.

Why does my email take so long to arrive?

Compare the timestamps between hops in the timeline. The analyser warns when any single hop takes more than five minutes. Delays inside the sender's systems usually mean queuing or rate limits; delays at the receiving server often mean greylisting, where the first attempt is deliberately refused and accepted on retry.

Can headers be faked?

Lines added before a message reaches the receiving server can be written by anyone, including fake Received lines. The trustworthy parts are the lines added by the final receiving server, especially its Authentication-Results. That is why the analyser takes its verdicts from that line rather than from anything the sender included.

Where your data goes

Headers are parsed by script in this page. They can include names, addresses and internal server details, and none of that is uploaded: the analysis, the timeline and the downloadable report are produced on your device.

Checked against the tool on

Top