About Netbench

What it is

Netbench collects the small tools that usually live in a dozen bookmarks into one place with one design, one keyboard model and one rule about where your data goes. Paste something into the inspector and it tells you what it is and hands it to the right tool. Every hostname, address and fingerprint in a result is a link to the tool that takes it next.

Where your input goes

Every tool page carries a badge. 39 of the 55 tools in the catalogue run entirely in your browser and never send what you type anywhere; the only network requests they make are for the page itself and, for MAC tools, static slices of the IEEE dataset. Remote tools query the target from our servers, say so on the page, and stamp their results with a time. Full TLS scans run on an isolated scan host and produce an unlisted report link that expires.

The MAC data

Hardware address lookups use a snapshot of the five IEEE Registration Authority registries (MA-L, MA-M, MA-S, IAB and CID): 58,700 assignments from 34,012 organizations in 118 countries, generated on 2026-09-15. The snapshot is refreshed nightly, validated before it replaces the previous one, and served as versioned static files so a lookup is one small fetch. Nested assignments resolve to the most specific block, so a 36-bit MA-S inside a 24-bit prefix returns the real registrant rather than the parent.

This site is not affiliated with or endorsed by the IEEE. The registries are published by the IEEE Registration Authority; this site reproduces the facts they contain.

Lineage

The MAC tools and the page shell descend from macvendorlookup.com, which remains the place for browsing vendors and blocks. This site is built for the questions that site does not answer: what a randomized address means, what is in an ARP table, what a subnet really contains, and whether a server is configured the way you think it is.

How it is built

A static Astro site with no runtime framework on most pages, a design system of tokens and a handful of component classes, and TypeScript packages shared between the browser and the tests. Remote tools will be served by a small API under one documented contract. Progress is tracked openly on the status page.