otlite · Email
Install MailAccess on Linux or macOS in one command
MailAccess checks an email address against a large set of platforms for registration, groups the hits into likely identities, and flags addresses seen in breach data. It is a newer alternative to Holehe with broader coverage.
MailAccess in three lines
pipx install otlite
otlite install mailaccess
otlite run mailaccess -- e:jane@example.comRuns KatrielMoses/MailAccess (MIT, ★ 1.4k, otlite 1.2.1, catalog updated Oct 23, 2026). otlite installs and runs it at a tested version; it does not change or verify the tool itself.
What MailAccess is for
- Broad registration checks on one address.
- A second opinion next to Holehe.
Typed inputs for MailAccess
otlite translates these prefixes into MailAccess's own flags. Anything else after -- is passed through unchanged, so every original flag still works.
- e:
- Email ·
otlite run mailaccess -- e:jane@example.com - d:
- Domain ·
otlite run mailaccess -- d:example.com
Run every installed tool that takes the same input at once: otlite run --all e:jane@example.com
otlite marks it dual-use, so it asks you to accept a responsible-use notice before it installs.
Where the results go
Every run lands under ./results/mailaccess/<target>/ as a timestamped output file, a .meta.json sidecar (the exact command, start and end time, exit code, and the SHA-256 of the output), and a .envelope.json with the entities found, in the same shape for every tool. List runs with otlite results, group them with --case, compare the last two with otlite diff mailaccess <target>, and pull indicators out with otlite extract mailaccess.
Before you run it
- Newer project; verify surprising hits by hand.
Update, remove, inspect
otlite info mailaccess # inputs, keys, an example command
otlite example mailaccess # sample output, where there is one
otlite update mailaccess # move to the next tested version
otlite remove mailaccess # delete its virtualenvFull reference: the otlite docs, and the tool's own README on GitHub.
Pairs with
When open-source isn't enough
MailAccess flags that an address appears in breaches. SearchIn's leak providers return the rows.
FAQ
MailAccess with otlite, answered
How do I install MailAccess on Kali, Ubuntu, or macOS?
Install otlite once with pipx install otlite (or the one-line installer on the otlite page), run otlite init, then otlite install mailaccess. The tool lands in its own virtualenv under ~/.otlite/, pinned to a version that was tested, so nothing touches your system Python. otlite doctor prints the command that fixes a missing git or venv module.
Which inputs does MailAccess take through otlite?
e: (email), d: (domain). otlite maps each prefix to MailAccess's own flag. Everything after -- that is not a typed input is passed through unchanged, so the original flags still work.
Where does otlite save MailAccess results?
Under ./results/mailaccess/<target>/ in the folder you run from, as a timestamped output file plus a .meta.json sidecar (the exact command, timing, exit code, and SHA-256) and a .envelope.json with the entities found. Add --case <name> to group runs, otlite results to list them, and otlite diff mailaccess <target> to compare the last two.
Does MailAccess need an API key or a login?
No key is required for the basic run. Optional keys, where the project supports them, go in with otlite keys set NAME and are passed only to tools that declare them.
Can I run MailAccess together with other tools?
Yes. otlite run --all e:jane@example.com runs every installed tool that takes email input, in parallel, including MailAccess. Save the combination as a playbook to repeat it.