Topic · Investigation
Email header analysis
Email header analysis examines transport and authentication metadata to understand how a message traveled.
How it works
Received hops, Authentication-Results, Return-Path and DKIM signatures provide evidence.
What can go wrong
Headers can be forged by untrusted senders before the first trusted receiving hop.
What to check or do
Start from trusted receipt headers and correlate with server-side logs.
Practical scenario
An investigator reads a forwarded screenshot of headers that appears to show dmarc=pass. Without trusted original headers, the result may have been copied from an untrusted upstream message or another sender.
Verification checklist
- Obtain the original complete message source whenever possible.
- Identify the receiving service that wrote the trusted Authentication-Results field.
- Trace Received headers from the trusted edge backward, noting forged upstream possibilities.
- Correlate identity, IP and timestamps with provider logs and current DNS configuration.
How to investigate Email header analysis
- Signal to investigate
- A message looks fraudulent but an SPF result in the visible client summary says 'pass'.
- Evidence to collect
- Export full raw headers and reconstruct trusted Received hops, Authentication-Results, From, Reply-To and Return-Path.
- Common wrong conclusion
- Untrusted parties can prepend forged header fields; identify the receiving system's trusted authentication stamps.
How to interpret the evidence
Raw headers encode different layers of evidence: visible From, Reply-To, Return-Path, message trace hops, DKIM signatures, and receiver authentication assessments. A malicious sender can prepend forged headers, so investigators need the trusted boundary of the receiving infrastructure before relying on Authentication-Results or Received lines.
What to change and how to verify it
Export the original message rather than a screenshot or forwarded text. Identify the destination provider's trusted authentication results, reconstruct credible trace hops and compare observed sender identities. Preserve hashes and timestamps if the message may be evidence in an incident response or abuse report.
# Work with the original .eml and trusted receiver headers,
# not a forwarded screenshot or a pasted SPF summary.Educational example; not validated against your live infrastructure.Put this into practice
Run a focused check, then explore protection if your domain needs it.