How to Inspect Email Headers in Gmail and Outlook
Open the full email header in Gmail or Outlook, check sender details and authentication results, and verify suspicious payment or document requests independently.

Xian Hui
12 November 2026 · 6 min read

In brief
How do I inspect email headers in Gmail and Outlook?
In Gmail, open the message and choose More beside Reply, then Show original. In new Outlook or Outlook on the web, use More actions, then View > View message details. In classic Outlook, use File > Properties. Compare sender domains and authentication results, then verify suspicious requests through a known contact route.
What you'll learn
- Open and copy full email headers in Gmail and Outlook
- Compare sender, reply and routing details for inconsistencies
- Interpret SPF, DKIM and DMARC results alongside the domains checked
- Verify suspicious requests independently and preserve headers for reporting
How to Inspect Email Headers in Gmail and Outlook
Imagine an accountant at a Singapore practice preparing a client's weekly payment batch. An email carrying a familiar supplier name asks for a bank account change before today's transfer. The signature looks right, but the reply address seems unfamiliar. Before changing the payment record, the accountant opens the email header and checks which domains actually handled the message.
Email headers are the technical records attached to a message. They show addresses, routing details and authentication results that the normal inbox view hides. Use them to investigate a payment instruction or request for client documents, then verify the request independently before acting.
How do you open the full header in Gmail?
Use Gmail in a computer browser. The Gmail mobile app does not offer this full header view.
- Open the email you want to inspect.
- Next to Reply, click More, then Show original.
- The full header opens in a new window.
- Click Copy to clipboard to copy it.
These are Google's instructions for tracing an email with its full header. The Show original page usually starts with a summary containing SPF, DKIM and DMARC results. Read the domain alongside each result rather than stopping at the word "pass".
For a clearer routing view, Google's free Admin Toolbox Messageheader tool can analyse a pasted header. Paste it into the input box and click Analyze the header above. Headers can contain client and staff addresses, so use the tool only if your practice permits sharing that information with the service.
How do you open the full header in Outlook?
The route depends on your version. Microsoft's header instructions cover these Windows and web options.
New Outlook for Windows and Outlook on the web, including Outlook.com:
- Open the message.
- Select More actions at the top of the message window.
- Select View > View message details.
Classic Outlook for Windows:
- Double-click the email to open it in its own window.
- Select File > Properties.
- Find the Internet headers box.
- Select the text and press Ctrl+C to copy it.
Microsoft's cited page does not cover Outlook for Mac. Outlook for Mac can show the message source, but the simplest route is to open the message in Outlook on the web and follow the web steps.
Which email header fields should you read first?
Start with the sender and reply addresses, then compare the authentication domains. Use routing and timing details as supporting evidence.
| Field | What to check |
|---|---|
From | Separate the display name from the actual address inside < >. A familiar name can hide an unfamiliar domain. |
Reply-To | Check where replies will go. An unexpected address different from the sender is a classic business email compromise sign. |
Return-Path | This is the address used for delivery failures. Its domain may legitimately differ when a mailing service is involved. |
Authentication-Results | Read spf=, dkim= and dmarc= with their pass or fail results and the domain checked. |
Received | Each server adds a line. Read from the bottom up because the bottom entry is the earliest recorded hop. |
Message-ID | Check the domain in the message identifier. It may reflect a sending service, so a difference alone does not establish fraud. |
Date | Compare the sender's stated date, time and time zone with the delivery trail. Timing alone does not prove identity. |
Legitimate delivery services can explain some differences. Equally, sender-supplied fields and lower routing entries can be forged. Ask your IT contact to interpret anything unclear rather than treating the header as a complete, verified history.
What would a suspicious supplier header show?
This fictional header is shortened for teaching. Authentication separators and other technical details are omitted, so it is a reading example rather than a complete raw header.
From: "Supplier Accounts" <accounts@supplier-co.example>
Reply-To: supplier-co.accounts@freemail.example
Return-Path: <billing@supp1ier-co.example>
Authentication-Results: [shortened extract]
spf=pass smtp.mailfrom=supp1ier-co.example
dkim=pass header.d=supp1ier-co.example
dmarc=fail header.from=supplier-co.example
Message-ID: <payment-update-1042@supp1ier-co.example>Read each line against the supplier address already held in your records:
- From claims to be
accounts@supplier-co.example. The display name adds no assurance. - Reply-To diverts your response to
supplier-co.accounts@freemail.example, outside the claimed supplier domain. - Return-Path uses
supp1ier-co.example. Look closely at the digit1replacing the letterl. - Authentication-Results introduces the three checks. SPF passes for
supp1ier-co.example, the envelope sender domain. DKIM passes for that same lookalike signing domain. DMARC fails for the visible From domain,supplier-co.example. - Message-ID also uses the lookalike domain. It supports the concern but does not prove who sent the message.
The two passes do not authenticate the claimed supplier domain. The reply diversion and failed DMARC result give the accountant good reason to hold the bank change and verify it separately.
What do SPF, DKIM and DMARC results actually prove?
SPF checks whether the sending system is authorised for the envelope sender's domain. DKIM checks a domain's digital signature. DMARC checks whether the visible From domain aligns with a passing SPF or DKIM result.
A failure involving a domain that claims to be a known organisation is a strong warning. Delivery arrangements or configuration problems can also cause failures, so ask IT to investigate rather than declaring fraud from one result.
A pass is not approval to pay or disclose information. It establishes only the relevant authentication result for the domain shown. A lookalike domain can pass all three checks using its own authorised systems. A genuine but compromised mailbox can pass too. Neither result proves that the person requesting the action is honest.
How should you verify and report a suspicious request?
Do not reply or follow instructions in the email. Use a phone number already held in approved records or another established contact route. Follow the steps for verifying unexpected requests independently. Do not substitute a number supplied in the suspicious message.
For changed payment instructions, follow the practice's approval process and verify supplier bank-detail changes before updating records or releasing funds. Header checks support that decision, they do not replace a callback on a known number.
Keep the original message and full header text for reporting and containing a cyber incident. Tell the designated contact what looked wrong and whether you clicked, replied, sent documents or changed payment details. You do not need to finish analysing every header field before reporting.
Key takeaways
- Open the full header using the steps for your Gmail or Outlook version.
- Compare the actual sender, reply destination and domains behind authentication results.
- Treat authentication failures as warnings and passes as limited evidence.
- Verify sensitive requests independently and preserve the header when reporting.
Last source check: 12 November 2026.
Next in the course: How to Check a Link or Website Before and After You Click
Sources
Frequently asked questions
This information has been prepared for general informational purposes only and is not intended to be relied upon as accounting, tax, or other professional advice.


