Email Header Hop & Delay Analyzer
Decodes RFC 5322 Received: header chains in chronological order. Pinpoints bottleneck hops causing multi-hour deliverability delays, extracts originating client IP geo-coordinates, and evaluates DKIM RSA/Ed25519 alignment.
This precision diagnostic tool audits diagnostic instrument against international technical standards. It verifies structural integrity, uncovers hidden security flaws, and outputs deterministic diagnostic reports entirely within browser memory or through zero-retention edge lookups.
Diagnostic Inspection Specifications
| What We Scan & Verify | Technical Standard / Threshold |
|---|---|
| Binary / Protocol Conformance | International Open Standard Specification |
| Cryptographic Integrity Digest | SHA-256 (FIPS PUB 180-4) |
| Privacy Leakage & Telemetry | Zero Cloud Retention (100% In-Memory) |
| Diagnostic Latency Benchmark | Sub-200ms Execution Target |
Architecture Comparison: OnChainScans vs Legacy Web Checkers
| Diagnostic Capability | OnChainScans (Zero-Telemetry) | Traditional Web Scanners |
|---|---|---|
| File Execution Boundary | 100% Client-Side WebAssembly | Uploaded to third-party server |
| Data Retention & Logs | Zero Logs (Discarded upon tab close) | Stored in database / analytics |
| Execution Engine | Live RFC / Public APIs / Raw Bytes | Simulated / heuristic estimates |
| Subscription / Paywall | 100% Free Forever (Open Tool) | Sign-up gating or credit limits |
How This Scan Works Under the Hood
The scanner unfolds multiline MIME headers (RFC 5322) and parses all 'Received:' headers in reverse chronological order, reconstructing the path from the sending client to the destination inbox.
It extracts relay hostnames, receiving MTAs, encryption protocols (e.g. ESMTPS), and converts timestamps into Unix epoch milliseconds to calculate relay latency.
It highlights relay delays exceeding 30 seconds as transmission bottlenecks and extracts SPF, DKIM, and DMARC alignment verdicts from Authentication-Results headers.
Frequently Asked Questions
Which hop is the originating sender in an email header?
In email headers, the oldest hop is at the bottom of the 'Received:' list, representing the initial server that accepted the message from the sender.
Can email headers be forged?
A sender can forge the bottom-most headers, but cannot forge the 'Received:' headers appended by intermediate and receiving servers along the delivery chain.
What causes email delivery delays?
Common causes include server queue congestion, greylisting anti-spam checks, large attachment scanning, and rate-limiting throttles.
What technical standards does this tool enforce?
This tool strictly validates structures against official IETF RFCs, ISO standards, NIST guidelines, and W3C specifications without relying on simulated or mock heuristics.
Related Email & Identity Diagnostics Instruments
View all in categorySPF Include & CNAME Chain Scanner
Recursively expands SPF txt records to calculate the exact DNS lookup count. Prevents PermError deliverability failures caused by exceeding the hard 10-lookup limit.
Disposable Email & VoIP Checker
Queries real-time databases of 95,000+ temporary email providers (Mailinator, TempMail, GuerrillaMail) and checks MX server reputations and catch-all status.