Email Headers Are a "Travel Log"
Every email carries metadata called "headers" alongside the body text. Normally hidden, they can be viewed using the "Show headers" feature in your email client. Headers contain a detailed "travel log" of the email - which servers it passed through, when it was sent, the sender's IP address, and whether authentication checks passed.
Knowing how to read headers is a powerful tool for determining the authenticity of phishing emails or tracing the origin of spam.
Key Header Fields
Received Header - Server Relay Records
This is the most important header. Each server the email passes through adds its own information as a Received: header. Reading from bottom to top reveals the chronological path from sender to recipient.
Received: from mail-out.example.com (203.0.113.10) by mx.recipient.com with ESMTPS Wed, 15 Apr 2026 10:30:15 +0900
From this header, you can read the sending server's hostname and IP address, the receiving server, the communication protocol (ESMTPS = encrypted), and the timestamp.
From / Return-Path - The Sender's "Self-Declaration"
From: is a field the sender can freely set, making it easy to forge. Phishing emails set legitimate company addresses in the From: field. Return-Path: (envelope From) is the actual bounce address - if it differs from From:, forgery is possible.
Authentication-Results - Verification Outcomes
This header records the receiving server's SPF, DKIM, and DMARC authentication results.
Authentication-Results: mx.recipient.com; spf=pass (sender IP is 203.0.113.10); dkim=pass header.d=example.com; dmarc=pass
If SPF, DKIM, and DMARC all show pass, the sender's legitimacy is highly likely. If fail or none appears, caution is warranted.
X-Originating-IP - The Sender's Real IP
X-Originating-IP: is a non-standard header meant to pass the IP address of the sender's device on to the recipient. Some webmail services used to add it, but because it reveals where the sender is, the major providers moved away from including it. Gmail omits the header for privacy protection, and Hotmail (later Outlook.com) stopped adding it in December 2012, replacing it with X-EIP:, which carries the IP address in encoded form.
Tracing a sender through this header therefore only works when the message passed through a mail server configured to add it. If the record is there, enter the IP address in IP Check-san's IP Address Lookup to see the approximate geographic location and the network provider.
Detecting Phishing Through Headers
When you receive a phishing email, examining the headers can help expose the forgery.
From:shows a major company's address, but theReceived:sender IP is from an unrelated country's server- SPF is
fail- the sender IP is not on the domain's authorized list - DKIM is
fail- the email content may have been tampered with Reply-To:uses a different domain thanFrom:- an attempt to redirect replies to a different address
Summary
Email headers are a complete record of the journey a single email has taken. Tracing the route via Received headers, checking authentication status in Authentication-Results, and detecting forgery through From and Return-Path mismatches - these skills are practical email security knowledge.
Related Glossary Terms
Frequently Asked Questions
What can email headers reveal?
Email headers contain the complete route an email took from sender to recipient, authentication results (SPF, DKIM, DMARC), the sending server's IP address, the email client used, and timestamps for each hop. This information is invaluable for investigating phishing and spam.
Can phishing emails be detected through headers?
Yes. Key indicators include mismatches between the From address and Return-Path, failed SPF/DKIM/DMARC authentication, suspicious originating IP addresses, and Received headers showing unexpected server hops. These signs often reveal that an email is not from who it claims to be.
Does Gmail include the sender's IP address in headers?
No. Gmail omits the X-Originating-IP header for privacy protection, and Hotmail (later Outlook.com) stopped adding it in December 2012, so the major webmail services rarely leave the sender's real IP in this header. The main clues for tracing a route are the relay records in the Received headers.