Email header analyser

Paste an email's headers. See who really sent it.

Copy the headers of any email you have received and paste them in. We tell you in plain English which server sent it, whose name it was signed in, and whether it passed SPF, DKIM and DMARC as the domain in its From address.

The page cuts your paste at the end of the headers, so the message itself never leaves your browser. We read the headers once and keep nothing.

  • Reads the headers only
  • No account, nothing to install
  • Nothing is kept

How to find an email's headers

Pasting the whole message is fine: the page keeps the headers and sends nothing after them.

What the result tells you

Who really sent it

The server that handed the email to your mail service, and the mail service or network that server belongs to.

What your mail server recorded

The SPF, DKIM and DMARC results your own mail server wrote when the email arrived. A line the sender wrote into its own email is set aside.

What happens to a fake

Whether the domain asks inboxes to refuse an email faked in its name, send it to junk, or deliver it anyway.

The route it took

Each server the email passed through, in order, with the time at each and which lines are the sending side's own account.

An example: an email that claims to be from harbourview.example, sent from a server that domain does not approve. The sender put a ready-made pass into its own email, and it was set aside.

Example data

These headers did not pass DMARC as harbourview.example

✕ Fail

harbourview.example asks inboxes to refuse email like this. Treat it as a fake unless you know why it failed.

The headers you pasted: "Invoice 2291 is overdue", from harbourview.example.

Sent from 198.51.100.24 on Example Hosting's network.

Received by mx.northquay.example.

  • ✕ Fail

    SPF

    Failed. The server that sent it (198.51.100.24) is not on harbourview.example's list of approved senders.

  • ✕ Fail

    DKIM

    Not signed. Nothing vouches that this email really came from harbourview.example.

  • ✕ Fail

    DMARC

    Failed. Neither SPF nor DKIM passed as harbourview.example, so receivers cannot tell this email apart from a fake.

  • ✓ Pass

    Spam blocklist

    The server that sent it is not on the Spamhaus blocklist.

If harbourview.example is your domain and this email is yours: what to change

  1. Add the service that sent this to harbourview.example's SPF record. The service publishes the line to add, usually starting "include:".
  2. In your mail service's settings, set up DKIM for harbourview.example. It is often called domain authentication or a branded sending domain: it gives you records to add to your DNS, and from then on it signs as harbourview.example.

The SPF, DKIM and DMARC results are the ones mx.northquay.example recorded when it received the email.

We set aside 1 result line in the paste that we could not tie to the receiving server. A sender can put any line it likes into its own email.

The route it took

Each server an email passes through adds a line. The first hop is at the top.

The route these headers record, first hop first
HopHanded over byReceived byWhenNetwork
110.0.4.17as the sending side describes itmail.parcel-notice.example9 Nov 2026, 09:14:05 UTCNot known
2mail.parcel-notice.example (198.51.100.24)mx.northquay.example9 Nov 2026, 09:14:07 UTC2 seconds laterExample Hosting

Questions

What is an email header?

The lines every mail server adds as an email travels. They record which servers handled it and which checks it passed. Mail apps hide them, and the steps on this page show where to find them.

Can I tell whether an email is fake from its headers?

They show whether it passed DMARC as the domain in its From address. A pass proves the domain and nothing about the sender's intentions, so read the domain letter by letter: a look-alike domain with good records passes too.

Do you read the message itself?

No. The page cuts your paste at the end of the headers before anything is sent, so what the email says never leaves your browser. We read the headers once and keep nothing. To check them we look up the domains and the sending server they name in public DNS.

Why does my own email fail?

The rows say which check failed, and the list under them says what to change. To have a signature checked properly, send the same email to the email tester.

Why does the result say it was worked out from DNS?

The headers held no result from your mail server that we could rely on, so we checked the sending server against the domain's records as they are now. A line the sender wrote into its own email is never counted.

What do SPF, DKIM and DMARC mean?

SPF lists the servers allowed to send email for a domain. DKIM is a signature the sending service adds, which shows the email was not changed on the way. DMARC ties both to the From address you see, and tells inboxes what to do with email that fails.

Each of the three in more depth: SPF, DKIM and DMARC explained.

Start with the free check.

It reads your SPF, DKIM and DMARC records in about 30 seconds, and tells you where you stand today.