
Email header & .eml analyzer for SPF/DKIM/DMARC, spoofing and phishing. Runs 100% in your browser, so your emails are never uploaded.
[!IMPORTANT] Your emails never leave your device. The hosted version runs the whole analyzer inside your browser tab with WebAssembly. There is no ESHA server: the headers and
.emlfiles you open are never uploaded, stored or shared, not even with GitHub or the ESHA project.
- No uploads: analysis runs locally in a background worker in the page.
- No third parties: no CDNs, analytics, trackers, or DNS or reputation lookups.
- Enforced by the browser: the page's Content Security Policy (
connect-src 'self') blocks it from contacting any other server.- Verifiable: open your browser's DevTools, go to Network, analyze a message, and you'll see no request carrying it.
That makes it suitable for sensitive or confidential messages, such as phishing reports from colleagues or incident evidence.
Paste an email's headers, or drop the whole .eml or Outlook .msg file, and ESHA tells you where the message really came from: whether SPF, DKIM and DMARC passed, which identities don't match the sender, and which signs of phishing or spoofing it shows. Analysis runs entirely on your machine and never contacts third-party services.
Built for SOC analysts, incident responders and IT admins who triage suspicious email. ESHA started from the open-source MHA (E-Mail Header Analyzer) by @lnxg33k, and its analysis engine, interface, API and command line have since been rewritten.
Authentication and mismatches
compauth) verdicts, taken from the receiving server's Authentication-Results, or Received-SPF and DKIM-Signature when that's missingp=none DMARC policies, conflicting SPF results, and fake Authentication-Results headers inserted by the senderl= body-length tag, or that sign too few headersSender identity
paypa1), homoglyphs and Cyrillic/Greek confusables (раураl), punycode, brand names embedded in other domainsacmecorp-hr.com vs acme-corp.com), typical of invoice and payroll fraudRoute
Content (when the body is included)
javascript: and data: linksinvoice.pdf.html), and files whose content doesn't match their nameatob, Blob, msSaveOrOpenBlob, large base64 data).ics) from organisers outside the sender's domain, with their links added to the link tableOutlook .msg files: received messages keep their original internet headers, so they're analyzed exactly like an .eml, attachments and embedded messages included. Messages saved from Sent Items or Drafts have no transport headers; ESHA rebuilds From, To, Subject and Date from Outlook's properties and says the route can't be checked. Bodies stored only as RTF aren't decoded.
Spam filters: Microsoft 365 (SCL, BCL, SFV, CAT such as SPOOF or PHSH) and SpamAssassin verdicts.
Indicators and export
to_ids attributes, so benign mail services aren't marked malicious.Every result is combined into a 0–100 risk score. Each finding has a plain-language explanation, advice on what to do and its MITRE ATT&CK techniques. The report is split into tabs: Findings, Route, Authentication, Links & attachments (when the message body is included) and All headers. The score is heuristic: treat it as triage, not proof.
ESHA is published as a static site on GitHub Pages: https://0xanalyst.github.io/email-security-header-analyzer/
The hosted version runs the same Python analyzer inside your browser tab with Pyodide (WebAssembly). Headers and .eml files you open are never uploaded. GitHub serves the page's files and doesn't see any email content. The page's Content Security Policy (connect-src 'self') blocks it from contacting any other server, and Pyodide is hosted with the site rather than loaded from a CDN. The first visit downloads about 14 MB (less after compression), which your browser then caches.
To build and preview the static site yourself:
pip install -r requirements.txt
python scripts/build_site.py # writes ./site
python -m http.server -d site 8000 # http://127.0.0.1:8000
node scripts/check_site.js site tests/samples # optional smoke test of the in-browser engine
Every push to main rebuilds and deploys the site (.github/workflows/pages.yml).