What information does an email header contain?
By default, an email header only shows a few required details, such as the sender address, subject, or sending date. In fact, it also contains additional information about the sender and the transmission path of the message, which can provide important clues when analysing spam, phishing attempts, or delivery issues.
Key Takeaways
- An email header contains technical details about the transmission path of a message, in addition to the sender, recipient, and subject.
- Each header line consists of a field name, a colon, and the content; new entries appear at the top.
- Hidden fields such as
Received,Return-Path,Message-ID, andAuthentication-Resultsprovide clues about the origin and authenticity of a message. - In Outlook, Thunderbird, or webmail, you can display the full header via the message properties (‘Internet headers’) or the message source.
- Tools such as Google Admin Toolbox or MXToolbox automatically evaluate the transmission chain as well as SPF, DKIM, and DMARC results.
- Only the
Receivedentries of trusted servers are reliable; earlier lines can be forged.
How is an email header structured?
The top section of an email, known as the email header, contains various technical details and also shows the path the message took during transmission. Each line of an email header starts with a keyword (the field name), followed by a colon and the content. The order of the entries follows a clear technical principle. Newly added information appears at the top, while older information, meaning earlier transmission points, appears further down in the header.
Required email header fields at a glance
From: This field identifies the sender by email address. Some email clients allow multiple senders. If the technical sending address differs from the author’s address, this appears in an additionalSenderline. The address shown here does not necessarily match the domain of the server that actually sent the email.
Example: From: Sender <sender-address@example.com>
To: This line lists the recipient or recipients of the email, separated by commas. It does not have to match theEnvelope-Toinformation passed to the transfer protocol. This means your own email address may not appear in this field at all.
Example: To: Recipient <recipient-address@example.com>, Recipient 2 <recipient2-address@example.com>
Cc: This optional CC field contains the email address or addresses of recipients who receive a copy of the message.
Example: Cc: <cc-address@example.com>, Copy recipient 2 <cc2-address@example.com>
Subject: This field gives a brief indication of what the email is about.
Example: Subject: Re: Your appointment request for next year
Hidden email header fields
Return-Path: This line shows the return address for the email. It is added by the receiving mail server and specifies where non-delivery reports, also known as bounce messages, should be sent. The address usually matches the sender address passed through the email transfer protocol, which makes it important for deliverability checks.
Example: Return-Path: <return-address@example.com>
Received: As an email travels from one server to another, each mail server involved adds aReceivedline to the header. Each new entry is placed at the top of the list. This means the most recent server, usually your provider’s mail server, appears in the firstReceivedentry. This is the first reliable point in the message’s transmission path.
Example: Received: from mail.example.com (mail.example.com [192.0.2.15])
Message-ID: This field contains a unique identifier for the email. It is usually generated by the mail server or by the sender’s email program. The ID consists of a character string followed by an@symbol and a domain name. It allows the message to be identified technically and is especially useful for troubleshooting or grouping related messages into conversations.
Example: Message-ID: <434571BC.8070702@example.com>
Content-Type: This header line provides information about the message format and character set. Individual parameters are separated by semicolons. In addition totext/plainortext/html, the field may also indicate attachments withmultipart/mixedor alternative display formats withmultipart/alternative.
Example: Content-Type: text/plain; charset=UTF-8
Authentication-Results: Modern email systems often include anAuthentication-Resultsline. It records the outcome of security checks such as SPF, DKIM and DMARC and shows whether the email was technically authorised to be sent on behalf of the stated sender domain.
Example: Authentication-Results: spf=pass; dkim=pass; dmarc=pass
-
ARC (Authenticated Received Chain): Forwarded emails may include additional ARC header fields such asARC-Authentication-Results,ARC-SealorARC-Message-Signature. These fields are mainly used when a message passes through intermediaries, such as mailing lists or automatic forwarding services. -
BIMI (Brand Indicators for Message Identification): Some emails include references to BIMI. This method lets companies display a verified brand logo in the inbox, for example next to the sender address. For a mail provider to show the logo, the sender domain must meet specific security requirements, specifically a DMARC policy set top=quarantineorp=reject. A monitoring-only policy (p=none) is not sufficient. Related information may also appear in the email header, usually in connection with authentication checks.
What is the purpose of an email header?
By analysing the usually hidden information in an email header, you can trace the path an email took and check whether the stated sender is likely to be the actual sender. If you receive an email and have doubts about its authenticity, the header is an important place to look.
Beyond the delivery path, authentication checks now play a key role. Authentication-Results entries show whether security mechanisms such as SPF, DKIM, or DMARC passed or failed. A fail result can indicate spoofing or phishing.
Header analysis is also useful for businesses. When emails fail to deliver, are classified as spam, or generate high bounce rates, the full email header can provide important clues about configuration errors in the sender domain.
How email header analysis works
A detailed email header analysis helps you identify important technical information and better understand where a message came from and how it was delivered. The following sections explain the individual steps involved.
Step 1: Display the email header
Before you can analyse an email header, you first need to access the full header data. Most email programs hide the transmission details by default, so you need to display this information manually.
In Microsoft Outlook, for example, follow these steps:
- Open the message.
- Go to ‘File’ → ‘Properties’ → ‘Internet headers’ to view the full header.
- In Outlook on the web, open the three-dot menu and select ‘View message details’.
In Mozilla Thunderbird, you can display the header as follows:
- Right-click the message and choose ‘Message Source’, or press
Ctrl+U. A new window will open showing the complete raw message including all headers. - Alternatively, open the ‘View’ menu, select ‘Headers’ and then ‘All’ — though this option may not be available in all current versions of Thunderbird.
Other email services, such as Gmail, usually provide the full header through the menu of the selected message. In Gmail, this option is called ‘Show original’. In other interfaces, it may be called ‘View message source’ or ‘Show header’.
Step 2: Determine the sender address
To identify the sender, review the full email header for the IP address and the name of the first server involved in transmitting the message. To trace the delivery path, read the Received entries from bottom to top:
- The bottom entry was added first and represents the origin of the message — the earliest known point in the transmission chain.
- The
Receivedlines above it show subsequent transfer points, each added by the next server in the chain. - The top entry was added last and usually comes from your receiving mail server or provider. It marks the first reliable trust boundary.
- The top
Receivedentry contains the IP address of the system that delivered the message directly to your mail server. This is often a relay, gateway, or email service provider, not necessarily the sender’s original device.
Copy the IP address from the relevant Received entry into a suitable IP analysis tool. For a structured review of the full email header, browser-based services such as Google Admin Toolbox – Message header or MXToolbox Email Header Analyzer are useful.
These tools automatically reconstruct the transmission chain and clearly show the results of SPF, DKIM, and DMARC checks. This helps you assess the submitting system and its location. The result should match both the server name and the time zone shown in the header line.
How can you spot manipulated email headers?
Spam senders usually do not want replies to their messages. They also typically try to hide their identity. For this reason, the From and Return-Path lines in spam emails often do not reflect the true sender. Instead, attackers use false identities to disguise where the message really came from.
Common examples
Many recipients in Ireland receive fake emails claiming to come from companies or organisations such as An Post, DPD, PayPal, banks, or government agencies. These messages often ask users to open an external link. In many cases, the sender addresses only roughly resemble the real addresses and can be exposed as spam by analysing the email header.
Received entries as a control point
Identifying the true source of spam emails is often difficult. Spammers may use misconfigured mail servers or virus-infected computers as relay points, which makes clear identification through the email header harder.
The Received entries are the only parts of the email header that senders cannot fully control or change afterward. This is because they do not have access to the last Received entry, which normally also contains the source IP address.
However, earlier Received lines can be manipulated or inserted to create false trails. For this reason, they should always be assessed together with authentication results such as SPF, DKIM, or DMARC checks.