Searchable list of common network ports and services
Showing 57 of 57 ports
Port Reference is a quick-lookup table of 55+ common TCP and UDP port numbers mapped to the services and protocols that use them, from well-known ports like 22 (SSH), 80 (HTTP), and 443 (HTTPS) to database and mail ports such as 3306 (MySQL), 5432 (PostgreSQL), 25 (SMTP), and 993 (IMAPS). Each entry shows the port number, transport protocol, service name, and a short description of what runs there.
Network administrators, developers, students studying for certifications, and security analysts use it to decode firewall rules, read netstat and nmap output, plan port forwarding, and confirm which service a given number belongs to without memorizing the IANA registry.
TCP and UDP identify individual applications on a host using a 16-bit port number, giving a range of 0 to 65535. IANA divides this space into three bands: well-known ports (0 to 1023) reserved for core services such as HTTP on 80 and DNS on 53, registered ports (1024 to 49151) assigned to specific vendor or application services like MySQL on 3306, and dynamic or ephemeral ports (49152 to 65535) that clients borrow temporarily for outbound connections. A socket is uniquely defined by the pair of IP address and port, which is why one server can run many services at once.
This tool ships as a static, curated dataset of the most frequently encountered ports and their canonical services, so lookups resolve entirely in your browser with no network request. Remember that a port assignment is a convention, not a guarantee: administrators can run any service on any port (for example SSH on 2222), so the reference tells you the standard meaning of a number rather than what is definitively running on a specific machine.
TCP is connection-oriented and guarantees ordered, reliable delivery, used by services like HTTP, SSH, and SMTP. UDP is connectionless and lower-latency, used by DNS queries, DHCP, and SNMP. Some services such as DNS on port 53 use both, which is noted in the protocol column.
Certain services are registered for both TCP and UDP at the same port number, such as DNS (53) and NTP (123). The port number is shared across the two protocols because they are separate transport layers, so a host can technically listen on TCP 53 and UDP 53 independently.
No. This is a reference of standard assignments only. To find out whether a port is actually open and reachable on a specific host, use a live scanning tool such as our Port Checker, or run netstat or nmap locally.
Well-known ports are 0 to 1023 and cover core internet services, usually requiring elevated privileges to bind on. Registered ports run 1024 to 49151, and dynamic or ephemeral ports run 49152 to 65535, used automatically by clients for the source side of outbound connections.
Yes. Port assignments are conventions, not enforced rules. It is common to move SSH off 22 or run a second web server on 8080 or 8443. This tool shows the standard meaning of a number, not what a particular server has chosen to run.
Yes, it is completely free with no sign-up. The port list is a static dataset bundled with the page, so your searches run entirely in your browser and nothing you type is sent to a server or stored.
There is no universal blocklist, but a common practice is to deny everything inbound by default and allow only the ports your services need, such as 443 for HTTPS. Legacy plaintext ports like 23 (Telnet) and 21 (FTP) are frequently blocked in favor of encrypted alternatives like SSH (22) and SFTP.