Theory · 10 min · Email and phishing analysis
Reading an email header
Find who really sent a message, where replies go, and what the receiving server concluded.
The From line the user sees is just a header the sender wrote. The address the receiving server talked to is the envelope sender (SMTP MAIL FROM), which ends up in the Return-Path header. They can differ, and in phishing they often do.
Received headers are added by each server the message passed through, newest at the top. Read them from the bottom up to follow the path from the sender to your mailbox. Only the ones your own servers added are fully trustworthy.
Reply-To sends replies somewhere other than the From address. A "CEO" email whose replies go to a free webmail address is a classic business email compromise sign.
Authentication-Results is written by your receiving server: the SPF, DKIM and DMARC verdicts. It is usually the fastest single line to read.
- Return-Path
- The envelope sender, used for bounces and checked by SPF.
- Received
- One hop on the path; read from the bottom up.
- Authentication-Results
- Your server’s SPF, DKIM and DMARC verdicts.
Your turn: select the field that proves it. Select the field that shows replies would go to the attacker, not to the CFO.
Do the interactive check Free, in the browser.
Sources
- RFC 5322: Internet Message Format (header fields) IETF
- RFC 5321: Simple Mail Transfer Protocol (envelope, Return-Path) IETF
- RFC 8601: Message Header Field for Indicating Message Authentication Status IETF