h8mail
2.5.5 open-sourceThe section your link pointed to isn't on h8mail's page any more, so we've brought you to the top.
h8mail is an email OSINTOSINTOpen-source intelligence, collecting and analyzing information from publicly available sources. Investigators use it to learn about people, infrastructure or threats. and breach hunting tool using different breach and reconnaissance services or local breaches.
h8mail -t test@gmail.com -j test.json h8mail target -t user@example.com --first-last-seen h8mail --target target.txt --urls https://example.com/breach_list.txt h8mail gen-config h8mail --debug -t target@example.com
Summary
h8mail is an open-source, free command-line tool for email OSINT and breach hunting, run from a terminal on Windows, Linux or macOS, or via Docker or pip. It takes a single address, a bulk file of targets, or a URL to scrape for emails, then checks them against breach and reconnaissance services or local breach datasets such as Collection#1 and the Breach Compilation torrent, chasing related emails found along the way and writing results to CSV or JSON. It suits penetration testers and OSINT investigators tracking down compromised credentials rather than developers looking to integrate a library, and it sits in the reconnaissance space alongside other breach-checking and email-discovery tools. First committed in 2018 and now at 10 contributors across 11 tracked releases, it has had no commits in the past year, so treat it as stable but no longer actively maintained.
h8mail is an email OSINT and breach hunting tool using different breach and reconnaissance services or local breaches.
How h8mail helps
Which of these email addresses turn up in a known breach dataset?
checks each address against configured breach and reconnaissance services or local breach files like "Collection#1" and the Breach Compilation torrent, and reports what it finds per address
Which addresses on this page or site have leaked credentials sitting behind them?
scrapes the given URL for email patterns first, then runs the same breach and reconnaissance checks against whatever addresses it extracts
What other compromised accounts belong to the same person I'm already investigating?
takes related emails surfaced during a lookup and feeds them back into the search automatically, expanding the target list as it goes
Which of a large list of targets already appear in leaked data?
reads a bulk file of addresses, runs each through the configured services, and writes the results to CSV or JSON for later review
Can I find matches without sending anything to a third-party service?
searches local cleartext or compressed breach dumps directly on disk, using multiprocessing, without querying an external API
What password, username, IP or domain data exists for a target beyond just the email?
passes the value to premium APIs configured for that query type and returns whatever hash, password, IP or domain data those services hold
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for h8mail, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail h8mail puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
8 entries
No entries match these filters.
- January 20211
- July 20201
- April 20201
- January 20201
- October 20191
- August 20191
- June 20191
- May 20191
Project health
Issue, contributor and maintainer activity in khast3x/h8mail, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 0 ±0 vs prior 12 months
- Maintainers 0 +0 joined · −0 left, last 12 months
- Bus factor 0 committers behind half the commits
- Community-filed 100% of issues opened, last 12 months
- Median time to close not measured issues closed, last 12 months
- Open backlog 26 of 135 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 26
- Contributors / month 0
- Commits / month 0
- Stars 5,309
- other 100%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.