➡️
Discord |
Installation Guide |
Usage Guide
⬅️
Turns a 17 minutes Nmap scan into 19 seconds.
Find all open ports fast with RustScan, automatically pipe them into Nmap.
|
| | | | | ----------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- | |
docker pull rustscan/rustscan:v1.9.0 Usage | Read the install guide | yay -S rustscan | cargo install rustscan |
nmap on those ports.| Name | ⚡ Nmap with RustScan ⚡ | 🐢 Nmap 🐢 |
|---|---|---|
| Gif |  |
 |
| Time | 39 seconds | 17 minutes and 41 seconds |
Note This is an older gif. RustScan's current top speed is 3 seconds for all 65k ports. This gif is 26 seconds.
RustScans only job is to reduce the friction between finding open ports and inputting them into nmap.
| Installation Guide | Documentation | Discord | | -------------------------------------------------------------------------------------- | -------------------------------------------------------- | ---------------------------------------- | | 📖 Installation Guide | 📚 Documentation | 🦜 Discord |
Why spend time running fast scans and manually copying the ports, or waiting for a 20 minute scan to finish when you can just do all 65k ports in less than a minute?
RustScan running in 8 seconds and finding all open ports out of 65k.
| Name | RustScan | Nmap | Masscan | | ------------------------------------------------------------------------------------------ | -------- | ---- | ------- | | Fast | ✅ | ❌ | ✅ | | Actually useful | ❌ | ✅ | ❌ | | Realises it's not useful, and pipes the only useful data into the only useful port scanner | ✅ | ❌ | ❌ |
You need Nmap. If you have Kali Linux or Parrot OS installed, you already have Nmap. If not, follow the nmap install guide.
The easiest way to install RustScan is to use one of the packages provided for your system, such as HomeBrew or Yay for Arch Linux.
The most universal way is to use cargo, Rust's built in package manager (think Pip but for Rust). Follow this guide to installing Rust & Cargo.
If you face any issues at all, please leave a GitHub issue. I have only tested this on Linux, so there may be issues for Mac OS or Windows.
Note: sometimes Rust doesn't add Cargo to the path. Please see this issue for how to fix that.
Download the .deb file from the releases page:
https://github.com/RustScan/RustScan/releases
Run the command dpkg -i on the file.
Note: sometimes you can double click the file to achieve the same result.
Docker is the recommended way of installing RustScan. This is because:
To install Docker, follow their guide.
Once Docker is installed, you can either build your own image using the Dockerfile (alpine) provided in the repo, or alternatively, use the published Docker image like below (most convenient)
Please see our DockerHub for further our published versions. However, we recommend using our latest release v1.9.0
``` Stable and supported: rustscan/rustscan:v1.9.0
Bleeding edge (run at your own risk!): rustscan/rustscan:latest ```
We strongly recommend using the v1.9.0 tag, as this is the latest major - stable - release of RustScan. This README uses the v1.9.0 image by default, however, note that the latest image is considered experimental.
Simply run this command against the IP you want to target:
bash
docker run -it --rm --name rustscan rustscan/rustscan:v1.9.0 <rustscan arguments here> <ip address to scan>
Note: this will scan the Docker's localhost, not your own.
Once done, you will no longer need to re-download the image (except when RustScan updates) and can use RustScan like a normal application.
You will have to run this command every time, so we suggest aliasing it to something memorable.
bash
alias rustscan='docker run -it --rm --name rustscan rustscan/rustscan:v1.9.0'
Then we can scan:
bash
rustscan 192.168.1.0/24 -t 500 -b 1500 -- -A
Download the repo:
bash
git clone https://github.com/RustScan/RustScan.git
Ensure you navigate to the download location of the repo:
bash
cd /path/to/download/RustScan
Build away!
bash
docker build -t <yourimagename> .
Note for Mac users Mac OS has a very, very small ulimit size. This will negatively impact RustScan by a significant amount. Please use the Docker container, or tell RustScan to up the ulimit size on every run.
brew install rustscan
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh which I took from the Rust website https://www.rust-lang.org/tools/installcargo build --releasetarget/release/rustscanHere are all of RustScan's community distributions.
If you maintain a community distribution and want it listed here, leave an issue / pull request / Discord message or however you want to let us know.
```console $ rustscan -h
Fast Port Scanner built in Rust. WARNING Do not use this program against sensitive infrastructure since the specified server may not be able to handle this many socket connections at once. - Discord https://discord.gg/GFrQsGy - GitHub https://github.com/RustScan/RustScan
USAGE:
rustscan [FLAGS] [OPTIONS] [addresses]... [--
FLAGS: --accessible Accessible mode. Turns off features which negatively affect screen readers -h, --help Prints help information -n, --no-config Whether to ignore the configuration file or not --no-nmap Turns off Nmap -q, --quiet Quiet mode. Only output the ports. No Nmap. Useful for grep or outputting to a file -V, --version Prints version information
OPTIONS:
-b, --batch-size
ARGS:
The format is rustscan -b 500 -t 1500 192.168.0.1 to scan 192.168.0.1 with 500 batch size with a timeout of 1500ms. The timeout is how long RustScan waits for a response until it assumes the port is closed.
The batch size determines how fast RustScan is. Set it to 65k, and it will scan all 65k ports at the same time. This means at at 65k batch size, RustScan will take TIMEOUT long to scan all ports. Essentially, if timeout is 1000ms, RustScan can scan in 1 second.
Your operating system may not support this, but it is worth it to play around and see where your open file limit is. Shortly I will be releasing a dockerised version with a much larger open file limit, so this will be possible.
This binary accepts a configuration file that is read from the home directory of the user. It follows the TOML format and accepts the following fields:
addressesportsrangescan_ordercommandaccessiblequietbatch-sizetimeoutulimittoml
addresses = ["127.0.0.1", "192.168.0.0/30", "www.google.com"]
command = ["-A"]
ports = [80, 443, 8080]
range = { start = 1, end = 10 }
quiet = false
accessible = true
scan_order = "Serial"
batch_size = 1000
timeout = 1000
ulimit = 1000
This program, by default, scans 5000 ports at a time (5000 per second).
This may cause damage to a server, or may make it incredibly obvious you are scanning the server.
Servers as well as individual services can block your IP completely after a huge amount of simultaneous connections/tries, Possibly causing you to see false positives. False positives are open ports at the initial scanning process later found closed when you want to do further scanning, or connect to it.
There are 2 ways to deal with this;
rustscan -b 10 will run 10 port scans for 1 second, and then another 10 for 1 second and so on.rustscan -T 5000 will mean RustScan waits 5 seconds until it scans the next ports.You can also use both of these at the same time, to make it as slow or as fast as you want. A fun favourite is 65535 batch size with 1 second timeout. Theoretically, this scans all 65535 ports in 1 second.
Please do not use this tool against sensitive servers. It is designed mainly for Capture the Flag events, not real world servers with sensitive data.
This is the most common error found in RustScan.
The open file limit is how many open sockets you can have at any given time.
This limit changes from OS to OS.
RustScan does not automatically create defaults (other than 5000) like Nmap does with their -T1, -T2 system.
By figuring out for yourself the optimal batch size, you will know that RustScan is the most optimised port scanner for your system.
There are 2 things you can do:
Decreasing batch size slows down the program, so as long as it isn't too drastic, this is a good option.
Run these 3 commands:
bash
ulimit -a
ulimit -Hn
ulimit -Sn
They will give you an idea on the open file limit of your OS.
If it says "250", run rustscan -b 240 for a batch size of 240.
Increasing the open file limit increases speed, but poses danger. Although, opening more file sockets on the specified IP address may damage it.
To open more, set the ulimit to a higher number:
bash
ulimit -n 5000
Mac OS Mac OS has, from what I can tell, a naturally very low open file descriptor limit. The limit for Ubuntu is 8800. The limit for Mac OS is 255!
In this case, I would say it is safe to increase the open file limit. As most Linux based OS' have limits in the thousands.
Although, if this breaks anything, please don't blame me.
Windows Subsystem for Linux Windows Subsystem for Linux does not support ulimit (see issue #39).
The best way is to use it on a host computer, in Docker, or in a VM that isn't WSL.
Automatic Ulimit updating We are currently working on automatic Ulimit updating. If it is too high, it will lower itself. If it is too low, it will suggest a higher Ulimit. Watch this issue for more.
To run your own nmap commands, end the RustScan command with -- -A where -- indicates "end of RustScan flags, please do not parse anything further" and any flags after that will be entered into nmap.
RustScan automatically runs nmap -vvv -p $PORTS $IP. To make it run -A, execute the command rustscan 127.0.0.1 -- -A.
If you want to run commands such as --script (vuln and safe), you will need to enclose it in quotations like so --script '"(vuln and safe) or default"'.
This increases speed, by allowing us to process more at once. Something experimental I am working on is changing the open file limit. You can do this manually with ulimit -n 70000 and then running rustscan with -b 65535. This should scan all 65535 ports at the exact same time. But this is extremely experimental.
For non-experimental speed increases, slowly increase the batch size until it no longer gets open ports, or it breaks.
To increase accuracy, the easiest way is to increase the timeout. The default is 1.5 seconds, by setting it to 4 seconds (4000) we are telling RustScan "if we do not hear back from a port in 4 seconds, assume it is closed".
Decreasing accuracy gives some speed bonus, but my testing found that batch size dramatically changed the speed whereas timeout did, but not so much.
Howdy Space Cow-Person 🤠🌌
RustScan is always looking for contributors. Whether that's spelling mistakes or major changes, your help is wanted and welcomed here.
Before contributing, read our code of conduct.
TL;DR if you abuse members of our community you will be perma-banned 🤗
RustScan has 2 major labels for GitHub issues you should look at:
If you want to, solve the issue or comment on the issue for help.
The flow for contributing to open source software is:
And then comment on the issue that you've done.
RustScan also has some // TODO's in the codebase, which are meant more for the core team but we wouldn't say no to help with these issues.
If you have any feature suggestions or bugs, leave a GitHub issue. We welcome any and all support :D
We communicate over Discord. Click here to join our Discord community!
I cannot pay you :-( But, I can place your GitHub profile on the README under #Contributors as a thank you! :)
Please read the contributing.md file
Thanks goes to these wonderful people (emoji key):
This project follows the all-contributors specification. Contributions of any kind welcome!
