osintverse-community/mailcat
Finds existing email addresses for a nickname across 25+ mail providers
No key · Python wheel
5 tools. 2 run with ot in a sandbox on Windows, macOS and Linux; 3 with otlite on Linux and macOS, no Docker. Compare them side by side ↓
People often use the same handle as the local part of their email address, and developers leave an address in every git commit they push. These tools check which mail providers have a mailbox for a handle, read the addresses from a GitHub user's public commits and keys, and find linked accounts that expose an address.
Windows, macOS and Linux, with Docker or Podman. Each tool runs in a read-only container that can reach only the sites it declares, and every result comes back in the same JSON shape.
Finds existing email addresses for a nickname across 25+ mail providers
Looks up a GitHub user's public profile, SSH and GPG keys, and email addresses from their commits
ot install osintverse-community/mailcat osintverse-community/osgintInstalls the first 2 in one go; ot auto u:… then runs every installed tool that takes an username and saves the results. No ot yet? Install it in one line.
Linux and macOS. otlite installs each one with pip or git into its own virtualenv, pinned to a version it has tested: otlite install linkook.
| osintverse-community/ | None | Online, passive | Yes | Python | No reports yet | fewer than 10 | |
| osintverse-community/ | account, email, person, url | None | Online, passive | Yes | Docker | No reports yet | fewer than 10 |
Facts from each tool's manifest and what people report about whether it works. "Reaches" says whether a run stays offline, reads public sources, sends requests about the target, or may notify them.
Every registry tool here runs on your machine in a sandbox, and ot auto u:… runs all the installed ones on one value.
No. It asks each provider's API or mail server whether the mailbox exists without delivering a message, so the owner isn't notified.
Every git commit records an author address. Unless the author set GitHub's no-reply address, pushing commits to a public repository publishes it, and the GitHub API returns it.
No. ot runs each tool on your own machine in a read-only container that can only reach the sites the tool declares, and results stay in your results folder. The registry only counts installs.
Most tools here work without one; the row says "Key required" when one is needed, and ot keys set stores it in your OS keychain so only that tool's container sees it.