Which option shows step-by-step output for NMAP scripts?

• A. --verbose
• B. --script-trace
• C. --debug-commands
• D. --log-errors

Answer: (B)

Step-by-step visibility into how NSE (Nmap Scripting Engine) scripts run is what this option provides. Enabling script-trace prints the flow of each script as it executes—showing script function calls, decisions, and data being processed—so you can see exactly how a script operates on the target and where it may be returning results or encountering issues. This is ideal for debugging and learning how specific NSE scripts behave.

In contrast, verbose adds general scan progress and network-level detail, not the granular internal steps of each script. The debug-commands option logs the actual commands Nmap runs, which helps you see what is being executed at the engine level but doesn't give the full script execution trail. Log-errors focuses on recording errors, not the full step-by-step script activity.

Therefore, the best option for observing the detailed, step-by-step output of NSE scripts is script-trace.