nbtscan
1.5 open-sourceThe section your link pointed to isn't on nbtscan's page any more, so we've brought you to the top.
NBTscan is a program for scanning IP networks for NetBIOS name information, sending status queries and listing IP address, computer name, user, and MAC addressMAC addressA hardware-address identifier used on a local network, such as Ethernet or Wi-Fi. It identifies a network interface for delivery on that link, rather than routing across the internet..
echo '192.168.1.1-255' | nbtscan -t 500 nbtscan -t 120 192.168.1.0/24 nbtscan -s <target> nbtscan -d <target>
Summary
nbtscan is an open-source command-line tool that scans IP networks for NetBIOS name information, sending status queries to each address in a range and listing, for hosts that respond, the IP address, NetBIOS computer name, logged-in user name, and MAC address. It runs from the shell against a supplied IP range or list, which suits network administrators and reconnaissance-focused pentesters doing early host and Windows/SMBSMBA network file-sharing protocol developed by Microsoft that lets systems share files, printers, and named pipes over a network; cyber tools target or speak it because it is ubiquitous in Windows environments. discovery on a network rather than deep service enumeration. It sits in the same space as other NetBIOS and network-scanning utilities used for that footprinting step, rather than offering anything broader. The project is a revival of Alla Bezroutchko's original tool, now maintained by the resurrecting-open-source-projects group with only 3 contributors, and while packaged for Debian, it has seen no commits in the past year, so treat it as stable but essentially dormant.
NBTscan is a program for scanning IP networks for NetBIOS name information, sending status queries and listing IP address, computer name, user, and MAC address.
How nbtscan helps
Which hosts on this subnet are actually Windows machines I can investigate further?
sends a NetBIOS status query to every address in the given range and lists the IP, computer name, logged-in user, and MAC address for each host that answers, leaving silent addresses as either down or non-NetBIOS
Who is logged into a given machine on my network right now?
reads the logged-in user name back from the NetBIOS status reply for each responding host, giving a point-in-time answer rather than a login history
Which physical device sits behind a given IP address?
pulls the MAC address out of the NetBIOS status reply, letting the IP be tied to a specific network interface
Can I tell which hosts belong to which machine when several IPs map to one computer name?
lists computer name alongside IP for every responder, so repeated names across different addresses stand out as the same host with multiple interfaces or DHCP leases
Is this list of addresses actually reachable as hosts before I run anything heavier against them?
walks a supplied IP range or list and reports back only the addresses that returned a NetBIOS status response, giving a quick first-pass host census ahead of deeper scanning
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 nbtscan, 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 nbtscan 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…
Releases
3 entries
No entries match these filters.
- May 20021
- February 20021
- March 20001
Project health
Issue, contributor and maintainer activity in resurrecting-open-source-projects/nbtscan, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 0 ±0 vs prior 12 months
- Maintainers 0 +0 joined · −0 left, last 12 months
- Bus factor 0 committers behind half the commits
- Community-filed not measured of issues opened, last 12 months
- Median time to close not measured issues closed, last 12 months
- Open backlog 0 of 2 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 0
- Contributors / month 0
- Commits / month 0
- Stars 52
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
2 articles · updated Nov 4, 2026Where nbtscan 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.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.