otlite · Web and records

Install Sitedorks on Linux or macOS 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 otlite
otlite install sitedorks
otlite run sitedorks -- q:acme

Runs Zarcolio/sitedorks (GPL-3.0, ★ 1.1k, 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 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

otlite translates these prefixes into Sitedorks's own flags. Anything else after -- is passed through unchanged, so every original flag still works.

q:: Search text · otlite run sitedorks -- q:acme

Sitedorks asks questions in the terminal, so otlite run --all and otlite auto skip it. Run it on its own.

Where the results go

Every run lands under ./results/sitedorks/<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 sitedorks <target>, and pull indicators out with otlite extract sitedorks.

Before you run it

It opens browser tabs rather than scraping, so there is no file output to keep. Use otlite run --case for the command record.

Update, remove, inspect

otlite info sitedorks      # inputs, keys, an example command
otlite example sitedorks   # sample output, where there is one
otlite update sitedorks    # move to the next tested version
otlite remove sitedorks    # delete its virtualenv

Full reference: the otlite docs, and the tool's own README on GitHub.

Pairs with

ParamSpider

ParamSpider pulls every archived URL for a domain from the Wayback Machine and keeps the ones with query parameters.

CrossLinked

CrossLinked scrapes search engines for LinkedIn results about a company and turns the names it finds into email addresses in the format you specify.

OnionSearch

OnionSearch sends a query to a set of dark web search engines over Tor and collects the onion URLs they return into one CSV.

FAQ

Sitedorks with otlite, answered

How do I install Sitedorks 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 sitedorks. 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 Sitedorks take through otlite?

q: (search text). otlite 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 otlite save Sitedorks results?

Under ./results/sitedorks/<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 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 with otlite keys set NAME and are passed only to tools that declare them.

Can I run Sitedorks together with other tools?

Not under --all. Sitedorks asks questions in the terminal, so otlite run --all and otlite auto skip it on purpose. Run it on its own.