Reading Email Headers
what the hidden lines of an email reveal about where it really came from
An email has two parts: the part you read, and the headers, a block of technical lines added as the message travels. When you suspect a message is fake, the headers are where the evidence is. Most mail apps offer "View original" or "Show headers".
The lines worth reading
- From: the address shown to you. Anyone can type anything here, so it proves little by itself.
- Reply-To: where your reply will go. A mismatch with From is a classic warning sign.
- Return-Path (the envelope sender): where bounces go. It often shows the real sending system.
- Message-ID: a unique ID. A domain here that does not match the claimed sender is suspicious.
- Date and Subject: odd dates or mismatched threading can reveal replayed or forged messages.
- Received: one line added by each mail server that handled the message.[1]
Read Received lines from the bottom up
Each server adds its line on top, so the oldest hop is at the bottom. Follow them upward to trace the route: the lowest one is closest to the original sender. Look for the sending server's name and IP address, the time between hops and anything that does not fit, such as a "bank" email whose first hop is a consumer server in another country. Only the lines added by servers you trust (your own provider) are reliable, because earlier ones can be forged.
The authentication results
Look for an Authentication-Results header added by your provider. It usually reports:
- SPF: was the sending server allowed to send for the domain?[2]
- DKIM: does the cryptographic signature check out, and for which domain?
- DMARC: do SPF or DKIM line up with the domain in the visible From address, and what policy does the domain owner want applied?
pass is good news, fail is worth attention, but a pass is not proof of honesty: attackers can send authenticated mail from a look-alike domain they own. Always compare the domain to the one you expected.
A quick checklist
- Does the From domain match Return-Path and the sending server?
- Do SPF, DKIM and DMARC pass, and for the right domain?
- Is there a Reply-To that sends answers elsewhere?
- Does the first trusted Received hop look plausible?
- Do links point where they claim to?
Headers can contain personal details, so avoid pasting full headers into random websites; use your organization's tools.
Sources
Test yourself
My notes
Private — saved only on this device, never sent anywhere.