| Port | Protocol | Service | Description | Range |
|---|
What Runs on Port 80, 443, 22, 3306, and More • 100% Local
| Port | Protocol | Service | Description | Range |
|---|
A port number identifies a specific service or connection on a device — the same computer can run a web server on port 80, an SSH server on port 22, and a database on port 3306 all at once, and the port number is how incoming traffic gets routed to the right one. This table covers a curated set of the port numbers most commonly seen in real-world work — troubleshooting a firewall rule, reading a netstat or server log, configuring a reverse proxy, or just double-checking what a number means — rather than the full official IANA registry, which lists tens of thousands of entries, the overwhelming majority of which are rarely relevant day to day.
Port numbers fall into three official ranges, and each entry here shows which one it's in: Well-Known (0–1023), reserved for core, foundational services and generally requiring administrator/root privileges to bind on Unix-like systems; Registered (1024–49151), used by a huge range of specific applications and services that have registered (or informally claimed) a port with IANA; and Dynamic/Private (49152–65535), reserved for temporary, ephemeral connections rather than fixed services.
A quick honest caveat: a port's "well-known" association is a convention, not a rule enforced by the network itself — any service can technically be configured to listen on any available port, so what's actually running on a given port in a specific system can only be confirmed by checking that system directly, not assumed from a lookup table alone.