Does opening an EML file contact the sender or load tracking pixels?
No. The message is parsed in a browser worker. HTML remains source text and remote URLs are not requested.
Open an EML message locally, decode MIME headers and transfer encodings, inspect the nested part tree, and preview or download attachments without contacting remote resources.
Paste raw RFC 5322 source or choose an .eml file. HTML stays source-only, attachments use passive previews, and no address or remote resource in the message is requested.
DecodeLens unfolds RFC 5322 headers, decodes RFC 2047 display text and RFC 2231 filenames, builds the nested MIME tree, and opens Base64 or quoted-printable parts as local bytes. Attachments can use the same passive file preview system as other DecodeLens tools.
Continue with tools that decode, convert, inspect, or verify the same data.
Decode Base64 text or files, or encode UTF-8 text and raw file bytes locally.
Open toolBrowse ZIP, TAR, TAR.GZ, and GZIP entries, preview supported files, and download individual entries.
Open toolInspect PEM or DER certificates, identity, validity, algorithms, SANs, extensions, fingerprints, and chain signatures.
Open toolAnalyze HAR requests, failures, timing, transfer sizes, bodies, and sensitive fields; export a separate redacted copy.
Open toolLoad the example to follow a multipart/mixed message into multipart/alternative text and HTML bodies, then open the transfer-decoded JSON attachment in the shared preview.
RFC 5322 headers + multipart MIME bodydecoded headers + MIME tree + passive attachment previewNo. The message is parsed in a browser worker. HTML remains source text and remote URLs are not requested.
No. That value is an Authentication-Results claim written by another mail system. Independent DKIM verification requires the signed header set, canonicalization, DNS key retrieval, and cryptographic checks.
Yes. Select an attachment to decode its MIME transfer encoding, inspect the detected file type, and download the resulting local bytes.