Microsoft 365, AD and Windows · #23

Online Email Header Analyzer

Orders the Received chain of an email header and shows delays between hops and authentication results.

  • Data is processed in your browser and not sent to a server
  • Export: CSV

Tool

Header section only. Data does not leave your browser.

What does this tool do?

The story of a late, spam-filtered or suspicious email is in its headers, but they come in reverse order, with folded lines and different time zones. The tool puts the Received lines in chronological order, calculates the time between hops in UTC and tabulates the Authentication-Results.

How to use it

  1. Open the original header in your mail client (Outlook: File › Properties › Internet headers; Gmail: Show original) and paste the header section.
  2. Do not add the body; anything after the first blank line is ignored. Press Calculate.

Fields

Email header
Header section only. Data does not leave your browser.

Worked example

InputValue
Email header
Received: from AM9P191MB1234.EURP191.PROD.OUTLOOK.COM (2603:10a6:20b:3a::12)
 by DB9P191MB5678.EURP191.PROD.OUTLOOK.COM with HTTPS; Mon, 16 Nov 2026 09:12:40 +0000
Received: from mail.gonderen.example (198.51.100.20) by AM9P191MB1234.mail.protection.outlook.com
 (10.167.240.10) with Microsoft SMTP Server; Mon, 16 Nov 2026 09:11:10 +0000
Received: from [192.0.2.15] by mail.gonderen.example with ESMTPSA id 1a2b3c;
	Mon, 16 Nov 2026 12:11:05 +0300
Authentication-Results: spf=pass (sender IP is 198.51.100.20)
 smtp.mailfrom=gonderen.example; dkim=pass (signature was verified)
 header.d=gonderen.example; dmarc=pass action=none header.from=gonderen.example;compauth=pass reason=100
DKIM-Signature: v=1; a=rsa-sha256; d=gonderen.example; s=k1; h=from:to:subject:date; bh=abc=; b=def=
From: Ayşe Demir <[email protected]>
To: [email protected]
Subject: Teklif
Date: Mon, 16 Nov 2026 12:11:03 +0300
Message-ID: <[email protected]>

Expected result: 3 hops: the sending server 5 s after the client, then Microsoft's edge server 1 min 30 s later; SPF, DKIM and DMARC pass.

The first Received line is in +0300, the others in +0000; the tool converts all to UTC. The 90-second delay happened between the sending server and Microsoft; long delays usually come from greylisting or the sender's queue.

Method and assumptions

Header lines are unfolded per RFC 5322 (lines starting with whitespace continue the previous header). Received headers are prepended by each server, so they are ordered bottom to top.

The date after the last ; of each Received line is parsed with its time zone and converted to UTC. The delay is the difference between consecutive hops; a negative value indicates clock skew.

spf, dkim, dmarc, arc and compauth results are read from Authentication-Results; d= and s= from DKIM-Signature.

Using the result and troubleshooting

The hop with the large delay shows which server is the problem. A negative delay means that server's clock is wrong (check NTP).

If authentication fails, check the sending domain with the SPF Record Checker and DKIM Selector Lookup.

Limits and common mistakes

  • Received headers can be added by the sender; the lower part of the chain (before your own servers) cannot be verified.
  • It does not replace Microsoft 365 message trace or server logs.

Frequently asked questions

Is it safe to paste a header?

The analysis runs entirely in your browser; the header is not sent to a server, the URL or analytics. You can still mask personal addresses with the Log Masking Tool before sharing.

Related tools and service

  • SMTP Error Code LookupDecodes the SMTP code in a bounced email into class, subject and detail and tells you whether the error is permanent or temporary.
  • SPF Record CheckerExpands an SPF record with its include and redirect chain, counts the DNS lookup budget and shows structural errors.

Related service: Microsoft 365, Azure, AWS and Google Cloud Services

Systems online tools · See all online tools