otinstaller · Username
Install Nexfil on Linux in one command
Nexfil checks a username against a few hundred sites and prints the profile URLs that exist. It is quick and has a small dependency set, which makes it a good extra opinion.
Nexfil in three lines
pipx install otinstaller
ot install nexfil
ot run nexfil -- u:jane_doeRuns thewhiteh4t/nexfil (MIT, ★ 2.6k, otinstaller v0.0.4, registry updated Oct 13, 2026). otinstaller installs and runs it; it does not change or verify it.
What Nexfil is for
- Another username pass next to Sherlock and Maigret.
- Fast checks in scripts with the original -u flag.
Typed inputs for Nexfil
otinstaller translates these prefixes into Nexfil's own flags. Anything else after -- is passed through unchanged, so every original flag still works.
- u:
- username ·
ot run nexfil -- 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/nexfil/<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 nexfil <target>, and pull indicators out with ot extract.
Before you run it
- Detection rules are updated less often than Sherlock's; verify hits by hand.
Update, remove, inspect
ot info nexfil # inputs, flags, keys
ot example nexfil # sample output
ot update nexfil # move to the next tested version
ot remove nexfil # delete its virtualenvFull reference for this tool: docs for nexfil.
Pairs with
FAQ
Nexfil with otinstaller, answered
How do I install Nexfil on Kali or Ubuntu?
Install otinstaller once with pipx install otinstaller, run ot init, then ot install nexfil. 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 Nexfil take through otinstaller?
u: (username). otinstaller maps each prefix to Nexfil'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 Nexfil results?
Under ./results/nexfil/<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 nexfil <target> to compare the last two.
Does Nexfil 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 Nexfil together with other tools?
Yes. ot run --all u:jane_doe runs every installed tool that accepts username input, in parallel, including Nexfil. Save the combination as a playbook to repeat it.