OSINTverse

otinstaller · Domain and DNS

Install BBOT on Linux in one command

BBOT is a recursive scanner that starts from a domain or IP, discovers subdomains, hosts, and services, and feeds each finding back in as a new target. Presets choose between passive enumeration and active scanning.

BBOT in three lines

pipx install otinstaller
ot install bbot
ot run bbot -- d:example.com

Runs blacklanternsecurity/bbot (AGPL-3.0, ★ 11k, otinstaller v0.0.4, registry updated Oct 13, 2026). otinstaller installs and runs it; it does not change or verify it.

What BBOT is for

  • Subdomain enumeration that keeps going as it finds new names.
  • Passive recon with the subdomain-enum preset when you must stay quiet.
  • Exports to JSON or CSV for a spreadsheet or a case.

Typed inputs for BBOT

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

d:
domain · ot run bbot -- d:example.com

It also takes ip input through its own flags; there is no typed prefix for those yet.

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/bbot/<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 bbot <target>, and pull indicators out with ot extract.

Before you run it

  • Active presets probe the target. Only run them with written authorisation.
  • The first run installs module dependencies, which can take a few minutes.

Update, remove, inspect

ot info bbot      # inputs, flags, keys
ot example bbot   # sample output
ot update bbot    # move to the next tested version
ot remove bbot    # delete its virtualenv

Full reference for this tool: docs for bbot.

Pairs with

dnstwist generates lookalike domains for a name you give it, including typos, homoglyphs, and extra TLDs, then checks which ones are registered and what they resolve to.
ctfr lists the subdomains of a domain by reading Certificate Transparency logs through crt.sh.
SpiderFoot runs two hundred-odd modules against a domain, IP, email, or username and links what they return into one graph.

FAQ

BBOT with otinstaller, answered

How do I install BBOT on Kali or Ubuntu?

Install otinstaller once with pipx install otinstaller, run ot init, then ot install bbot. 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 BBOT take through otinstaller?

d: (domain). otinstaller maps each prefix to BBOT'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 BBOT results?

Under ./results/bbot/<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 bbot <target> to compare the last two.

Does BBOT 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 BBOT together with other tools?

Yes. ot run --all d:example.com runs every installed tool that accepts domain input, in parallel, including BBOT. Save the combination as a playbook to repeat it.