otinstaller · Username
Install Sherlock on Linux in one command
Sherlock checks a username against several hundred sites and reports where a profile with that exact handle exists. It returns a list of profile URLs, nothing about who owns them.
Sherlock in three lines
pipx install otinstaller
ot install sherlock
ot run sherlock -- u:jane_doeRuns sherlock-project/sherlock (MIT, ★ 93k, otinstaller v0.0.4, registry updated Oct 13, 2026). otinstaller installs and runs it; it does not change or verify it.
What Sherlock is for
- A first pass on a handle before deeper work.
- Spotting which platforms a brand or project name is already taken on.
- Feeding profile URLs into socid-extractor or Maigret for details.
Typed inputs for Sherlock
otinstaller translates these prefixes into Sherlock's own flags. Anything else after -- is passed through unchanged, so every original flag still works.
- u:
- username ·
ot run sherlock -- u:jane_doe
Run every installed tool that takes the same input at once: ot run --all u:jane_doe
Where the results go
Every run lands under ./results/sherlock/<target>/ as a timestamped output file plus a .meta.json sidecar: the exact command, start and end time, exit code, and the SHA-256 of the output. Group runs with --case, compare the last two with ot diff sherlock <target>, and pull indicators out with ot extract.
Before you run it
- Sites change their responses often, so expect a few false positives; open each hit.
- Rate limits on popular sites can mark a profile as missing when it exists. Re-run with --timeout raised.
Update, remove, inspect
ot info sherlock # inputs, flags, keys
ot example sherlock # sample output
ot update sherlock # move to the next tested version
ot remove sherlock # delete its virtualenvFull reference for this tool: docs for sherlock.
Pairs with
When open-source isn't enough
Sherlock tells you where a handle exists. SearchIn's people-search and leak providers return the profile fields and breach records behind it.
FAQ
Sherlock with otinstaller, answered
How do I install Sherlock on Kali or Ubuntu?
Install otinstaller once with pipx install otinstaller, run ot init, then ot install sherlock. The tool lands in its own virtualenv under ~/.otinstaller/, pinned to a version that was tested on Ubuntu, so nothing touches your system Python. ot doctor flags a missing git or venv module.
Which inputs does Sherlock take through otinstaller?
u: (username). otinstaller maps each prefix to Sherlock's own flag. Everything after -- that is not a typed input is passed through unchanged, so the original flags still work.
Where does otinstaller save Sherlock results?
Under ./results/sherlock/<target>/ in the folder you run from, as a timestamped output file plus a .meta.json sidecar with the exact command, timing, exit code, and SHA-256. Add --case <name> to group runs, and ot diff sherlock <target> to compare the last two.
Does Sherlock need an API key or a login?
No key is required for the basic run. Optional keys, where the project supports them, go in ~/.otinstaller/.env and are passed only to tools that declare them.
Can I run Sherlock together with other tools?
Yes. ot run --all u:jane_doe runs every installed tool that accepts username input, in parallel, including Sherlock. Save the combination as a playbook to repeat it.
Why does Sherlock report accounts that do not exist?
Some sites answer every profile URL with a page instead of a 404, and Sherlock's detection rule for that site may be stale. Treat the output as leads and open each one. Running Maigret on the same handle gives a second opinion.