otinstaller · Frameworks

Install OWASP Nettacker on Linux in one command

OWASP Nettacker runs port scans, service detection, and vulnerability checks against hosts and ranges, and writes HTML or JSON reports. The otinstaller registry lists it under the name opendoor.

OWASP Nettacker in three lines

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

Runs OWASP/Nettacker (Apache-2.0, ★ 5.6k, otinstaller v0.0.4, registry updated Oct 13, 2026). otinstaller installs and runs it; it does not change or verify it.

What OWASP Nettacker is for

Service and vulnerability sweeps on infrastructure you own or are contracted to test.

Typed inputs for OWASP Nettacker

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

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

Before you run it

Active scanner throughout. Written authorisation first.
The registry name is opendoor: ot install opendoor.

Update, remove, inspect

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

Full reference for this tool: docs for opendoor.

Pairs with

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.

FinalRecon

FinalRecon runs a set of web recon checks against a URL in one go: headers, SSL certificate, WHOIS, crawler, DNS, subdomains, directory search, and a port scan.

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.

FAQ

OWASP Nettacker with otinstaller, answered

How do I install OWASP Nettacker on Kali or Ubuntu?

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

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

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

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

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