Look up what a port number is for, with the three port ranges explained and a note on what exposing each service usually means.
31 ports
Search by number, by service, or by what it does.
Port 0 is not usable. Asking to bind it tells the operating system to pick a free port for you.
0–1023 — well-known. Binding one needs root on Unix, which is why a container that drops privileges listens high and publishes low.
1024–49151 — registered. Where your own services belong.
49152–65535 — dynamic. Linux actually draws outbound source ports from about 32768, so listening above that invites an intermittent bind failure nobody can reproduce.
20TCPFTP dataThe data channel of classic FTP.
FTP is unencrypted. Use SFTP (22) instead.
21TCPFTP controlThe command channel of classic FTP.
Credentials cross the network in clear text.
22TCPSSH / SFTPSecure shell, and file transfer over it.
Safe to expose with key-only authentication; password authentication on port 22 is brute-forced constantly.
23TCPTelnetUnencrypted remote shell.
Everything, including the password, is in clear text. There is no safe configuration.
25TCPSMTPMail transfer between servers.
Blocked outbound by most cloud providers to limit spam.
53TCP/UDPDNSName resolution. UDP normally, TCP for large responses and zone transfers.
80TCPHTTPUnencrypted web traffic.
Fine as a redirect to 443; serving real content here sends everything in clear text.
110TCPPOP3Mail retrieval, older style.
123UDPNTPTime synchronisation.
An open NTP server can be used to amplify denial-of-service traffic.
143TCPIMAPMail retrieval, leaving messages on the server.
443TCPHTTPSWeb traffic over TLS. Also HTTP/3 over UDP on the same number.
465TCPSMTPSMail submission wrapped in TLS from the start.
587TCPSMTP submissionThe port mail clients should use, with STARTTLS.
993TCPIMAPSIMAP over TLS.
995TCPPOP3SPOP3 over TLS.
1433TCPMicrosoft SQL ServerThe default SQL Server port.
A database port should not be reachable from the internet.
1521TCPOracleOracle database listener.
A database port should not be reachable from the internet.
3000TCPNode development serverThe convention for Node and Next.js in development.
3306TCPMySQL / MariaDBThe default MySQL port.
A database port should not be reachable from the internet.
3389TCPRDPWindows remote desktop.
Heavily targeted. Put it behind a VPN rather than exposing it.
5173TCPVite development serverVite's default.
5432TCPPostgreSQLThe default Postgres port.
A database port should not be reachable from the internet.
5672TCPAMQP / RabbitMQMessage broker protocol.
6379TCPRedisThe default Redis port.
Redis historically had no authentication by default, and exposed instances are routinely compromised.
8000TCPAlternative HTTPCommon for Django and Python development servers.
8080TCPAlternative HTTPThe usual choice for an application behind a proxy, and for an unprivileged container.
8443TCPAlternative HTTPSHTTPS on an unprivileged port.
9000TCPPHP-FPM / variousPHP FastCGI, and a popular default for several other tools.
9090TCPPrometheusThe Prometheus server's default.
9200TCPElasticsearchThe Elasticsearch HTTP API.
Exposed clusters with no authentication have leaked large amounts of data.
27017TCPMongoDBThe default MongoDB port.
A database port should not be reachable from the internet.
Port Number Reference runs entirely on your device — nothing is uploaded, and no host or port is contacted.
You’re on the Free plan. Compare plans
The three port ranges exist for reasons people run into. Ports below 1024 are well-known, and on Unix binding one requires root or an explicit capability — which is why a Node process that works on 3000 fails on 80, and why a container that drops privileges listens high and is published low.
The ephemeral range is why a service sometimes "randomly" fails to bind. Outbound connections take a source port from roughly 32768–60999 on Linux, so a service configured to listen on a port in that range will one day find it already in use by an outgoing connection. It is intermittent, environment-dependent, and avoided entirely by listening below 32768.
Each entry carries a note on what exposing that service to the internet usually means. Port 23 has no safe configuration. Port 22 is fine with key-only authentication and is brute-forced constantly with passwords. A database port reachable from the internet is almost always a mistake rather than a design.
The notes are about the service, not about your host. Nothing here contacts anything, so this cannot tell you whether a port is open, filtered or listening — those are questions only a real connection can answer.
Because ports below 1024 need root on Unix, and your process is not running as root — correctly. Listen on a high port and map 80 to it, which is what a container or a reverse proxy does.
The range the kernel draws source ports from for outbound connections — about 32768–60999 on Linux. A service listening in that range can intermittently fail to bind because an outgoing connection took the port first.
Above 1024, so you do not need root, and below 32768, so the ephemeral range cannot collide with it. That leaves plenty of room and avoids both problems.
No. Nothing is contacted. Whether a port is open, filtered or listening can only be answered by actually connecting to it.
Only by convention. The IANA registry is a coordination mechanism, not an enforcement one — anything can listen on any port it is allowed to bind.