A MESSAGE IS MORE THAN ITS SUBJECT LINE.
See what the
mail file contains.
Inspect a downloaded .eml without opening its HTML or attachments. Read repeated headers, expose control characters and compare attachment bytes locally.
1. Open an email file
Not Outlook .msg, a mailbox or a mail client. No accounts or sending. Limits: 128 MIME parts, depth 16, 128 KiB parser header budget, 8-second stop.
Your file stays in this page. This is not authentication, malware scanning or a safety verdict.
2. Read the claims
Whole input SHA-256
Fingerprints identify bytes, not the author or safety of a message.
Repeated top-level header names
A repeated header is not automatically wrong. Received and other headers often repeat. Nothing here verifies From, SPF, DKIM or Authentication-Results.
All headers, in parser order
Unfolded values preserve encoded words. The second line decodes them for inspection only, not address interpretation. Control characters appear as \u{XXXX}; literal backslashes are doubled. Indices start at zero.
3. Compare attachment bytes
No preview, extraction or execution. Names and MIME types are file claims. Matching groups are byte-compared after decoding, not just named alike. Attached messages remain opaque. Calendar attachment text can be normalized by the parser.
4. Read decoded text
No links are made clickable. Controls are escaped; tabs/newlines are kept in this text view. This is not a lossless MIME-part or source view.
Keep the inspection
The JSON report contains mail content, headers, names, addresses and identifying hashes. It is not sanitized or anonymous. Review before sharing. Attachment bytes and HTML source are not included.