Email Header Analyzer

No. It only analyzes manually supplied text in a local worker. It does not fetch DNS records, connect to a mailbox, read messages or send email.

No. The tool summarizes method=result claims in Authentication-Results. Such headers can be forged outside the recipient trust boundary. It does not validate signatures, SPF authorization, DMARC alignment or ARC seals.

Received headers are reversed from source order, so the bottom field is shown first. They are not sorted by timestamp. Adjacent parsed UTC timestamps yield estimated differences; clock skew, forged headers and nonstandard ordering can make them negative or misleading.

English month names, four-digit years from1900, valid calendar/time and numeric ±HHMM zones, optional weekday and seconds. -0000 is represented as UTC with unknown original local zone. Legacy named zones, obsolete two-digit years and leap seconds remain unresolved.

Address fields, subjects, message IDs, queue IDs, authentication properties, signatures and raw header values are not exported. From/by routing tokens are masked by default; a public-sample mode can show simple host/IP tokens. Header names/counts, timestamps, known protocol tokens and declared authentication methods/results remain visible.

100,000 characters,500 header fields,100 Received fields and20 comment levels. Continuation lines are unfolded. Text after the first blank header/body separator is ignored. Routing supports simple from/by/with tokens; extended routes and some authentication syntax are outside scope. JSON/text include authentication summaries; CSV contains only the timeline.