Cybersecurity & Information Security

Analyzing Email Headers: SPF, DKIM, DMARC, and Received

6 min readPublished: August 5, 2026

Professional visual illustration of email header analysis in the field of Incident Response and DFIR

Quick answer

Email header analysis is a controlled process that balances damage containment with evidence preservation. Document source, time, and tools, save Hash, build a Timeline, and separate fact, interpretation, and decision.

Incident Response and DFIR require a balance between speed, evidence preservation, business continuity, and documentation. A correct action is one that can be explained, reproduced, and reviewed after the incident. This article focuses on Email Header Analysis and is intended for SOC analysts and mail administrators. The goal is to provide a working methodology that can be applied in practice, in professional interviews, and in a work environment, without settling for a dictionary definition.

The main challenge is that data is almost always partial. Received chain, Return-Path, and SPF can indicate a direction, but their meaning depends on time, asset, user, and expected activity. Therefore, we will build the examination around an investigative question, required evidence, and a clear criterion for completion.

The practical scenario in the article is: decoding a simulated Header and marking anomalous points. All examples are laboratory data or process descriptions. When dealing with Penetration Testing, Web, or Cloud, work only with explicit authorization, a defined Scope, and the ability to stop the examination.

Header Structure

The important fields are not necessarily those displayed at the top of the screen. In Email Header Analysis, it is necessary to identify stable identifiers, time, source, destination, result, and context. Useful examples are Received chain, Return-Path, SPF, DKIM, DMARC, Message-ID. The goal is to enable Correlation between records and not just reading a single Event.

It is recommended to create a small Data dictionary: field name, meaning, format, source, expected Null values, and whether it is reliable for linking. This way, you can distinguish between a display field and an investigative identifier, and identify when a Connector or version has changed the Schema.

Received chain

The topic 'Received chain' is a central part of working on Email Header Analysis. It is recommended to break it down into three questions: what is the input, what decision do you want to make, and what evidence is sufficient to justify it. These questions prevent automatic use of a tool without understanding the purpose.

In practice, record the Received chain, Return-Path, SPF, DKIM, DMARC, compare them to expected behavior, and define at least one Pivot. The result should be verifiable by another analyst, including limitations and next steps.

SPF

The topic 'SPF' is a central part of working on Email Header Analysis. It is recommended to break it down into three questions: what is the input, what decision do you want to make, and what evidence is sufficient to justify it. These questions prevent automatic use of a tool without understanding the purpose.

DKIM and DMARC

The topic 'DKIM and DMARC' is a central part of working on Email Header Analysis. It is recommended to break it down into three questions: what is the input, what decision do you want to make, and what evidence is sufficient to justify it. These questions prevent automatic use of a tool without understanding the purpose.

From, Return-Path and Message-ID

The topic 'From, Return-Path and Message-ID' is a central part of working on Email Header Analysis. It is recommended to break it down into three questions: what is the input, what decision do you want to make, and what evidence is sufficient to justify it. These questions prevent automatic use of a tool without understanding the purpose.

Unique Examination Focus Areas

In this topic, it is recommended to build a focused evidence map in advance. The main examination focus areas are: Received chain, Return-Path, SPF, DKIM, DMARC, Message-ID, mailbox rules. The list is not an automatic Checklist; each item is chosen because it can link an entity, action, and time, or explain legitimate behavior.

Received chain: Define the expected value, what would be considered anomalous, and what additional source would corroborate the finding.
Return-Path: Define the expected value, what would be considered anomalous, and what additional source would corroborate the finding.
SPF: Define the expected value, what would be considered anomalous, and what additional source would corroborate the finding.
DKIM: Define the expected value, what would be considered anomalous, and what additional source would corroborate the finding.
DMARC: Define the expected value, what would be considered anomalous, and what additional source would corroborate the finding.
Message-ID: Define the expected value, what would be considered anomalous, and what additional source would corroborate the finding.

When one of the focus areas is unavailable, document the gap and choose an alternative. For example, if a Process identifier is not stable, you can use time, Host, User, and Parent; if a Payload is encrypted, use Metadata, volume, frequency, and TLS/DNS context.

Recommended Workflow

Define the Scope and a single working question regarding Email Header Analysis.
List the data sources and required evidence: Received chain, Return-Path, SPF, DKIM.
Create a short Baseline of normal behavior or expected outcome.
Perform the minimal check in a lab environment and save time, input, and output.
Build a Timeline or comparison table and separate fact from interpretation.
Pivot to an additional source to confirm or refute the initial explanation.
Summarize the decision, limitations, recommended action, and Retest criterion.

Practical Scenario

The chosen scenario is decoding a simulated Header and marking anomalous points. The purpose of the exercise is not to prove attack capability, but to practice safe collection, comparison, and documentation. Before starting, define simulated data, a time window, and an expected outcome.

At the end of the exercise, submit a product that another analyst or reviewer can evaluate: a screenshot or Export of the evidence, a short Timeline, initial assumption, corroborating evidence, limitation, and recommendation. When there is insufficient evidence, the correct conclusion is that the scenario was not proven.

Stage	What to perform	Output
Preparation	Define Scope, time, and target. List which fields or evidence from Received chain, Return-Path, SPF are expected to appear.	Short test plan
Data Creation	Perform a safe and simulated action related to Email Header Analysis, without real information or impact on a production system.	Controlled Event/Request/Flow
Collection	Collect the raw evidence and context from an additional source. Ensure Time zone, identifiers, and integrity.	Two linked pieces of evidence
Analysis	Write what each piece of evidence proves, what it does not prove, and what is the legitimate possible explanation.	Interim conclusion
Completion	Choose closure, escalation, Finding or Tuning; add a recommendation and Retest.	Documented output

Practical Checklist

Check and document: Source of evidence.
Check and document: Collection time and time zone.
Check and document: Hash and Chain of Custody.
Check and document: Tool and version.
Check and document: Response actions taken.
Check and document: Timeline and working assumptions.
Specify Time zone, tool version, and collection time.
Save the raw data before filtering or modification.
Write what the finding proves and what is still unknown.
Define owner and next action with a deadline.

Common Mistakes

Changing the system before preserving evidence.
Not documenting the time zone.
Not calculating Hash.
Mixing fact and conjecture.
Not documenting who held the evidence.
Prioritizing theoretical completeness over immediate damage containment.

Summary and CTA

Email Header Analysis: SPF, DKIM, DMARC, and Received is a topic that connects technical knowledge with work discipline. Start with a question, collect only relevant evidence, preserve context and time, and choose an action that can be justified and re-examined.

In HPI's Cybersecurity & AI track, these principles are practiced using systems, logs, and labs. A natural next step is to move on to the linked articles, perform the lab exercise, and save the output as part of a professional portfolio.

FAQ

Does Email Header Analysis alone prove an attack or vulnerability?

No. It provides a signal or a finding that requires context, validation, and an additional source. A professional conclusion relies on a chain of evidence and alignment with expected behavior.

What to do when some data is missing?

Document the missing information, check for an alternative source, and reduce the confidence level. Do not complete fields based on conjecture or present 'Unknown' as valid.

How long should evidence be kept?

The time depends on policy, regulation, cost, and the type of incident. It is important to define Retention, Legal hold, and the ability to export evidence in a verifiable format in advance.

How to practice without risking a real system?

Use virtual machines, simulated data, CTF, or a dedicated lab. In authorized tests, define Scope, Stop conditions, and backup before starting work.