Skip to content
Email basics November 4, 2026 · 3 min read · By Smailor Team

Also in FrançaisEspañolDeutsch

How to read email headers, line by line

Every email carries a block of technical lines above its text, called headers. They record which servers handled the message and whether it passed its authentication checks. When a message arrives late, lands in spam, or looks suspicious, the answer is usually there.

How to open them

App Where
Gmail Three dots at the top right of the message, then "Show original"
Outlook on the web Three dots, then "View", then "View message source"
Outlook desktop File, then "Properties", under "Internet headers"
Apple Mail View menu, then "Message", then "All Headers"
Yahoo Mail Three dots, then "View raw message"

The lines that matter

Authentication-Results is the most useful line. It is added by the receiving server and sums up the checks:

Authentication-Results: mx.google.com;
  dkim=pass [email protected];
  spf=pass smtp.mailfrom=example.com;
  dmarc=pass header.from=example.com

All three should read pass. See SPF, DKIM and DMARC for what each one means.

Received lines record each hop. There is one per server, and each server adds its line at the top. So read them from the bottom up to follow the message from origin to destination:

Received: from mail.example.com (mail.example.com [203.0.113.10])
  by mx.google.com with ESMTPS;
  Tue, 3 Nov 2026 09:14:02 +0100

Compare the timestamps from one hop to the next. A large gap tells you where a delay happened.

Other useful ones:

  • From is the address displayed. Anyone can write anything here.
  • Return-Path is where bounces go, and what SPF checks.
  • Reply-To is where your reply goes. If it differs from From on an unexpected message, be careful.
  • Message-ID is the unique ID, which is what you give to support when asking about a message.
  • DKIM-Signature names the signing domain in d=.
  • List-Unsubscribe is the address behind the unsubscribe link at the top of bulk mail.

Spotting a fake

Headers are one of the few ways to check a suspicious message. See how spoofing works for the bigger picture.

  1. Read Authentication-Results first. A dmarc=fail on a message from your bank is close to proof.
  2. Compare From and Reply-To. A different domain in Reply-To is a warning sign.
  3. Check the first Received line, at the bottom. Does the origin make sense for that sender?

The lower lines can be forged. A sender can invent extra Received lines before the message reaches a trusted server. Only the lines added by servers you trust, the ones nearest the top, are reliable. The first one was written by your own provider.

Frequently asked questions

Do headers show the sender's real location?

Rarely now. They show a server's IP, usually a mail provider's, rather than the person's computer. Big webmail services do not expose the user's IP at all.

Can I see who else received a message?

You can see To and Cc, but never Bcc. Those recipients are absent from the headers by design.

Are headers private?

They contain server names and IP addresses, and sometimes internal names from your company. Be careful about posting them publicly, and remove anything personal first.

Why does my message have spf=softfail when everything works?

A softfail often comes from a forward, or from a service you added without updating SPF. If DKIM passes with your domain, DMARC still passes.

To see what your own domain publishes without opening a terminal, the domain check reads your SPF, DKIM and DMARC records for you.