otinstaller · Web and search
Install Sitedorks on Linux in one command
Sitedorks builds search-engine queries that look for a term across a curated set of sites, such as paste sites, code hosts, and social networks, and opens them in your browser. It saves typing the dorks by hand.
Sitedorks in three lines
pipx install otinstaller
ot install sitedorks
ot run sitedorks -- d:example.comRuns Zarcolio/sitedorks (GPL-3.0, ★ 1.1k, otinstaller v0.0.4, registry updated Oct 13, 2026). otinstaller installs and runs it; it does not change or verify it.
What Sitedorks is for
- Checking where a company name or domain appears across paste and code sites.
- Bug bounty scope discovery with the built-in program lists.
Typed inputs for Sitedorks
otinstaller translates these prefixes into Sitedorks's own flags. Anything else after -- is passed through unchanged, so every original flag still works.
- d:
- domain ·
ot run sitedorks -- d:example.com - url:
- url ·
ot run sitedorks -- url:https://example.com
Run every installed tool that takes the same input at once: ot run --all d:example.com
Where the results go
Every run lands under ./results/sitedorks/<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 sitedorks <target>, and pull indicators out with ot extract.
Before you run it
- It opens browser tabs rather than scraping, so there is no file output to keep. Use ot run --case for the command record.
Update, remove, inspect
ot info sitedorks # inputs, flags, keys
ot example sitedorks # sample output
ot update sitedorks # move to the next tested version
ot remove sitedorks # delete its virtualenvFull reference for this tool: docs for sitedorks.
Pairs with
FAQ
Sitedorks with otinstaller, answered
How do I install Sitedorks on Kali or Ubuntu?
Install otinstaller once with pipx install otinstaller, run ot init, then ot install sitedorks. 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 Sitedorks take through otinstaller?
d: (domain), url: (url). otinstaller maps each prefix to Sitedorks'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 Sitedorks results?
Under ./results/sitedorks/<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 sitedorks <target> to compare the last two.
Does Sitedorks 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 Sitedorks together with other tools?
Yes. ot run --all d:example.com runs every installed tool that accepts domain input, in parallel, including Sitedorks. Save the combination as a playbook to repeat it.