Skip to content

Email header analyzer (SPF, DKIM & DMARC)

Debug delivery delays and spoofing warnings directly in your browser without sending sensitive internal headers to a remote server.

How to use Email header analyzer

  1. Paste raw email headers or drop an EML file. Enter full header text from Gmail Show original or Outlook Properties into the header input box, drop a .eml, .txt, or .msg file, or click Load sample headers to test a multi-hop trace.
  2. Run local header analysis in the worker. Click Analyze headers to extract header fields up to the first blank line, unfold wrapped lines, and decode RFC 2047 international subjects and addresses without DNS lookups.
  3. Inspect authentication verdicts and alignment checks. Review the SPF, DKIM, DMARC, and ARC badge cards alongside PASS, FAIL, and NOTE diagnostics comparing From against Return-Path, Reply-To, and DKIM domains.
  4. Trace the chronological server hop waterfall. Follow Hop 1 through the final relay to spot TLS or ESMTPS encryption badges, private IP badges, 5-minute bottleneck alerts, and negative clock-skew intervals.
  5. Export unfolded headers, JSON, or hop CSV. Toggle Show all unfolded headers for raw inspection, use Copy JSON or Export JSON for ticket logs, or save email-hops.csv for spreadsheet review.

Everything runs in this browser tab. Nothing you paste or open is uploaded or logged, so it's safe for keys, tokens and private data.

Why does this email header analyzer inspect headers without DNS?

To trace email headers safely during security or deliverability triage, this browser-based email header analyzer parses every line locally inside a Comlink dev Web Worker with zero live DNS lookups. Corporate hostnames, internal IP subnets, envelope senders, and confidential subjects stay inside browser memory rather than leaking through remote web scanners or external DNS queries.

Standard online tools often log submitted text or broadcast inspected domains over DNS resolvers. Here, you can paste raw Gmail Show original or Outlook Properties blocks directly into the text input, drop a .eml, .txt, or .msg file, or click Load sample headers to explore the built-in multi-hop trace containing ARC seals, internal relay [10.24.8.19], and TLSv1.3 hops.

When raw evidence comes locked inside a Google Takeout or Thunderbird mailbox export rather than a standalone message, pull individual .eml headers first with the MBOX viewer and reset between messages using Clear or Analyze headers.

Tracing the chronological Received hop waterfall and latency

Reading SMTP headers manually feels upside down because every mail transfer agent prepends its Received: timestamp above existing entries. Per the RFC 5321 SMTP header trace specification, the top line belongs to the final destination server while the bottom line marks where transmission started.

Diagnostic signal Exact code rule Rendered UI badge or alert Operational meaning
Delivery bottleneck delayMs > 300,000 ms Warning note (> 5m delay) Mail queued for over 5 minutes between relays
Clock skew delayMs < 0 ms Clock skew warning badge Downstream MTA clock lags upstream server or header forged
Private / internal hop 10/8, 172.16-31/16, 192.168/16, CGNAT, fe80: Private IP badge Internal or carrier-NAT relay exempt from public TLS warning
Unencrypted public hop Public IP missing TLS token Security warning card Plaintext SMTP crossing public networks without encryption
Encrypted relay transport Matches tls, esmtps, https, or ssl TLS badge in hop row Link transport encrypted between mail relays

Reversing RFC 5321 headers and catching clock skew

Header parsing calls extractHeaderBlock to read up to the first blank line (\n[ \t]*\n), then runs unfoldHeaders to join space- or tab-indented continuation lines before decoding RFC 2047 subjects and addresses. The analyzer flips Received entries bottom-to-top into Hop 1 through Hop N, totaling elapsed transit time from the first timestamp to the last.

If any adjacent relay pair yields delayMs < 0, the row shows a Clock skew badge instead of fake sub-second delivery. Any gap above 300,000 milliseconds triggers a >5-minute delay note, and you can also convert exported EML messages into PDF packages when archiving visual message content alongside timing notes.

Classifying private IPv4 subnets, CGNAT, and missing TLS

Every extracted sender address runs through isPrivateOrReservedIp covering IPv4 10/8, 127/8, 0/8, 192.168/16, 172.16-31/16, 169.254/16, carrier-grade NAT 100.64-127/10, plus IPv6 ::1, fe80:, fc/fd, and ::ffff: mapped private prefixes. Those internal hops earn a Private IP badge and suppress noisy plaintext warnings inside internal mail routing.

By contrast, public hops lacking tls, esmtps, https, or ssl tokens trigger an unencrypted-hop warning card immediately.

Extracting SPF, DKIM, and ARC authentication verdicts

Receiving gateways stamp verification results at delivery time so administrators can inspect what checks passed or failed without re-querying live DNS records later. Following the RFC 8601 Authentication-Results format, the analyzer prioritizes the newest Authentication-Results header first across SPF, DKIM, DMARC, and ARC methods.

ARC-Seal: i=1; a=rsa-sha256; cv=none; d=lists.example.net; s=arc2025
Authentication-Results: mx.northwind.example;
  dkim=pass header.d=billing.northwind.example header.s=s2026;
  spf=pass smtp.mailfrom=bounce@billing.northwind.example;
  dmarc=pass (p=REJECT) header.from=northwind.example

Fallback priority across Authentication-Results and ARC headers

When Authentication-Results omits an entry or is absent, the parser falls back sequentially to ARC-Authentication-Results, then to Received-SPF, raw DKIM-Signature tags (d=, s=, a=, h=), and ARC-Seal chain status (cv=). Per the RFC 8617 Authenticated Received Chain protocol, reading ARC headers matters when mailing lists or forwarders modify recipients and break SPF while keeping earlier pass seals intact.

Supported verdict states and DKIM signature metadata tags

Verdict badges normalize every extracted result to one of eight states: pass, fail, softfail, neutral, temperror, permerror, none, or missing. Under DKIM, inspecting the d= domain, s= selector, a= algorithm, and signed h= header list distinguishes cryptographically verifiable signatures from unsigned relays. When diagnosing binary Outlook items rather than raw RFC 5322 text, use Outlook MSG header inspection without desktop Office.

Auditing DMARC domain alignment across From and Return-Path

Authentication passing in isolation never prevents lookalike spoofing if an attacker signs spam with their own valid domain. As specified in the RFC 7489 DMARC alignment specification, DMARC requires the domain visible in From to align with either the SPF bounce domain (Return-Path) or the DKIM signing domain (d=).

Relaxed organizational domain matching and ccTLD boundaries

The analyzer computes organizationalDomain across From, Return-Path, Reply-To, and DKIM d=, comparing registrable base domains so subdomains like alerts.northwind.example align cleanly under relaxed rules. A 16-entry TWO_LABEL_CCTLD exception table (co.uk, org.uk, ac.uk, gov.uk, com.au, net.au, org.au, co.nz, org.nz, co.jp, or.jp, com.br, co.in, org.in, com.sg, com.mx) prevents two organizations sharing .co.uk from falsely matching.

Flagging Reply-To mismatches and X-Originating-IP traces

Alongside From alignment, the checks panel compares Reply-To against From and surfaces X-Originating-IP inside the envelope summary whenever present. Mismatched Reply-To domains generate a diagnostic NOTE rather than an automatic failure because helpdesk SaaS mailers frequently route replies externally.

If API webhook callbacks or OAuth notifications embed bearer tokens inside raw headers, inspect those signed payloads separately with a signed JWT bearer token header inspector.

Security triage tip: Treat spf=pass alongside a FAIL alignment warning as high-priority spoofing evidence. An external sender can pass SPF for their own bounce domain while forging your organization’s visible From address unless DMARC policy alignment holds.

How are header analysis JSON and hop CSV exports structured?

Exporting results saves a UTF-8 BOM hop table (email-hops.csv) with 11 formula-safe columns (Hop, From Host, From IP, Private IP, By Host, Protocol, TLS, With, Timestamp UTC, Delay (ms), Clock Skew) or a complete structured diagnostic report (email-header-analysis.json / Copy JSON). Both formats preserve chronological order and computed transit latencies cleanly.

  • JSON diagnostics schema: Combines subject, decoded from, to, returnPath, replyTo, messageId, xOriginatingIp, totalTransitMs, spf/dkim/dmarc/arc verdicts, checks, chronological hops, and unfolded rawHeaders.
  • CSV injection protection: headerAnalysisToCsv prepends a UTF-8 BOM and neutralizes cells starting with spreadsheet formula prefixes (=, +, -, @) before generating email-hops.csv so untrusted subjects or relay hostnames open cleanly without executing Excel formulas.
  • Full unfolded header drawer: Click Show all unfolded headers to inspect every RFC 2047 decoded header field and custom X-* routing tag side by side, or press Clear to purge pasted header text and diagnostic state between sessions.

Questions

Does this analyzer perform live DNS lookups for SPF or DMARC?

No. Everything runs offline inside a Comlink dev Web Worker with zero external network requests or DNS queries. Instead of probing corporate domains externally, the parser extracts authentication verdicts recorded by receiving mail servers inside Authentication-Results, ARC headers, Received-SPF, and DKIM-Signature fields.

Why do Received headers appear in reverse order in raw email?

Each SMTP server handling a message prepends its Received line at the top of the header block, placing the final mailbox server first and the originating sender last. The analyzer reverses those entries automatically so the hop table reads chronologically from Hop 1 at origin to delivery.

What causes negative hop delays and clock skew warnings?

A negative inter-hop delay occurs when a receiving server stamps an earlier UTC timestamp than the upstream relay that handed off the message. Because mail cannot arrive before it is sent, unsynchronized NTP clocks or forged headers produce delayMs below zero and trigger the Clock skew badge.

How does relaxed DMARC alignment compare From and Return-Path?

Relaxed alignment extracts the registrable organizational domain from the visible From address and checks whether it matches the Return-Path bounce domain and DKIM d= signing domain. Subdomains like mail.example.net align with example.net, while 16 two-label country suffixes such as co.uk and com.au compare three labels.

Which file formats can be loaded alongside pasted email headers?

Besides pasting raw lines directly into the textarea, the compact drop zone accepts .eml, .txt, and .msg text files. Header extraction stops at the first blank line so body text and large attachments are ignored cleanly while parsing folded metadata.

What happens when an internal hop uses CGNAT or RFC 1918 IP addresses?

Hops matching RFC 1918 private ranges, carrier-grade NAT 100.64.0.0/10, loopback, link-local 169.254/16, or IPv6 unique-local addresses receive a Private IP badge. Unencrypted transport across internal private relays does not trigger the public unencrypted-hop warning reserved for internet-facing servers.

Updated