ToolSphere

Port Number Lookup

Computer science

Search well-known and registered TCP and UDP port numbers and networking services. Quick lookup for firewall configuration, security audits, and sysadmins.

Port number lookup

Look up well-known and commonly used TCP/UDP port numbers.

PortProtocolService
20TCPFTP (Data)
21TCPFTP (Control)
22TCPSSH
23TCPTelnet
25TCPSMTP
53TCP/UDPDNS
67UDPDHCP (Server)
68UDPDHCP (Client)
80TCPHTTP
110TCPPOP3
119TCPNNTP
123UDPNTP
143TCPIMAP
161UDPSNMP
194TCPIRC
389TCPLDAP
443TCPHTTPS
445TCPSMB
465TCPSMTPS
514UDPSyslog
587TCPSMTP (Submission)
631TCPIPP (Printing)
993TCPIMAPS
995TCPPOP3S
1433TCPMicrosoft SQL Server
1521TCPOracle DB
2049TCPNFS
27017TCPMongoDB
3000TCPCommon dev server (Node/React)
3306TCPMySQL / MariaDB
3389TCPRDP
5432TCPPostgreSQL
5900TCPVNC
6379TCPRedis
6443TCPKubernetes API Server
8080TCPHTTP alternate / proxy
8443TCPHTTPS Alternate
9200TCPElasticsearch

On this browser only

Give feedback

Did this tool help?

Tell us what worked, what didn’t, or what you’d like next.

Opens Google Forms in a new tab with this tool’s name filled in. No sign-in or email required. Feedback is optional.

About Port Number Lookup

Why Ports Are Organized Into Three Ranges

The full 16-bit port range (0-65535) splits into three IANA-managed bands, each serving a different purpose (see Well-Known Port Numbers for the full breakdown): well-known ports (0-1023, reserved for standardized system services like HTTP on 80 or SSH on 22), registered ports (1024-49151, assignable to specific applications with less strict enforcement), and dynamic/private ports (49152-65535, used for temporary, per-connection endpoints rather than permanently assigned services).

Looking up an unfamiliar port number quickly answers a genuinely common troubleshooting question — "what's normally supposed to be running on this port" — whether configuring a firewall rule, investigating unexpected network traffic, or just trying to remember which port a specific database or dev server tool conventionally uses (a detail that's easy to forget across the dozens of common development tools each defaulting to their own port).

Most operating systems restrict binding to well-known ports (0-1023) to privileged processes specifically, a deliberate security measure — which is exactly why an unprivileged server process typically can't accidentally (or maliciously) impersonate a standard service like HTTP or SSH just by trying to listen on that port number.

Guides and tutorials

Frequently asked questions

Why are ports below 1024 restricted to privileged processes on most systems?

This is a deliberate security measure — well-known ports (0-1023) are reserved for standardized system services that users and other systems implicitly trust, and restricting who can bind to them prevents unprivileged software from impersonating a trusted service.

What's the difference between a registered port and a well-known port?

Well-known ports (0-1023) are reserved for standardized core services with strict conventions; registered ports (1024-49151) can be assigned to specific applications with much less strict enforcement, which is why many common dev tools and applications default to a registered-range port.

Why does my browser's outgoing connection use a seemingly random high port number?

Client-side connections use the dynamic/private range (49152-65535) as temporary, per-connection local endpoints — the server you're connecting to listens on its own well-known or registered port, but your side of that specific connection gets an arbitrary dynamic-range port.

Have a suggestion for Port Number Lookup?Share your feedback ↗