How to Read an Email Header: Authentication, Route and Spotting Spoofing
When you wonder "is this email genuine?", the header is where the clues are. Here is what is written where, and what to look at to notice spoofing.
Published: November 17, 2026 · 日本語
What an email header is
Besides the body, every email carries a "header" of extra information. Your mail app shows only the sender, recipient, subject and date, but the real header holds much more: which servers the message passed through, and how the receiving server judged it.
A header is a list of lines in the form Name: value, such as "Received:" or "From:". A long value is folded onto the next line, which starts with a space.
How to get the header
- Gmail: open the message, click the three dots at the top right, then "Show original".
- Outlook (classic): double-click the message to open it, then File → Properties → "Internet headers".
- Thunderbird: select the message, then View → Message Source.
- Apple Mail: select the message, then View → Message → All Headers or Raw Source.
The wording differs by app. Look for "original", "source", "all headers" or "internet headers".
First, the three sender fields
What looks like "the sender" is really three different fields.
- From: the sender shown in your mail app. The sender can write anything here, so it cannot be trusted on its own.
- Return-Path: where delivery errors go. It holds the domain of the side that actually sent the message. With a mailing service it is normally a different domain from From.
- Reply-To: where your reply goes. If From is a company domain but Reply-To is an unrelated free-mail address, someone may be trying to intercept replies.
Authentication-Results: the receiving server's verdict
The most important line is Authentication-Results. The server that received the message checks SPF, DKIM and DMARC and writes the outcome here. It looks like this:
Authentication-Results: mx.example.net;
spf=pass smtp.mailfrom=bounce.mailer.net;
dkim=pass header.d=example.co.jp header.s=k1;
dmarc=pass (p=REJECT) header.from=example.co.jp
spf=pass: the sending server's IP address was allowed by the SPF record of thesmtp.mailfromdomain (SPF basics, in Japanese).dkim=pass: the digital signature of theheader.ddomain verified correctly (DKIM basics, in Japanese).dmarc=pass: SPF or DKIM passed for a domain belonging to the same organization as the From domain (DMARC basics, in Japanese).
What matters is less whether it passed than for which domain. In the example, SPF passed for mailer.net and DKIM for example.co.jp. If From is example.co.jp, DKIM matches From, so DMARC passes too.
If SPF and DKIM pass but DMARC fails, an attacker may have passed authentication with their own domain while faking only the From address. That is the classic spoofing pattern.
Received: the path the message took
Each time the message passes a server, that server adds one Received line at the very top. So you read them from the bottom up to follow the path from sender to recipient.
Received: from mx.example.net (mx.example.net [203.0.113.9])
by mail.example.org with ESMTPS; Tue, 17 Nov 2026 10:00:05 +0900
Received: from [10.0.0.5] (unknown [10.0.0.5])
by mx.example.net with ESMTP; Tue, 17 Nov 2026 10:00:03 +0900
fromis the sending side andbyis the receiving side.- The address in brackets, such as
[203.0.113.9], is the connecting IP the receiving side actually saw. - The time at the end of each line shows where the delay was. Timestamps that go backwards suggest clock drift or tampering.
Note that only the upper lines, written by your own mail service, can be trusted. A sender can plant fake Received lines at the bottom from the start.
Which lines to trust
A header grows as each server adds lines on top. The topmost Authentication-Results was written by your own receiving server and can be trusted, while any below it were written by the sender or an earlier server and can be forged. The Certadomain email header analyzer also uses only the topmost one.
A checklist for spotting spoofing
- Is it
dmarc=fail? - Even if SPF or DKIM passed, did they pass for a domain other than From?
- Is Reply-To an address unrelated to From, especially a free-mail address?
- Does the display name show another domain or a famous brand that disagrees with the real From domain?
- Is there more than one From (sometimes used to slip past authentication)?
- Was the sender's domain registered only recently? (The Phishing Check shows this.)
No single item proves a message is fake. Legitimate mail sent through a mailing service or mailing list often has a Return-Path or SPF that does not match From. Be wary when several signs add up.
What a header cannot tell you
- Passing authentication does not make a message genuine. Attackers can pass with a domain they registered themselves.
- A DKIM signature cannot be re-verified without the body. A
dkim=passin the header only repeats what the receiving server checked at the time. - The header says nothing about whether links in the body are safe. Check the domain of a suspicious link before opening it.
FAQ
Is the header sent anywhere when I paste it?
The Certadomain Email Header Analyzer analyzes the pasted text only inside your browser. The full header is never sent to our site; only domain names and the sending server's IP address are looked up to check the sender.
I cannot find Authentication-Results.
Some mail apps copy only the few fields shown on screen. Copy the full header from "Show original" or similar. Also, if the receiving server did not run authentication, the line may not exist at all.
A legitimate email shows SPF fail.
When a message is forwarded, the sending IP becomes the forwarding server's, which can make SPF fail. If DKIM passes and matches From, DMARC still passes.
Paste a header and check it
Paste an email header and the points in this article are checked for you. No sign-up.
Analyze an email header