Wesloo
All topicsTopics

Email

Read Email Headers: A Practical Guide

Short answer

Email headers are the hidden metadata attached to every message. They record the servers, IP addresses, timestamps, and authentication results behind a message. Reading them helps you trace a sender, verify SPF, DKIM, and DMARC, and judge whether a message is trustworthy.

Key points

  • Headers are metadata, not the message body.
  • Received lines show the path in reverse chronological order.
  • SPF, DKIM, and DMARC results indicate authentication status.
  • The bottom Received line usually reveals the original sender.
  • Analyzers and IP checks can speed up review.

Read email headers when you need to know where a message really came from, which servers handled it, and whether its sender identity checks passed. Every email carries hidden metadata that records its path from sender to recipient, including IP addresses, timestamps, and authentication results. Most mail clients hide this data behind a menu, but it is available in every major service. Learning to read it takes a few minutes and can help you judge whether a message is genuine or a phishing attempt.

What an email header contains

An email header is the block of metadata attached to every message. It is not the subject line or body; it is the routing and identity information that mail servers add as the message moves. Fields such as From, To, Subject, Date, and Message-ID describe the message itself. Received lines record each server that handled it, usually in reverse chronological order, so the oldest entry is near the bottom. Authentication results show whether SPF, DKIM, and DMARC checks passed or failed.

Mail routing depends on DNS records such as MX records, which tell sending servers where to deliver mail for a domain. Headers preserve that journey after delivery, so you can inspect it later. They also travel with the message whether you read mail with IMAP or POP3, because both protocols retrieve the stored message with its metadata intact.

Other common fields include Reply-To, which shows where replies are directed, and List-Unsubscribe, which appears in many mailing list messages. X- headers are custom fields added by providers or filters and can include spam scores or internal routing notes. Not every field appears in every message, and the order can vary. Focus on the fields that answer your question rather than reading every line.

How to read email headers in major clients

The exact menu names differ, but the process is similar: open the message, open its menu, and choose the option that shows the full source or original message. You can then copy the header block into an analyzer if you prefer a parsed view. The steps below cover the most common clients.

Gmail

Open the message and choose the option that shows the original message, then copy the header text for review.

Outlook

Open the message and use Outlook's option to view the full source or message details, then copy the header text if you want to paste it into an analyzer.

Apple Mail

Open the message and use Apple Mail's option to view all headers or the raw source, then copy the header block if needed.

Yahoo Mail and Proton Mail

Open the message and use the client's option to view the raw message or headers, then copy the full header block for review.

Reading the Received chain

Received lines are the most useful part of a header for tracing a message. Each mail server that handles the message adds a Received line at the top, so the list runs backward in time. The bottom Received line usually points to the server or client that first submitted the message. Look for the sending IP address, the hostname, and the timestamp in that line.

A single message can pass through several servers, especially when it crosses providers or security gateways. Compare the hostnames and IP addresses to see whether the path matches the claimed sender. If the first server is unrelated to the sender's domain, treat the message with caution. Time gaps between Received lines can also reveal delays or suspicious routing.

When a message is forwarded, the forwarding server adds its own Received line, so the chain can become longer than the original path. In those cases, identify the earliest line that belongs to the original submission and compare it with the claimed sender. If you cannot find a plausible origin, treat authentication failures as a stronger warning.

FieldWhat it tells you
ReceivedServer that handled the message and when
FromClaimed sender address
Return-PathAddress used for bounces
Message-IDUnique identifier for the message
DateTime the message was sent
X-Originating-IPOriginal sender IP in some systems

Authentication results: SPF, DKIM, and DMARC

SPF, DKIM, and DMARC are checks that help receiving servers decide whether a sender is authorized to use a domain. SPF compares the sending IP with the domain's published list of allowed senders. DKIM checks a cryptographic signature added by the sending domain. DMARC tells receiving servers what to do when SPF or DKIM fails and whether the domains align.

Look for Authentication-Results or similar fields in the header. A PASS result means the check succeeded for that message. A FAIL result means the check did not pass. When SPF, DKIM, and DMARC all return PASS, the sender has been verified and the message can be treated as trustworthy. When any of those checks returns FAIL, avoid interacting with the message and report it to your email provider.

Spotting phishing with headers

Phishing messages often imitate a trusted sender while failing authentication or using an unrelated sending server. Compare the From address with the domain in the bottom Received line. Check whether the Return-Path domain matches the From domain. Look for mismatched display names, unusual Message-ID domains, and failed SPF, DKIM, or DMARC results.

A message can still look convincing in the body while its headers reveal a different origin. A bank notice sent from an unrelated IP with a failed DMARC result should not be trusted. Headers do not prove intent, but they give concrete evidence about routing and identity. Use them as one part of a broader check that includes links, attachments, and sender behavior.

Using an analyzer and IP checks

An analyzer can break the header into readable sections and check the sending IP against reputation databases, which reduces manual lookups when you review many messages. For a single check, entering the IP into a blacklist checker gives a quick indication of whether other users have flagged the sender.

IP intelligence can show the network, region, and hosting type associated with an address. That context helps you decide whether a sending server is plausible for the claimed organization. It is not proof of identity, because attackers can use compromised servers or shared hosting. Treat IP data as supporting evidence, not a final verdict.

Mail often passes through cloud computing infrastructure, so a hosting provider name in the IP data is not automatically suspicious. Compare it with the sender's known services and domains. If the IP belongs to an unrelated consumer network, be more cautious.

If you migrate emails to a new provider, old headers remain intact and can still be reviewed later. That makes headers useful for long-term investigations as well as immediate checks.

Common mistakes and limits

Do not assume the From field alone proves the sender. It is easy to forge and should be checked against Received and authentication results. Do not read headers from top to bottom as if they were a timeline; remember that new Received lines are added at the top. Do not ignore time zones when comparing timestamps.

Headers can be long and noisy, especially in messages that pass through mailing lists or security filters. Focus first on the bottom Received line, authentication results, From, Return-Path, and Message-ID. If those are consistent and pass checks, the message is more likely to be legitimate. If they conflict, investigate before responding.

Quick review checklist

  1. Open the message and view its full headers.
  2. Read the bottom Received line for the original IP and hostname.
  3. Check SPF, DKIM, and DMARC results.
  4. Compare From, Return-Path, and Message-ID domains.
  5. Use an analyzer or IP check when the result is unclear.

Questions people also ask

Where do I find email headers?

Open the message, use its menu, and choose an option such as Show original, View message details, View raw message, or View headers. The exact name depends on the mail client.

What does a failed DMARC result mean?

It means the message did not pass the domain's stated authentication policy. Do not interact with the message and report it to your provider.

Can headers show the sender's exact location?

They can show an IP address and related network information, but that is not the same as a precise personal location. Use it as supporting evidence.

Do I need an analyzer to read headers?

No. You can scroll through the raw header, but an analyzer makes the fields easier to read and may add IP reputation checks.

Related pages

  • Organize Email Inbox with Filters and Labels

    Filters and labels turn a crowded inbox into a sorted workspace by routing messages automatically and grouping them by topic. A simple system of folders, rules, and daily review habits keeps important mail visible while archiving the rest.

  • Catch-all email address: what it is and how it works

    A catch-all email address is a mailbox that receives messages sent to any address on its domain, including addresses that do not exist. Businesses use it to avoid losing mail to typos or guessed addresses, while marketers must test and segment these addresses because a catch-all server accepts mail without proving the recipient is real.

  • How to migrate emails to a new provider

    Migrating email means copying messages and contacts to a new mailbox, then changing DNS so new mail arrives there. Back up first, keep the old account active until tests pass, and update MX, SPF, DKIM, and DMARC records.

  • What Are MX Records and How Do They Work?

    MX records are DNS entries that name the mail servers responsible for receiving email for a domain. They include a priority number so sending servers can choose the preferred destination and fall back to alternatives if needed.

  • What Is the Difference Between IMAP and POP3?

    IMAP keeps email on the server and synchronizes changes across phones, tablets, and computers. POP3 downloads messages to one device and usually removes them from the server, so it suits a single computer. Choose IMAP for multi-device access and POP3 only when local storage on one machine matters.

  • PID Controllers in Robotics: How Motion Control Works

    PID controllers in robotics compare a target motion with measured motion and combine proportional, integral, and derivative corrections to calculate a control command. The robot applies that command to a motor or other actuator, then repeats the measurement and correction as new sensor data arrives.

How this page was prepared

Before writing, the topic was researched in the sources below. The page then passed automatic quality checks.

Report a mistake on this page