CyberChef Tools

Email Header Analyzer

Inspect a message's route, sender fields and reported authentication results. Open the message in CyberChef, then select the Email output viewer to turn raw headers into a structured view.

Open email workspaceTry the example

Opens the CyberChef workbench. Your input is processed locally.

How to use it

  1. Get the original message source or .eml file from your mail client. A forwarded message may have different headers.
  2. Open the email workspace and paste the original source into Input. Keep the recipe empty so Output contains the complete message. Press Bake if Auto Bake is off.
  3. Choose Email in the Output viewer strip. Review the sender fields, Received chain and authentication results together. IP addresses in the route are displayed in defanged form.

A reproducible example

This synthetic sample uses no live indicators.

Input

Return-Path: <sender@example.org>
Received: from mail.example.org (mail.example.org [192.0.2.10])
 by mx.example.net with ESMTP; Tue, 22 Sep 2026 09:00:02 +0000
Authentication-Results: mx.example.net; spf=pass smtp.mailfrom=example.org; dkim=none; dmarc=pass header.from=example.org
From: Sample Sender <sender@example.org>
To: Analyst <analyst@example.net>
Subject: Synthetic header example
Date: Tue, 22 Sep 2026 09:00:00 +0000
Content-Type: text/plain; charset=utf-8

A synthetic message for header inspection.

What to look for

Sender: sender@example.org
Subject: Synthetic header example
Received: mail.example.org → mx.example.net
Reported authentication: spf=pass, dkim=none, dmarc=pass

Read the route and sender fields

Received headers are usually added at the top as a message moves between servers. Read the chain from bottom to top, but distinguish trusted receiving infrastructure from headers a sender could have supplied. Compare From, Reply-To and Return-Path; a difference deserves context and is not by itself evidence of phishing.

Authentication results are reported evidence

The viewer reads SPF, DKIM and DMARC results already present in the message. It does not independently verify a DKIM signature or rerun DNS-based checks. Trust an Authentication-Results field only when you know which receiving system added it. A pass does not establish that the content is safe.

Missing or malformed headers

Body-only text cannot provide a delivery route. If fields are missing, use the original message source and retain folded continuation lines and the blank line between headers and body. Truncated messages may produce incomplete results. All addresses in this example are reserved for documentation.

Reference: RFC 8601: Authentication-Results.

Related tools

Local processing, clear boundaries

These workflows process input in your browser. The hosted site uses analytics; optional Endpoint lookups are separate actions that can contact external services. See the privacy policy for details.