RustScan Fast Port ScannerStep-by-step reference: scan ports in seconds with RustScan and pipe results to Nmap. Educational use only.FAQ

What is RustScan?

RustScan is a free, open-source port scanner written in Rust. It finds open ports in seconds using an asynchronous sweep, then automatically passes the results to Nmap for service detection and scripting. It is a discovery accelerator: RustScan finds where to look, Nmap tells you what is there.

Is using RustScan legal?

RustScan itself is a legitimate open-source security tool. Scanning any host or network without explicit written permission is illegal. Its high speed can also stress fragile networks, so test only systems you own or are authorized to assess, and keep batch sizes reasonable.

How do I install RustScan?

Install it with cargo install rustscan if you have Rust, download the .deb from the GitHub releases page and run sudo dpkg -i on Debian-based systems, or pull the Docker image. Also install Nmap with sudo apt install nmap -y, since RustScan hands results to it.

How do I run a basic RustScan scan?

Run rustscan -a 192.168.1.10 -- -sV -sC against your authorized lab target. RustScan sweeps all ports in seconds, then Nmap runs version detection and default scripts on the open ports only.

How do I control scan speed?

Use -b to set the batch size and -t to set the per-probe timeout in milliseconds. Lower batch sizes are gentler on fragile networks. Limit the range with -r when you only care about specific ports.

What is the difference between RustScan and Nmap?

RustScan is optimized for one job: finding open ports as fast as possible. Nmap is slower but far deeper: versions, OS detection, and scripting. The standard workflow is RustScan first for speed, then Nmap on the open ports for depth.

Can RustScan scan UDP ports?

Yes. Add the -u flag to include UDP services alongside TCP. UDP scans are slower because closed UDP ports usually stay silent, so pair -u with a narrow -r range.

Why did my scan find nothing?

Verify the target is reachable, extend the timeout with -t 3000, and lower the batch size with -b 500. Firewalls and VPN routing are the most common reasons probes never return.

All tools · Sitemap · Games