Common network ports

A port is a numbered endpoint that lets a single device run many network services at once. When data arrives, your computer uses the port number to decide which program should receive it — the web browser, the mail client, a database, and so on. Combined with an IP address, a port identifies one specific service on one specific machine: the IP gets the packet to the right device, and the port gets it to the right application.

Port numbers are 16-bit values, so they range from 0 to 65535. They are used by the two main transport protocols: TCP, which sets up a reliable, ordered connection, and UDP, which sends lightweight datagrams without a persistent connection. Many services listen on the same number for both protocols, but a TCP port and a UDP port with the same number are separate.

Port ranges

The full range is split into three groups by the Internet Assigned Numbers Authority (IANA):

RangeNameTypical use
01023Well-known portsCore services such as HTTP, HTTPS, SSH and DNS; usually require elevated privileges to bind.
102449151Registered portsApplications and vendors register these for specific software (databases, proxies, tools).
4915265535Dynamic / ephemeral portsAssigned temporarily by the operating system for the client side of outgoing connections.

Common ports

The table below lists widely used ports and the services that run on them. Numbers separated by a slash indicate a service that uses more than one port or protocol.

PortProtocolServiceDescription
20/21TCPFTPFile Transfer Protocol; 21 handles commands and 20 carries data.
22TCPSSHSecure Shell for encrypted remote login and file transfer (SCP/SFTP).
23TCPTelnetLegacy unencrypted remote login; avoid on modern networks.
25TCPSMTPSimple Mail Transfer Protocol for server-to-server mail relay.
53TCP/UDPDNSDomain Name System name resolution; see what a DNS server is.
67/68UDPDHCPDynamic Host Configuration Protocol; server on 67, client on 68.
80TCPHTTPUnencrypted web traffic.
110TCPPOP3Post Office Protocol for downloading email from a mailbox.
123UDPNTPNetwork Time Protocol for clock synchronization.
143TCPIMAPInternet Message Access Protocol for reading mail stored on a server.
161UDPSNMPSimple Network Management Protocol for monitoring devices.
194TCPIRCInternet Relay Chat text messaging.
443TCPHTTPSEncrypted web traffic over TLS.
445TCPSMBServer Message Block for Windows file and printer sharing.
465/587TCPSMTP (submission)Client mail submission; 587 with STARTTLS, 465 with implicit TLS.
993TCPIMAPSIMAP over TLS for secure mail access.
995TCPPOP3SPOP3 over TLS for secure mail download.
3306TCPMySQLMySQL and MariaDB database connections.
3389TCPRDPRemote Desktop Protocol for graphical remote access to Windows.
5432TCPPostgreSQLPostgreSQL database connections.
5900TCPVNCVirtual Network Computing remote desktop.
6379TCPRedisRedis in-memory data store.
8080TCPHTTP-altAlternate HTTP port, often used by proxies and development servers.
27017TCPMongoDBMongoDB database connections.

Ports and your IP

Checking whether a port is open on a host is a different task from finding out what your IP address is. Port scanning asks "can I reach this service?", while this site answers "what public IP am I presenting to the internet?" If you want the latter, you can check your IP address on the home page or fetch it programmatically through the API.

Ports and addresses go hand in hand once you start planning a network. The subnet calculator helps you work out address ranges and host counts, and the guide to private IP ranges explains which addresses stay inside your local network — the same networks where you will typically expose internal services on the ports listed above.

A note on security

A port can be open (a service is listening and reachable), closed (nothing is listening), or filtered (a firewall is silently dropping the traffic). Firewalls and network address translation mean that most services running behind a home or office router are not reachable from the public internet unless a port is deliberately forwarded.

That default is a good thing. Sensitive services such as remote desktop (3389) and databases (3306, 5432, 6379, 27017) should almost never be exposed directly to the public internet — they are frequent targets for automated attacks. Keep them behind a firewall or VPN, restrict access to known addresses, and always require strong authentication and encryption.

→ Check your IP address  ·  More guides