otinstaller · Frameworks

Install IVRE on Linux in one command

IVRE stores and analyses scan results from Nmap, Masscan, Zeek, and passive DNS in a database, then lets you query and view them in a web UI. otinstaller installs the Python package; the scanners and database are separate.

IVRE in three lines

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

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

What IVRE is for

Keeping large scan datasets searchable.
Passive DNS and flow analysis from your own sensors.

Typed inputs for IVRE

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

d:: domain · ot run ivre -- 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/ivre/<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 ivre <target>, and pull indicators out with ot extract.

Before you run it

Needs MongoDB or another supported database and the scanners themselves. Follow the project's setup before the first run.

Update, remove, inspect

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

Full reference for this tool: docs for ivre.

Pairs with

BBOT

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.

secator

secator wraps dozens of recon and scanning tools behind one command with a shared output format, and runs them as tasks, workflows, or full scans.

OWASP Nettacker

OWASP Nettacker runs port scans, service detection, and vulnerability checks against hosts and ranges, and writes HTML or JSON reports.

FAQ

IVRE with otinstaller, answered

How do I install IVRE on Kali or Ubuntu?

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

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

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

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

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