Skip to content

How to Read Email Headers: Step-by-Step Guide for Senders

Email headers show who really sent a message and why it landed in spam. Here is how to read them, line by line.

Abedrahim B Nov 14, 2026 5 min read 1,180 words
How to Read Email Headers: Step-by-Step Guide for Senders

Every email carries a hidden log. Knowing how to read email headers lets you see who sent a message, which servers touched it and whether it passed authentication. For anyone who sends cold email, it is the fastest way to find out why a message went to spam.

This guide walks through the header fields that matter, in the order you should read them. You do not need to be an engineer. You only need the raw message source and ten minutes.

How to read email headers: a step-by-step guide
How to read email headers: a step-by-step guide

What email headers are#

An email has two parts. The body is what the reader sees. The header is a block of text lines above it. Each line is a field with a name, a colon and a value.

The format is set by RFC 5322. Your sending tool writes some fields, such as From and Subject. Every server that handles the message adds more, such as Received. The receiving mailbox adds the verdicts on authentication.

That mix is what makes headers useful. The fields you wrote can be faked. The fields added by the receiving server are much harder to fake.

How to find the raw message source#

Each mail client hides the header by default. Here is how to read email headers in each client. Use these menu paths:

  • Gmail: open the message, click the three dots, then choose "Show original".
  • Outlook (desktop): open the message, then File, Properties, and read "Internet headers".
  • Outlook on the web: open the message, then the three dots, View, "View message details".
  • Apple Mail: View, Message, "All Headers" or "Raw Source".

Copy the whole block. Paste it into a text editor so you can search it.

The fields to read first#

Read in this order. Each step takes a minute.

  1. Authentication-Results. Added by the receiving server. It lists the SPF, DKIM and DMARC verdicts. Start here.
  2. From and Return-Path. From is what people see. Return-Path is where bounces go. They are often different, and that is normal for sending tools.
  3. Received. One line per server hop. Read them from the bottom up.
  4. DKIM-Signature. Shows the signing domain (d=) and the selector (s=).
  5. Message-ID. A unique ID. The part after the @ often names the sending platform.
  6. Reply-To and List-Unsubscribe. Check that replies go where you expect.

Read the Authentication-Results line#

Here is a shortened example:

Authentication-Results: mx.example.net;
 spf=pass smtp.mailfrom=mail.sender.com;
 dkim=pass header.d=sender.com;
 dmarc=pass header.from=sender.com

Each verdict is a word:

  • pass: the check worked.
  • fail: the check ran and the message did not qualify.
  • softfail or neutral: the domain owner is unsure.
  • none: no record or no signature was found.

The format is defined in RFC 8601.

Why SPF can pass and DMARC can still fail#

SPF checks the Return-Path domain. DMARC compares the visible From domain with the domain that passed. That match is called alignment.

If your sending tool uses its own bounce domain, SPF passes for that domain, but it does not align with your From. DMARC then relies on DKIM. So always check that the header.d in the DKIM result matches your From domain.

To set these up from scratch, see our guides on how to set up SPF, DKIM and DMARC and how to check DMARC records. You can also run a quick lookup with the SPF checker.

Trace the route with Received lines#

Every server adds a Received line at the top. So the newest hop is first and the origin is last. Read from the bottom.

Look at three things in each hop:

  • The "from" name and IP. Is it the platform you expected?
  • The timestamp. A gap of several minutes between hops points to queuing or greylisting.
  • The "by" server. The last one is the receiving mailbox provider.

A message that took two hops to reach the inbox is usually healthy. One that shows an unknown relay between your tool and the recipient deserves a closer look.

Common problems you can spot#

What you see What it usually means
spf=fail The sending IP is not in your SPF record
dkim=none The tool did not sign the message, or the selector record is missing
dmarc=fail with spf=pass SPF passed for a different domain than From
Return-Path on an unrelated domain Shared bounce domain, check alignment
Large timing gap between hops Queueing, throttling or greylisting
X-Spam-Status: Yes The receiver scored it as spam; read the listed rules

If the DKIM record is the problem, our guide to finding your DKIM selector shows how to look it up.

A quick workflow for cold email senders#

Once you know how to read email headers, use this routine when a campaign suddenly lands in spam:

  1. Send a test to a Gmail address you control.
  2. Open "Show original". Gmail shows a summary of SPF, DKIM and DMARC at the top.
  3. Fix any fail or none before you change anything else.
  4. Check that the From domain matches the DKIM d= domain.
  5. Check that your sending IP or domain is not on a blocklist with the blacklist checker.
  6. Send again and compare the headers.

Google also publishes a free Messageheader tool that parses pasted headers and shows the delay per hop.

Authentication is one part of email deliverability. A clean header does not help if your list is full of bad addresses. Hard bounces damage your reputation fast, so verify addresses before you send. The Tomba Email Verifier checks syntax, domain and mailbox status so bounces stay low.

FAQ#

How do I read email headers in Gmail?#

Open the message, click the three dots and choose "Show original". Gmail shows the SPF, DKIM and DMARC summary first, then the full header.

Where are email headers stored?#

They are part of the message itself. Your mail client just hides them. Use "Show original", "View source" or "Properties" to see them.

Can email headers be faked?#

Some can. From, Reply-To and Message-ID are set by the sender. The Received lines added by servers you trust, and the Authentication-Results added by your own mailbox provider, are much more reliable.

What does dmarc=fail mean in a header?#

It means neither SPF nor DKIM passed with a domain that matches the From address. Depending on the DMARC policy, the receiver may reject the message, send it to spam or accept it.

How do I know which server sent the email?#

Read the lowest Received line. It shows the first server that handled the message and its IP address.

Do headers show the sender's location?#

Only indirectly. The originating IP can hint at a hosting region, but it often belongs to a mail platform and not to the person.

Next steps#

Now you know how to read email headers. Open one of your own sent emails today and read its header with the steps above. Once you can read the verdicts, most deliverability mysteries take minutes to solve. Then clean your list with the Tomba Email Verifier before the next send.

// start free

See who Tomba finds at any company

Type a company's domain to see its people, their roles and verified work emails, each with the pages it was found on. Free account, no card.

Free plan · No credit card required · GDPR & CCPA

Share
0 clapsEnjoyed it? Give a clap.
Abedrahim B

// about the author

Abedrahim B

CEO

Was this helpful?