PAGES
← all tools
◆ Reconnaissance & OSINT

h8mail

2.5.5 open-source

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.

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

all 6 features, with the evidence for each →

Languages

Not documented

Features

6 capabilities · 3 backed by code, an API document or a real run

Built from h8mail's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

What h8mail offers you

  • Command-line interface1
  • CSV data export1
  • JSON data export1
All capabilities 6 capabilities
Breach lookup verified Performs OSINT breach lookups against discovered email targets; skips lookup and exits cleanly when no email targets are found. 12 releases · 4 other sources · first seen May 2019

release 12 total

  • Adds Breachdirectory.tk API integration with its key included in the config template 2.5.5 · Jan 2021 · source · release history
  • Adds support for the intelx.io API to retrieve additional intelligence including clear text passwords 2.5.3 · Jul 2020 · source · release history
  • first / last seen time fields are now included in output 2.5.1 · Apr 2020 · source · release history
  • Integrates the [Dehashed](https://dehashed.com/) API as a new data provider source 2.5 · Jan 2020 · source · release history
  • Adds Scylla.sh API for email, password, IP, domain, and hash queries 2.4 · Oct 2019 · source · release history
  • Removed old HIBP v2 calls, stopping support for HIBP version 2 data sources 2.4 · Oct 2019 · source · release history

we ran it

  • The tool fetched http://dvwa, received an HTTP 302 redirect response, and extracted no email addresses from the page. Aug 2026 · the full run
  • The tool fetched http://dvwa, received an HTTP 302 redirect, extracted no email addresses from the response, and exited cleanly (status 0) after printing 'No targets found in URLs. Quitting'. Aug 2026 · the full run

example

  • Search Breach Compilation with API key h8mail -t targets.txt -bc ../Downloads/BreachCompilation/ -k "snusbase_token=$snusbase_token"
  • Query a single email target h8mail -t target@example.com
URL input and email extraction verified suggested Accepts URLs via string arguments or files (with pattern matching and glob support) and scrapes the fetched pages for email addresses to use as targets. 1 release · 5 other sources · first seen Jan 2020

Suggested capability: Attack surface inventory. This is our guess, not confirmed.

Also counts toward: Command-line interface

release

  • Adds --url (shorthand -u) CLI flag to fetch targets from a single or list of URLs for automated scanning 2.5 · Jan 2020 · source · release history

command line

  • --url — Either string inputs or files. Supports URL pattern matching from input or file, filepath globing and multiple arguments. Parse URLs page for emails. Requires http:// or https:// in URL. 2.5.pre-release · Jan 2020 · command-line history

we ran it

  • The tool fetched http://dvwa, received an HTTP 302 redirect, and extracted no email targets from the response. Aug 2026 · the full run

example

  • Pull a list of email targets from a remote text file to scan across all available integrations h8mail --target target.txt --urls https://example.com/breach_list.txt 2.5 · Jan 2020 · source
  • Query IP and power-chase related targets h8mail -t 42.202.0.42 -q ip -c h8mail_config_priv.ini -ch 2 --power-chase
  • Chase related emails from cleartext dump h8mail -t admin@evilcorp.com -lb /tmp/4k_Combo.txt -ch 10 -k "hunterio=ABCDE123"
JSON output verified Writes results to a JSON file specified by the user. 1 release · 2 other sources · first seen Jan 2021

Also counts toward: JSON data export

release

  • Adds -j / --json CLI flags to output results in JSON format instead of the default text view 2.5.5 · Jan 2021 · source · release history

command line

example

  • Scan a target and save the structured results to a file for downstream processing h8mail -t test@gmail.com -j test.json 2.5.5 · Jan 2021 · source
Breach timeline shipped Provides a chronological view of when a specific email address was exposed in data breaches. 1 other source · first seen Apr 2020

example

  • View the breach timeline for a specific email address h8mail target -t user@example.com --first-last-seen 2.5.1 · Apr 2020 · source
CSV output shipped Exports results to a CSV file specified by the user. 1 other source

Also counts toward: CSV data export

example

  • Bulk targets with config and CSV output h8mail -t targets.txt -c config.ini -o pwned_targets.csv
Local breach dataset processing shipped Processes local compressed files, such as gzip archives, to access breached data. 1 other source

example

  • Search gzip files, skip default checks h8mail -t targets.txt -gz /tmp/Collection1/ -sk

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. 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 →

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…

Explore the full chart →

Releases

Show

8 entries

  1. January 20211
  2. July 20201
  3. April 20201
  4. January 20201
  5. October 20191
  6. August 20191
  7. June 20191
  8. May 20191
    Show

    8 entries

    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.

    1. Contributors 0 ±0 vs prior 12 months
    2. Maintainers 0 +0 joined · −0 left, last 12 months
    3. Bus factor 0 committers behind half the commits
    4. Community-filed 100% of issues opened, last 12 months
    5. Median time to close not measured issues closed, last 12 months
    6. Open backlog 26 of 135 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 26
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars 5,309
    Issue themes, last 12 months
    • 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.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →