How to Analyze Email Headers to Spot Phishing

How to read email headers step by step: where to find them, how to follow the Received chain, and how SPF, DKIM and DMARC results tell a forged sender from a real one.

OSINT9 min readPublished 16 November 2026
FR

Francisco RamosGREM

Founder · Malware Analyst · Lead Instructor

What do email headers tell you?

The From address you see in the inbox is just text the sender wrote. The headers are harder to fake because each server that handles the message adds its own lines, and the last one, your own provider, also writes down the result of its authentication checks.

How to open the full headers

  • Gmail: open the message, ⋮ menu › Show original.
  • Outlook on the web: ⋯ menu › View › View message source.
  • Outlook desktop: open the message › File › Properties › Internet headers.
  • Thunderbird: View › Message Source, or Ctrl+U.

Work on a copy (save the .eml file) and do not click anything inside the message while you investigate.

The headers that matter, in order

Return-Path: <bounce@mailer.cheap-hosting.example>
Authentication-Results: mx.company.example;
  spf=pass smtp.mailfrom=mailer.cheap-hosting.example;
  dkim=pass header.d=cheap-hosting.example;
  dmarc=fail header.from=bank.example
From: "Bank Security" <security@bank.example>
Reply-To: <support-bank@freemail.example>
Received: from mailer.cheap-hosting.example (203.0.113.45) by mx.company.example
Message-ID: <a1b2c3@mailer.cheap-hosting.example>
A trimmed, fictitious example. SPF and DKIM pass, but for the sending service's domain, not for bank.example, so DMARC fails.
HeaderWhat to check
FromThe address the user sees. Easy to forge; never trust it alone.
Return-PathWhere bounces go, also called the envelope sender. A different domain from From is common for mailing services, but worth noting.
Reply-ToWhere your reply would go. A free mail address here, under a corporate From, is a strong phishing sign.
Authentication-ResultsWhat the receiving server checked: spf, dkim and dmarc, each with pass, fail, softfail or none.
ReceivedOne line per server. Read from the bottom (the origin) to the top (your server). Look at the first external IP.
Message-IDGenerated by the sending system. Its domain often reveals the real sending platform.

SPF, DKIM and DMARC without the jargon

CheckQuestion it answers
SPFIs this server allowed to send mail for the envelope sender's domain (Return-Path)?
DKIMWas the message signed by the domain in header.d, and has it not changed since?
DMARCDo SPF or DKIM pass for the same domain the user sees in From, and what does that domain ask receivers to do if not?

The trap is that SPF and DKIM can pass for the attacker's own domain. DMARC is the check that ties the result to the visible From, so dmarc=fail on a well-known brand is the line to look for first.

A quick checklist

  1. 1Does the From domain match the organisation it claims to be? Look for look-alike domains.
  2. 2Does Reply-To point somewhere else, especially a free mail service?
  3. 3What do SPF, DKIM and DMARC say, and for which domain does each one pass?
  4. 4Which IP address sent it (the first external Received line), and who owns it?
  5. 5Do the links in the body point to the domain the message claims to come from?

Header analysers such as Google Admin Toolbox Messageheader or MXToolbox lay out the Received chain and the delays between hops, which saves time on long headers.

From article to practice, with nothing to install

What you just read is learned by doing it. Here is what it looks like inside.

The SOC simulator, inside

This is the simulator from the courses, driven by a script: you can pause it and step through it. With a free account you solve it yourself.

A guided lab, step by step

hacktheknowledge.com/app/labs/ssh-brute-force

Example from the SOC track: the machine is real and the flag is checked when you submit it.