otinstaller · Frameworks
Install secator on Linux in one command
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. It installs the underlying tools for you.
secator in three lines
pipx install otinstaller
ot install secator
ot run secator -- d:example.comRuns freelabz/secator (Other, ★ 1.3k, otinstaller v0.0.4, registry updated Oct 13, 2026). otinstaller installs and runs it; it does not change or verify it.
What secator is for
- Standardised JSON output across many scanners.
- Repeatable recon workflows for authorised targets.
Typed inputs for secator
otinstaller translates these prefixes into secator's own flags. Anything else after -- is passed through unchanged, so every original flag still works.
- d:
- domain ·
ot run secator -- d:example.com - u:
- username ·
ot run secator -- u:jane_doe - e:
- email ·
ot run secator -- e:jane@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/secator/<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 secator <target>, and pull indicators out with ot extract.
Before you run it
- Its workflows can be active scans. Check what a workflow does before pointing it at a host.
- Installing the wrapped tools pulls in Go and other runtimes.
Update, remove, inspect
ot info secator # inputs, flags, keys
ot example secator # sample output
ot update secator # move to the next tested version
ot remove secator # delete its virtualenvFull reference for this tool: docs for secator.
Pairs with
FAQ
secator with otinstaller, answered
How do I install secator on Kali or Ubuntu?
Install otinstaller once with pipx install otinstaller, run ot init, then ot install secator. 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 secator take through otinstaller?
d: (domain), u: (username), e: (email). otinstaller maps each prefix to secator'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 secator results?
Under ./results/secator/<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 secator <target> to compare the last two.
Does secator 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 secator together with other tools?
Yes. ot run --all d:example.com runs every installed tool that accepts domain input, in parallel, including secator. Save the combination as a playbook to repeat it.