How does --version-intensity affect version detection and when would you adjust it?

• A. It changes the output format
• B. It alters the number of targets tested
• C. It sets the timing template for scans
• D. It controls aggressiveness of probes; higher values probe more deeply but slower scans

Answer: (D)

Version detection relies on probing the service to identify versions, and the --version-intensity setting controls how aggressive Nmap is during this fingerprinting. At higher values, Nmap sends more probes and performs deeper fingerprint checks, which makes version detection more thorough and accurate but slows the scan and increases network load. At lower values, probing is lighter, so scans finish faster and are gentler on the target, but some services may be fingerprinted less reliably or not at all. You’d adjust it when you need more thorough results on a small, trusted set of hosts or for hard-to-detect services, and you’d lower it when scanning many hosts, or when you want to reduce impact on the network or minimize detection. This option doesn’t change the output format, the number of targets tested, or the timing template; those aspects come from other settings. In short, higher values increase probe aggressiveness and slow scans, while lower values decrease aggressiveness and speed things up.