CLI Reference
Commands
The command layout stays explicit so the user can tell what the framework is about to do before it does it.
scan DOMAIN
Run the complete workflow from passive collection through findings and reports.
passive DOMAIN
Use passive sources only for a lower-noise first pass.
ports TARGET
Focus on service discovery without the whole web workflow.
dns DOMAIN
Inspect naming and resolution data without broader probing.
lab
Start the safe local practice target.
about / explain / manual
Read framework guidance without leaving the terminal.
CLI Reference
Global Flags
These switches show up across multiple commands so the CLI feels consistent instead of fragmented.
| Flag | Meaning | Typical Use |
|---|---|---|
--threads N | Set worker concurrency | Control speed versus stability |
--format cli|txt|html|json | Select the output style | Switch between operator, report, or automation views |
--output PATH | Write reports to a specific location | Save a named artifact |
--monitor | Compare the run against recon memory | Track change over time |
--headless | Use browser-backed rendering where available | Handle JS-heavy targets |
--web-session | Launch the local browser control panel | Operate through the web UI |
CLI Reference
Syntax Guide
The basic shape stays predictable: verb first, target second, then whatever tuning flags are needed.
shell
# General shape
$ asrfacet-rb COMMAND TARGET [--flags values]
# Examples
$ asrfacet-rb scan example.com --format html
$ asrfacet-rb passive example.com --threads 12
$ asrfacet-rb ports api.example.com --ports top100
$ asrfacet-rb manual workflow
Operator Habit
When you are unsure, start with passive or lab before escalating to scan.