naabu
v2.7.0 open-sourceThe section your link pointed to isn't on naabu's page any more, so we've brought you to the top.
Naabu is a port scanning tool written in Go that enumerates valid ports for hosts using fast SYN/CONNECT/UDPUDPA network protocol that sends individual messages without guaranteeing delivery or order. Applications trade built-in reliability for less overhead and can add their own recovery. scans.
naabu -host example.com -top-ports 1000 -sV -sV-workers 10 -sV-timeout 10s -json -o results.json
naabu -host 192.168.1.0/24 -p 53,161,500,4500 -s SYN -uP -json
naabu -host 10.0.0.0/24 -sn -show-dead -silent
naabu -host 10.10.10.0/24 -proxy socks5://127.0.0.1:1080 -dns-order pl
naabu -host 192.168.1.0/24 -s syn -p 80,443,8080,8443
opts := &naabu.Options{
DisableStdout: true,
// other options...
}
naabu -host 10.0.0.0/24 -json | jq '{ip: .ip, mac: .mac, port: .port}'
naabu -host 10.0.0.0/24 -timeout 250ms
naabu -config /path/to/custom/config.yaml -host example.com
echo google.com:443 | ./naabu -silent
echo 142.250.183.174:443 | ./naabu -silent -p 80
naabu --proxy socks5://127.0.0.1:9050 -host example.com
naabu -ptr -host example.com
echo AS15133 | naabu
naabu -passive -host example.com
naabu -l targets.txt --resume resume.state
cat hosts.txt | naabu -stream
naabu --host example.com --custom-resolvers ./my-resolvers.txt
naabu -s CONNECT -host example.com
naabu -scan-all-ips example.com
naabu -host example.com | xargs -I{} nmap -Pn {}
naabu --host example.com --nmap
naabu --host example.com -rate 1000
naabu --host example.com -exclude-cdn
Summary
Naabu is an open-source, MIT-licensed port scanner written in Go, run from the command line, that performs SYN, CONNECT, and UDP scans to enumerate open ports on a host or list of hosts quickly. It accepts input as STDIN, a single host, IP, CIDRCIDRA notation for a block of IP addresses, such as 10.0.0.0/24. The number after the slash says how many leading address bits identify the network. block, or ASNASNAutonomous System Number — a globally unique identifier assigned by regional internet registries to a network operator, letting routing protocols distinguish which organization controls a block of IP addresses., outputs to JSON, text, or STDOUT, and can hand results to Nmap for service detection or pipe them into other tools like httpx, which suits red teamers and reconnaissance engineers mapping attack surfaceattack surfaceThe exposed systems, interfaces and access points an attacker could try to use. It includes internet-facing services as well as identities, software and other reachable resources. rather than analysts investigating a single incident. It sits in the network reconnaissance space, alongside other host-discovery and scanning utilities rather than one named competitor, and is built for chaining into larger recon pipelines. Started in 2020 and maintained by ProjectDiscovery, it has 85 contributors, roughly 190 commits and 20 releases in the past year, with a release only 108 days ago, indicating active upkeep.
Naabu is a port scanning tool written in Go that enumerates valid ports for hosts using fast SYN/CONNECT/UDP scans.
How naabu helps
Which hosts on this network segment are actually alive and reachable?
runs a discovery scan across a host, CIDR block, or ASN and lists the ones that respond, before any port-level work begins
Which ports are actually open on these hosts right now?
sends SYN, CONNECT, or UDP probes to each target and reports every port that replies, rather than relying on a static assumption of what should be listening
What service and version is running behind an open port I found?
hands the discovered ports to Nmap for service detection, returning the fingerprint instead of just a bare port number
Can I find exposed ports on a target without sending it any traffic myself?
queries Shodan's Internetdb for previously observed open ports on an IP, giving a passive answer when a live probe isn't an option
Am I scanning the same set of live hosts twice when the input is a list of domains?
resolves DNS first and deduplicates by IP automatically, so one host behind several names is only scanned once
How do I get open-port results into the next stage of my recon pipeline?
writes results as JSON, plain text, or STDOUT so they can be piped directly into tools like httpx for follow-on probing
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for naabu, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail naabu puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Commercials
pricing & packaging history · ProjectDiscovery vendor page23 readings of ProjectDiscovery's pricing page since Feb 2024, with 7 relaunches of its plan lineup and 4 changes to what its plans include — each one dated, compared with the reading before it, and explained for someone buying the tool.
Pricing and packaging history is included with Researcher and Business. See how every vendor we track sells, and how that has changed over time, using data we don't publish anywhere else.
See plans → Already subscribed? Sign in →Plans by offering
Each offering on the pricing page links to its own page of plans, read at its latest capture.
Plan relaunches
Plans, prices and descriptions are quoted from the vendor's own pricing page as we read it on each date. A plan missing from a later reading is shown as no longer listed on the page — a statement about the page, not the product. Readings that failed to show any plans are left out rather than read as a change.
Website history
projectdiscovery.io, every changeProjectDiscovery's home page and 3 more pages as they looked each month from August 2021 to October 2026: 18 renders, 4 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
See plans → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Releases
20 entries
No entries match these filters.
- October 20261
- April 20261
- March 20261
- January 20261
- November 20251
- July 20251
- January 20251
- October 20241
- March 20241
- November 20231
- August 20231
- March 20231
- February 20231
- October 20221
- July 20221
- May 20221
- March 20221
- October 20211
- December 20201
- September 20201
Project health
Issue, contributor and maintainer activity in projectdiscovery/naabu, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 23 +2 vs prior 12 months
- Maintainers 2 +2 joined · −3 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 77% of issues opened, last 12 months
- Median time to close 9.1 days first maintainer reply 2.3 days
- Open backlog 0 of 431 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 0
- Contributors / month 0
- Commits / month 0
- Stars 6,248
- bugs 45%
- features 18%
- other 37%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Articles
1 article · updated Nov 4, 2026Where naabu turns up in what others publish: how-tos, attack reports that name it, and incident write-ups. A row says why it is here and quotes where the article names it; the link goes to the publisher.
Breach post-mortems & incident response 1
-
Gaming the system: how a Chinese-speaking actor turned Brazilian government sites into an SEO weapon
naabu – takes IPs or hostnames, port ranges, and a scan mode, attempts TCP connections across all targets, and marks each port as open, closed, or filtered.
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.