otlite · Username
Install Nexfil on Linux or macOS 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 otlite
otlite install nexfil
otlite run nexfil -- u:jane_doeRuns thewhiteh4t/nexfil (MIT, ★ 2.6k, 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 Nexfil is for
- Another username pass next to Sherlock and Maigret.
- Fast checks in scripts with the original -u flag.
Typed inputs for Nexfil
otlite translates these prefixes into Nexfil's own flags. Anything else after -- is passed through unchanged, so every original flag still works.
- u:
- Username ·
otlite run nexfil -- u:jane_doe
Run every installed tool that takes the same input at once: otlite run --all u:jane_doe
Where the results go
Every run lands under ./results/nexfil/<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 nexfil <target>, and pull indicators out with otlite extract nexfil.
Before you run it
- Detection rules are updated less often than Sherlock's; verify hits by hand.
Update, remove, inspect
otlite info nexfil # inputs, keys, an example command
otlite example nexfil # sample output, where there is one
otlite update nexfil # move to the next tested version
otlite remove nexfil # delete its virtualenvFull reference: the otlite docs, and the tool's own README on GitHub.
Pairs with
FAQ
Nexfil with otlite, answered
How do I install Nexfil 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 nexfil. 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 Nexfil take through otlite?
u: (username). otlite 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 otlite save Nexfil results?
Under ./results/nexfil/<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 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 with otlite keys set NAME and are passed only to tools that declare them.
Can I run Nexfil together with other tools?
Yes. otlite run --all u:jane_doe runs every installed tool that takes username input, in parallel, including Nexfil. Save the combination as a playbook to repeat it.