Common Ports Reference
Well-known TCP and UDP port numbers, searchable. Filter by category and see what each port is for.
| Port | Protocol | Service |
|---|---|---|
80 | TCP | HTTP Web |
443 | TCP | HTTPS Web |
8080 | TCP | HTTP alternate Web |
8443 | TCP | HTTPS alternate Web |
3000 | TCP | Dev server (Node / React) Web |
5173 | TCP | Vite dev server Web |
8000 | TCP | Dev server (HTTP alt) Web |
8888 | TCP | HTTP alternate (Jupyter) Web |
4200 | TCP | Dev server (Angular) Web |
25 | TCP | SMTP Mail |
587 | TCP | SMTP submission Mail |
465 | TCP | SMTPS (SMTP over TLS) Mail |
110 | TCP | POP3 Mail |
995 | TCP | POP3S (POP3 over TLS) Mail |
143 | TCP | IMAP Mail |
993 | TCP | IMAPS (IMAP over TLS) Mail |
22 | TCP | SSH Remote |
23 | TCP | Telnet Remote |
3389 | TCP/UDP | RDP (Remote Desktop) Remote |
5900 | TCP | VNC Remote |
5985 | TCP | WinRM (HTTP) Remote |
5986 | TCP | WinRM (HTTPS) Remote |
20 | TCP | FTP data File |
21 | TCP | FTP control File |
989 | TCP | FTPS data File |
990 | TCP | FTPS control File |
445 | TCP | SMB / CIFS File |
2049 | TCP/UDP | NFS File |
873 | TCP | rsync File |
69 | UDP | TFTP File |
548 | TCP | AFP (Apple Filing) File |
3306 | TCP | MySQL / MariaDB Database |
5432 | TCP | PostgreSQL Database |
6379 | TCP | Redis Database |
27017 | TCP | MongoDB Database |
1433 | TCP | Microsoft SQL Server Database |
1521 | TCP | Oracle Database Database |
9200 | TCP | Elasticsearch Database |
5984 | TCP | CouchDB Database |
11211 | TCP/UDP | Memcached Database |
9042 | TCP | Cassandra (CQL) Database |
8086 | TCP | InfluxDB Database |
53 | TCP/UDP | DNS Infra |
67 | UDP | DHCP server Infra |
68 | UDP | DHCP client Infra |
123 | UDP | NTP Infra |
161 | UDP | SNMP Infra |
389 | TCP | LDAP Infra |
636 | TCP | LDAPS (LDAP over TLS) Infra |
514 | UDP | syslog Infra |
179 | TCP | BGP Infra |
88 | TCP/UDP | Kerberos Infra |
500 | UDP | IKE (IPsec) Infra |
No ports match your search.
Runs entirely in your browser. Nothing you type is sent anywhere; open DevTools and watch the Network tab to verify zero requests.
What this tool does
This is a searchable reference for the port numbers that common network services listen
on by default. Each row lists the port, whether the service typically runs over
TCP, UDP, or both, the service name, and a category badge (web,
mail, remote access, file transfer, databases, or infrastructure). Type in the filter box
to narrow the table by port number, service name, or protocol, or tap a category button to
show just one family. The whole dataset is baked into the page, so it works offline and
sends nothing anywhere.
How to use it
Start typing in the Filter box. Entering 443 jumps straight
to HTTPS; entering smtp surfaces the mail ports; entering udp
shows every service that runs over UDP. The category buttons (All, Web,
Mail, Remote, File transfer, Databases, Infrastructure) combine with the text filter, so
you can, for example, pick Databases and type sql to compare
the SQL server ports. Clear the box to see every port again. Nothing is submitted and there
is no result limit.
Common use cases
- Checking which port a service listens on before opening a firewall rule or a security group.
- Reading netstat, ss, or nmap output and mapping a number back to the service behind it.
- Configuring a reverse proxy, load balancer, or container port mapping.
- Debugging a connection that hangs, by confirming the client and server agree on the port and protocol.
- Studying for a networking exam where the well-known port numbers come up.
Notes and common pitfalls
- Ports are conventions, not guarantees. A number here is only the default; any service can be configured to listen elsewhere, so always confirm the real port in your own configuration.
- TCP and UDP ports are separate spaces. Port 53 over TCP and port 53 over UDP are different endpoints, which is why DNS can use both at once without conflict.
- Secure and plaintext variants differ. Many protocols have a plaintext port and a TLS port, such as 80 versus 443, 143 versus 993, or 21 versus 990. Picking the wrong one usually shows up as a handshake or timeout error.
- Do not expose sensitive ports publicly. Database, cache, and remote access ports should sit behind a private network or firewall rather than being reachable from the open internet.
Frequently asked questions
- What is a well-known port?
- A well-known port is a number in the range 0 to 1023 that IANA reserves for a specific, widely used service, such as 80 for HTTP or 22 for SSH. Because these assignments are standardized, a client can connect to a service on its default port without any prior negotiation. On many systems, binding to a well-known port requires administrator or root privileges.
- What is the difference between TCP and UDP?
- TCP and UDP are the two main transport protocols that sit on top of IP. TCP is connection oriented and reliable: it sets up a connection, orders the data, and retransmits anything lost, which suits web pages, email, and file transfer. UDP is connectionless and has no built-in delivery guarantee, which makes it lighter and faster for things like DNS lookups, video streaming, and voice calls. Some services, such as DNS, are assigned both.
- What port does HTTPS use?
- HTTPS uses TCP port 443 by default, while plain HTTP uses TCP port 80. When you type a URL without a port, the browser assumes 443 for https and 80 for http, so you rarely need to write the number yourself. A server can be configured to serve HTTPS on a different port, in which case the URL must include it, for example https://example.com:8443.
- Which ports do databases use?
- Common defaults are 3306 for MySQL and MariaDB, 5432 for PostgreSQL, 6379 for Redis, 27017 for MongoDB, 1433 for Microsoft SQL Server, and 1521 for Oracle. These are conventions rather than hard rules, and production deployments often change them. Database ports should almost never be exposed directly to the public internet; keep them behind a private network or a firewall.
- What are ports 0-1023 versus 1024-49151?
- Ports split into three ranges. 0 to 1023 are the well-known or system ports, reserved for core services and usually requiring elevated privileges to bind. 1024 to 49151 are the registered ports, which IANA assigns to specific applications on request. 49152 to 65535 are the dynamic or ephemeral ports, which the operating system hands out temporarily for the client side of a connection.
- Can I change which port a service uses?
- Yes. Port numbers are conventions, not fixed hardware addresses, so almost any service can be configured to listen on a different port. Running SSH on a non-standard port or a web server on 8080 is common. The trade-off is that clients must then be told the new port, since they will otherwise assume the default, so document any change clearly.
- Does this tool send the ports I search to a server?
- No. The full list of ports is embedded in the page, and all filtering happens in your browser with JavaScript. You can confirm this by opening DevTools and watching the Network tab: typing in the search box makes zero requests.
Cite this tool
For academic, journalistic, or technical references. Pick a format:
Citations use 2026 as the publication year. Access date is left as a fillable placeholder where the citation style expects one.