Skip to main content
ponderloop

Network Ports Reference

Port 443 is HTTPS, port 22 is SSH, port 80 is HTTP and port 53 is DNS. This table lists 112 well-known and commonly used TCP and UDP ports with the service, a secure variant where one exists, and whether the number is registered with IANA or only commonly used. Search by number (443), range (8000-9000) or name (mysql). It is a static reference list: it never connects to, scans or probes any host.

Updated Runs in your browser: nothing you enter is uploadedHow this tool works

Try 443, 8000-9000, mysql or mail

Showing all 112 ports.

Ports

A fixed list from the IANA registry and common product defaults. It does not check whether any port is open on any machine.

Well-known and commonly used TCP and UDP ports with protocol, service, description, secure variant or notes, category and registration status
PortProtocolServiceWhat it is used forSecure variant / notesCategoryStatus
20TCPFTP dataFile Transfer Protocol data channel, used in active mode.Plain text. Use FTPS or SFTP (SSH, port 22) instead.File transferRegistered with IANA
21TCPFTPFile Transfer Protocol control channel: login and commands.Plain text. Explicit FTPS upgrades this port with TLS; implicit FTPS uses 990.File transferRegistered with IANA
22TCPSSHSecure Shell: encrypted remote login, command execution and tunnelling. Also carries SFTP and SCP.Already encrypted.Remote accessRegistered with IANA
23TCPTelnetUnencrypted remote terminal login.Sends passwords in plain text. Use SSH (22) instead.Remote accessRegistered with IANA
25TCPSMTPSimple Mail Transfer Protocol: relaying mail between mail servers.Can be upgraded with STARTTLS. Mail clients should submit on 587 or 465.MailRegistered with IANA
43TCPWHOISLooks up domain and IP address registration records.Plain text. RDAP, its successor, runs over HTTPS (443).Network managementRegistered with IANA
53TCP/UDPDNSDomain Name System: turns names into IP addresses. UDP for most queries, TCP for large answers and zone transfers.Plain by default. DNS over TLS uses 853; DNS over HTTPS uses 443.Network managementRegistered with IANA
67UDPDHCP serverDynamic Host Configuration Protocol: the server listens here to hand out IPv4 addresses.No encryption. The client side uses 68.Network managementRegistered with IANA
68UDPDHCP clientThe port a DHCP client listens on for the server’s reply.No encryption. The server side uses 67.Network managementRegistered with IANA
69UDPTFTPTrivial File Transfer Protocol: simple transfers, often for network boot and device firmware.No login and no encryption. Keep it on trusted networks.File transferRegistered with IANA
80TCPHTTPHypertext Transfer Protocol: unencrypted web traffic.Plain text. HTTPS on 443 is the encrypted version.WebRegistered with IANA
88TCP/UDPKerberosNetwork authentication used by Active Directory and other single sign-on setups.Password changes use 464.DirectoryRegistered with IANA
110TCPPOP3Post Office Protocol version 3: downloads mail from a server.Plain text by default. POP3S uses 995, or upgrade with STARTTLS.MailRegistered with IANA
111TCP/UDPONC RPC (rpcbind)Sun RPC portmapper: tells clients which port an RPC service such as NFS listens on.No encryption. Normally kept off the public internet.Network managementRegistered with IANA
119TCPNNTPNetwork News Transfer Protocol: reading and posting Usenet articles.Plain text. NNTPS uses 563.MessagingRegistered with IANA
123UDPNTPNetwork Time Protocol: keeps clocks in sync.Plain UDP. Network Time Security (NTS) adds authentication.Network managementRegistered with IANA
135TCP/UDPMicrosoft RPC endpoint mapperDCE/RPC endpoint mapper: tells Windows clients which port an RPC service listens on.Normally kept off the public internet.Network managementRegistered with IANA
137UDPNetBIOS name serviceNetBIOS over TCP/IP name resolution on older Windows networks.Legacy. SMB on 445 does not need it.Network managementRegistered with IANA
138UDPNetBIOS datagram serviceNetBIOS datagram distribution (browsing, messaging) on older Windows networks.Legacy. Not needed for SMB on 445.Network managementRegistered with IANA
139TCPNetBIOS session serviceSMB file and printer sharing carried over NetBIOS on older Windows networks.Legacy. Current SMB uses 445 directly.File transferRegistered with IANA
143TCPIMAPInternet Message Access Protocol: reads and manages mail on the server.Plain text by default. IMAPS uses 993, or upgrade with STARTTLS.MailRegistered with IANA
161UDPSNMPSimple Network Management Protocol: queries to routers, switches, printers and servers.SNMPv1 and v2c send community strings in plain text. SNMPv3 adds authentication and encryption.Network managementRegistered with IANA
162UDPSNMP trapWhere a manager receives SNMP traps and notifications sent by devices.SNMPv3 can authenticate and encrypt notifications.Network managementRegistered with IANA
179TCPBGPBorder Gateway Protocol: exchanging routes between networks.Sessions run between explicitly configured neighbours.Network managementRegistered with IANA
389TCP/UDPLDAPLightweight Directory Access Protocol: directory lookups and sign-in, for example against Active Directory.Plain text unless upgraded with StartTLS. LDAPS uses 636.DirectoryRegistered with IANA
443TCP/UDPHTTPSHTTP over TLS: encrypted web traffic. TCP for HTTP/1.1 and HTTP/2, UDP (QUIC) for HTTP/3.Already encrypted.WebRegistered with IANA
445TCPSMBServer Message Block: Windows file and printer sharing, directly over TCP.SMB 3 can encrypt traffic. Normally kept off the public internet.File transferRegistered with IANA
464TCP/UDPKerberos password changeKerberos change-password and set-password service.Related to Kerberos authentication on 88.DirectoryRegistered with IANA
465TCPSMTPS (submission over TLS)Mail submission with TLS from the first byte (implicit TLS), registered for this use by RFC 8314.Encrypted. RFC 8314 prefers it to STARTTLS on 587.MailRegistered with IANA
500UDPIKE (ISAKMP)Internet Key Exchange: sets up IPsec VPN tunnels.NAT traversal moves the traffic to 4500.Remote accessRegistered with IANA
514UDPSyslogClassic log forwarding. Port 514/TCP is assigned to the remote shell service (rsh), not to syslog.No encryption. Syslog over TLS uses 6514.Network managementRegistered with IANA
520UDPRIPRouting Information Protocol, versions 1 and 2.Legacy distance-vector routing protocol.Network managementRegistered with IANA
546UDPDHCPv6 clientThe port a DHCPv6 client listens on.IPv6 counterpart of 68. The server side uses 547.Network managementRegistered with IANA
547UDPDHCPv6 serverThe port DHCPv6 servers and relays listen on.IPv6 counterpart of 67. The client side uses 546.Network managementRegistered with IANA
563TCPNNTPSNetwork News Transfer Protocol over TLS.Encrypted version of 119.MessagingRegistered with IANA
587TCPSMTP submissionMail clients hand outgoing mail to their provider’s server here (RFC 6409), normally after signing in.Upgraded with STARTTLS. Implicit TLS alternative: 465.MailRegistered with IANA
631TCPIPPInternet Printing Protocol, used by CUPS and network printers.Encrypted variant (IPPS) uses TLS on the same port.OtherRegistered with IANA
636TCPLDAPSLDAP directory queries and sign-in over TLS from the first byte.Encrypted version of 389.DirectoryRegistered with IANA
853TCP/UDPDNS over TLS / QUICEncrypted DNS: TCP for DNS over TLS (RFC 7858), UDP for DNS over QUIC (RFC 9250).Already encrypted.Network managementRegistered with IANA
873TCPrsyncrsync file synchronisation daemon.The daemon protocol is not encrypted. Running rsync over SSH (22) is the usual alternative.File transferRegistered with IANA
989TCPFTPS data (implicit TLS)FTP data channel for implicit FTPS.Explicit FTPS starts on port 21 instead.File transferRegistered with IANA
990TCPFTPS control (implicit TLS)FTP control channel for implicit FTPS.Encrypted version of 21.File transferRegistered with IANA
993TCPIMAPSReading and managing mail on the server over TLS from the first byte.Encrypted version of 143.MailRegistered with IANA
995TCPPOP3SDownloading mail from the server over TLS from the first byte.Encrypted version of 110.MailRegistered with IANA
1080TCPSOCKS proxySOCKS proxy for relaying TCP connections.SOCKS5 itself does not encrypt the traffic it relays.OtherRegistered with IANA
1194TCP/UDPOpenVPNOpenVPN tunnels, usually over UDP.Encrypted with TLS.Remote accessRegistered with IANA
1433TCPMicrosoft SQL ServerDefault instance of Microsoft SQL Server.TLS encryption is a server and client setting on the same port.DatabaseRegistered with IANA
1434UDPSQL Server BrowserTells clients which port a named SQL Server instance listens on.Only needed for named instances.DatabaseRegistered with IANA
1521TCPOracle Database listenerDefault listener port of Oracle Database.TLS is configured separately in the Oracle listener.DatabaseCommonly used
1701UDPL2TPLayer 2 Tunneling Protocol, used for VPNs.No encryption of its own. Usually paired with IPsec (L2TP/IPsec).Remote accessRegistered with IANA
1723TCPPPTPPoint-to-Point Tunneling Protocol VPN control channel.Obsolete and considered insecure. Avoid it for new setups.Remote accessRegistered with IANA
1812UDPRADIUS authenticationRADIUS sign-in requests, used for Wi-Fi, VPN and network device access.Accounting uses 1813.Network managementRegistered with IANA
1813UDPRADIUS accountingRADIUS accounting records (session start, stop and usage).Authentication uses 1812.Network managementRegistered with IANA
1883TCPMQTTLightweight publish and subscribe messaging, common for IoT devices.Plain text. MQTT over TLS uses 8883.MessagingRegistered with IANA
1900UDPSSDP (UPnP discovery)Simple Service Discovery Protocol: finds UPnP devices on the local network.Local network discovery; no encryption.Network managementRegistered with IANA
2049TCP/UDPNFSNetwork File System: mounting remote directories as if they were local.NFSv4 needs only TCP 2049. Older versions also use 111 and helper services.File transferRegistered with IANA
2181TCPApache ZooKeeperDefault client port of Apache ZooKeeper, a coordination service used by several distributed systems.Keep it on private networks.OtherCommonly used
2375TCPDocker daemon (unencrypted)Docker Engine remote API without TLS.No authentication: never expose it. The TLS version uses 2376.OtherCommonly used
2376TCPDocker daemon (TLS)Docker Engine remote API protected with TLS client certificates.Encrypted version of 2375.OtherCommonly used
2379TCPetcd clientClient API of etcd, the key-value store used by Kubernetes.etcd supports TLS on the same port.DatabaseCommonly used
2380TCPetcd peerCommunication between etcd cluster members.etcd supports TLS on the same port.DatabaseCommonly used
3000TCPJavaScript dev serverDefault for many local dev servers, including Create React App and Next.js.Development use. No encryption by default.WebCommonly used
3128TCPSquid proxyDefault HTTP proxy port of the Squid caching proxy.Proxy traffic is plain text unless the proxy is configured for TLS.WebCommonly used
3260TCPiSCSIBlock storage over IP networks (iSCSI targets).Authentication (CHAP) is optional; use isolated storage networks.OtherRegistered with IANA
3268TCPLDAP global catalogActive Directory global catalog queries across all domains in a forest.Encrypted version uses 3269.DirectoryCommonly used
3269TCPLDAP global catalog over TLSActive Directory global catalog over TLS.Encrypted version of 3268.DirectoryCommonly used
3306TCPMySQLMySQL and MariaDB client connections.TLS is a server setting on the same port. The X Protocol uses 33060.DatabaseRegistered with IANA
3389TCP/UDPRDPRemote Desktop Protocol for Windows desktops. TCP, with optional UDP transport.Keep it off the public internet: use a VPN or Remote Desktop Gateway.Remote accessRegistered with IANA
3690TCPSubversion (svnserve)Subversion server protocol (svn://).Not encrypted by itself. Use svn+ssh or HTTPS.OtherRegistered with IANA
4200TCPAngular dev serverDefault of the Angular CLI development server (ng serve).Development use. No encryption by default.WebCommonly used
4321TCPAstro dev serverDefault of the Astro development server.Development use. No encryption by default.WebCommonly used
4500UDPIPsec NAT traversalIPsec traffic and IKE when a NAT device sits between the peers.Companion of 500.Remote accessRegistered with IANA
5060TCP/UDPSIPSession Initiation Protocol: sets up voice and video calls.Plain text. SIP over TLS uses 5061.MessagingRegistered with IANA
5061TCPSIP over TLSSIP signalling over TLS.Encrypted version of 5060.MessagingRegistered with IANA
5173TCPVite dev serverDefault of the Vite development server.Development use. No encryption by default.WebCommonly used
5222TCPXMPP clientChat clients connecting to an XMPP (Jabber) server.Upgraded with STARTTLS.MessagingRegistered with IANA
5269TCPXMPP serverXMPP servers talking to each other.Upgraded with STARTTLS.MessagingRegistered with IANA
5353UDPmDNSMulticast DNS: resolves .local names on the local network (Bonjour, Avahi).Local network only.Network managementRegistered with IANA
5432TCPPostgreSQLPostgreSQL client connections.TLS is a server setting on the same port.DatabaseRegistered with IANA
5601TCPKibanaDefault web interface port of Kibana.Plain HTTP unless TLS is configured.WebCommonly used
5671TCPAMQPSAMQP 0-9-1 and 1.0 over TLS.Encrypted version of 5672.MessagingRegistered with IANA
5672TCPAMQPAdvanced Message Queuing Protocol, used by RabbitMQ and other brokers.Plain by default. AMQPS uses 5671.MessagingRegistered with IANA
5900TCPVNCRemote Frame Buffer (VNC) remote desktop, first display. Further displays use 5901 and up.The session is not encrypted by the basic protocol. Tunnel it through SSH or a VPN.Remote accessRegistered with IANA
5984TCPCouchDBApache CouchDB HTTP API.Plain HTTP unless TLS is configured.DatabaseCommonly used
5985TCPWinRM (HTTP)Windows Remote Management, used by PowerShell remoting.HTTPS version uses 5986.Remote accessRegistered with IANA
5986TCPWinRM (HTTPS)Windows Remote Management over TLS.Encrypted version of 5985.Remote accessRegistered with IANA
6379TCPRedisDefault port of the Redis in-memory data store.Plain by default. TLS is available from Redis 6.DatabaseCommonly used
6443TCPKubernetes API serverDefault secure port of the Kubernetes API server.Served over HTTPS.OtherCommonly used
6514TCPSyslog over TLSSyslog messages over TLS (RFC 5425).Encrypted alternative to 514.Network managementRegistered with IANA
6667TCPIRCInternet Relay Chat servers, plain text.TLS usually uses 6697.MessagingCommonly used
6697TCPIRC over TLSInternet Relay Chat over TLS (RFC 7194).Encrypted version of 6667.MessagingRegistered with IANA
7687TCPNeo4j BoltBolt protocol of the Neo4j graph database.Encryption is a setting on the same port.DatabaseCommonly used
8000TCPPython and Django dev serverDefault of python -m http.server and the Django development server.Development use. No encryption by default.WebCommonly used
8080TCPHTTP alternateAlternative HTTP port, common for proxies, application servers and local testing.Plain text. 8443 is the usual HTTPS counterpart.WebRegistered with IANA
8086TCPInfluxDBHTTP API of the InfluxDB time-series database.Plain HTTP unless TLS is configured.DatabaseCommonly used
8443TCPHTTPS alternateAlternative HTTPS port, common for admin consoles and application servers.Encrypted counterpart of 8080.WebCommonly used
8883TCPMQTT over TLSMQTT messaging over TLS.Encrypted version of 1883.MessagingRegistered with IANA
8888TCPJupyterDefault port of Jupyter Notebook and JupyterLab.Development use. Protect it with the access token.WebCommonly used
9042TCPCassandra (CQL)Client port of Apache Cassandra for the Cassandra Query Language.Encryption is a server setting on the same port.DatabaseCommonly used
9090TCPPrometheusWeb interface and API of the Prometheus monitoring server.Plain HTTP unless TLS is configured.Network managementCommonly used
9092TCPApache KafkaDefault broker port of Apache Kafka.Plain text unless TLS listeners are configured.MessagingCommonly used
9100TCPNode ExporterDefault of Prometheus Node Exporter. Many network printers also accept raw print jobs here.Plain HTTP unless TLS is configured.Network managementCommonly used
9200TCPElasticsearch (HTTP)REST API of Elasticsearch.TLS and authentication depend on the Elasticsearch security settings.DatabaseCommonly used
9300TCPElasticsearch (transport)Node-to-node transport between Elasticsearch cluster members.Keep it on private networks.DatabaseCommonly used
9418TCPGit protocolgit:// read-only transport.No encryption or authentication. HTTPS or SSH are the usual choices.OtherRegistered with IANA
10250TCPKubelet APIAPI of the kubelet agent on each Kubernetes node.Served over HTTPS.OtherCommonly used
11211TCP/UDPMemcachedDefault port of the Memcached cache.No built-in authentication in the default setup. Keep it on private networks.DatabaseCommonly used
15672TCPRabbitMQ managementWeb interface and HTTP API of the RabbitMQ management plugin.Plain HTTP unless TLS is configured.MessagingCommonly used
25565TCPMinecraft (Java Edition)Default server port of Minecraft Java Edition.Game traffic.OtherCommonly used
27017TCPMongoDBDefault port of MongoDB servers.TLS is a server setting on the same port.DatabaseCommonly used
33060TCPMySQL X ProtocolMySQL X Protocol, used by the MySQL Shell and X DevAPI.TLS is a server setting on the same port.DatabaseCommonly used
51820UDPWireGuardConventional listen port for WireGuard VPN tunnels; the port is configurable.Encrypted. Sits in the dynamic range, which IANA does not assign.Remote accessCommonly used

Port number ranges

Port numbers are 16-bit, so there are 65,536 of them (0 to 65535). RFC 6335 §6 splits them into three ranges.
RangeName in RFC 6335Numbers in rangeWhat it is forPorts listed here
0-1023System ports (well-known)1,024Assigned by IANA to core services such as SSH, SMTP, DNS and HTTP. Port 0 is reserved and is not used as a service port.44
1024-49151User ports (registered)48,128Registered with IANA by vendors and projects for their own services, such as databases and message brokers. Many products also use numbers here by convention without a registration.67
49152-65535Dynamic ports (private, ephemeral)16,384Never assigned. Used for the temporary client side of a connection and for private use.1

Plain ports and their encrypted counterparts

Where a service has a separate encrypted port, this is the pair. Several services can also upgrade a plain connection on the same port with STARTTLS or StartTLS.
Plain portEncrypted portWhat changes
80 HTTP443 HTTPSHTTP becomes HTTPS: the same protocol inside TLS.
8080 HTTP alternate8443 HTTPS alternateThe usual alternative-port pair for proxies, consoles and app servers.
110 POP3995 POP3SPOP3 inside TLS from the first byte.
143 IMAP993 IMAPSIMAP inside TLS from the first byte.
587 SMTP submission465 SMTPS (submission over TLS)Submission with STARTTLS versus submission with implicit TLS.
389 LDAP636 LDAPSLDAP inside TLS from the first byte. LDAP can also upgrade on 389 with StartTLS.
21 FTP990 FTPS control (implicit TLS)FTP becomes implicit FTPS. Explicit FTPS upgrades on 21.
119 NNTP563 NNTPSNNTP inside TLS.
1883 MQTT8883 MQTT over TLSMQTT inside TLS.
5672 AMQP5671 AMQPSAMQP inside TLS.
5060 SIP5061 SIP over TLSSIP signalling inside TLS.
5985 WinRM (HTTP)5986 WinRM (HTTPS)WinRM over HTTP becomes WinRM over HTTPS.
514 Syslog6514 Syslog over TLSSyslog over UDP becomes syslog over TLS.
2375 Docker daemon (unencrypted)2376 Docker daemon (TLS)Docker daemon without TLS becomes the TLS-protected one.

Worked examples: what each search finds

Each row is a search typed into the filter above and the rows it returns, computed by the same code as the page.
You typeResultPorts found
4431 port443 HTTPS
22, 80, 4433 ports22 SSH; 80 HTTP; 443 HTTPS
8000-90006 ports8000 Python and Django dev server; 8080 HTTP alternate; 8086 InfluxDB; 8443 HTTPS alternate; 8883 MQTT over TLS; 8888 Jupyter
mysql2 ports3306 MySQL; 33060 MySQL X Protocol
mail7 ports25 SMTP; 110 POP3; 143 IMAP; 465 SMTPS (submission over TLS); 587 SMTP submission; 993 IMAPS; 995 POP3S
database17 ports1433 Microsoft SQL Server; 1434 SQL Server Browser; 1521 Oracle Database listener; 2379 etcd client; 2380 etcd peer; 3306 MySQL; 5432 PostgreSQL; 5984 CouchDB; and 9 more
vpn8 ports500 IKE (ISAKMP); 1194 OpenVPN; 1701 L2TP; 1723 PPTP; 1812 RADIUS authentication; 3389 RDP; 5900 VNC; 51820 WireGuard
udp34 ports53 DNS; 67 DHCP server; 68 DHCP client; 69 TFTP; 88 Kerberos; 111 ONC RPC (rpcbind); 123 NTP; 135 Microsoft RPC endpoint mapper; and 26 more
50000Port 50000 is not in this list. It falls in the dynamic ports (private, ephemeral) range 49152-65535. Not being listed does not mean it is unused.None

Listed ports by category

The 112 listed ports in 9 categories, with the first few by port number.
CategoryPorts listedFirst few
Web1280 HTTP; 443 HTTPS; 3000 JavaScript dev server; 3128 Squid proxy
Mail725 SMTP; 110 POP3; 143 IMAP; 465 SMTPS (submission over TLS)
Database171433 Microsoft SQL Server; 1434 SQL Server Browser; 1521 Oracle Database listener; 2379 etcd client
Remote access1222 SSH; 23 Telnet; 500 IKE (ISAKMP); 1194 OpenVPN
File transfer920 FTP data; 21 FTP; 69 TFTP; 139 NetBIOS session service
Directory688 Kerberos; 389 LDAP; 464 Kerberos password change; 636 LDAPS
Network management2443 WHOIS; 53 DNS; 67 DHCP server; 68 DHCP client
Messaging14119 NNTP; 563 NNTPS; 1883 MQTT; 5060 SIP
Other11631 IPP; 1080 SOCKS proxy; 2181 Apache ZooKeeper; 2375 Docker daemon (unencrypted)

TCP, UDP or both

The transport each listed service is normally used over. Firewall rules are written per transport protocol, so TCP 53 and UDP 53 are two separate rules.
ProtocolWhat it meansPorts listedFirst few
TCPConnection-oriented: reliable, ordered delivery. Web, mail, SSH and most databases.7820 FTP data; 21 FTP; 22 SSH; 23 Telnet
UDPConnectionless: no delivery guarantee, low overhead. DNS queries, DHCP, NTP, SNMP.2167 DHCP server; 68 DHCP client; 69 TFTP; 123 NTP
TCP/UDPBoth are in use for the service, for different purposes.1353 DNS; 88 Kerberos; 111 ONC RPC (rpcbind); 135 Microsoft RPC endpoint mapper

Registered with IANA or commonly used

The Status column of the table uses these two labels.
StatusWhat it meansPorts listed
Registered with IANAThe port is assigned to this service in the IANA Service Name and Transport Protocol Port Number Registry, or by the RFC that defines the service.76
Commonly usedA default that products and tools ship with. It is widely used, but this page does not claim the registry lists the port for that product.36

How to look up a port number

  1. Type a number, range or name. Enter a port such as 443, a list such as 22, 80, 443, a range such as 8000-9000, or a word such as mysql, mail or vpn. The table narrows as you type.
  2. Pick a category. Press a category chip (web, mail, database, remote access, file transfer, directory, network management) to see only those services. Combine it with the protocol and status selectors.
  3. Read the row. Check the protocol (TCP, UDP or both), what the service is for, and the secure variant or caution in the notes column. The Status column says whether IANA registers the number or it is only a common default.
  4. Compare with the range. A number below 1024 is a well-known port, 1024 to 49151 is the registered range, and 49152 and up is dynamic. A number missing from the list is not necessarily unused.
  5. Share or copy. The address bar updates with ?q= as you type, so you can send the same search as a link. Copy results puts the shown rows on your clipboard as tab-separated text for a spreadsheet.

Frequently asked questions

What is the difference between a port and a protocol?
A port is a number from 0 to 65535 that tells the operating system which program on a host should receive a packet. A protocol is the set of rules two programs follow once they are talking, such as HTTP, SMTP or SSH. Ports and protocols are linked only by convention: a web server speaks HTTP on 80 by default, but nothing stops it from doing so on 8080 or any other free number. The word protocol is also used for the transport underneath, TCP or UDP, which is why a row here has a protocol column and a service column.
What is the difference between TCP and UDP ports?
TCP and UDP each have their own set of 65,536 port numbers, so TCP 53 and UDP 53 are different endpoints. TCP sets up a connection and guarantees ordered, retransmitted delivery, which suits web pages, mail and file transfers. UDP sends independent datagrams with no delivery guarantee and little overhead, which suits DNS queries, time sync and real-time traffic. In this list 91 ports use TCP and 34 use UDP; 13 use both. A firewall rule that allows one does not allow the other.
Why does HTTPS use port 443?
Because IANA assigned it. There is no formula behind the number: it is an entry in the registry that maps 443 to https, and browsers use it by default for https:// addresses when no port is written. HTTP uses 80 the same way. Servers can listen on other ports, and then the address must name the port, as in https://example.com:8443/. Port 443 is also used over UDP for HTTP/3, which runs on QUIC (RFC 9114).
Does this page scan ports or tell me whether a port is open?
No. It is a lookup table that sits in the page; it sends no packets and makes no connection to any host, yours or anyone else’s. Whether a port is open depends on a specific machine, its firewall and the programs running on it, and a reference list cannot know that. To see what is listening on a computer you manage, use that computer’s own tools, for example ss -ltn or lsof -i on Linux and macOS, or netstat -ano on Windows.
What are well-known, registered and dynamic ports?
RFC 6335 §6 divides the numbers into three ranges. System ports, also called well-known, are 0-1023 (1,024 numbers) and hold core services such as SSH, SMTP and HTTP. User ports, also called registered, are 1024-49151 (48,128 numbers) and are registered by vendors and projects. Dynamic ports, also called private or ephemeral, are 49152-65535 (16,384 numbers) and are never assigned: clients use them as the temporary source port of a connection. Port 0 is reserved. Operating systems pick their own ephemeral range, which can differ from the IANA one.
What does Registered with IANA mean, and what does Commonly used mean?
Registered with IANA means the number is assigned to that service in the IANA Service Name and Transport Protocol Port Number Registry, or by the RFC that defines it. Commonly used means a product ships with that number as its default (Redis on 6379, MongoDB on 27017, Vite on 5173) without this page claiming a registration. Of the 112 ports listed here, 76 are marked registered and 36 commonly used. A default is only a default: administrators can change it.
Why do mail programs offer ports 25, 465 and 587?
They do different jobs. Port 25 is for mail servers relaying messages to each other. Ports 587 and 465 are for mail clients submitting outgoing mail to their own provider after signing in: 587 starts plain and upgrades with STARTTLS, while 465 is encrypted from the first byte (implicit TLS). RFC 8314 re-registered 465 for this purpose and prefers implicit TLS. Reading mail uses a different set: IMAP on 143 or 993 (encrypted), POP3 on 110 or 995 (encrypted).
Can two programs listen on the same port?
Not on the same IP address and transport protocol: the second program usually gets an address-in-use error. Different transports are independent, so a DNS server can hold TCP 53 and UDP 53 at once, and many clients can connect to one listening port because each connection is told apart by the client's address and port. Some systems allow deliberate sharing (the SO_REUSEPORT socket option on Linux, for example), but ordinary services do not rely on it.
Is moving a service to a non-standard port a security measure?
Not on its own. A different port can cut down automated noise in the logs, but anyone who looks for open ports can find the new one, and the service is exactly as exposed as before. Real protection comes from keeping the service off the public internet, strong authentication, current software, encryption and a firewall that allows only what is needed. Several rows in the table carry a note for this reason, such as Telnet, plain FTP and the unauthenticated Docker daemon port.
Is this list complete?
No. The IANA registry holds far more assignments than a page can usefully show. This list has 112 ports: the ones people most often look up, and a row appears only when its number and meaning are firmly established. Software that is not here may still use a port you can find in that product’s documentation, and a port that is not listed is not necessarily free.

How it works

The list was compiled by hand from the IANA Service Name and Transport Protocol Port Number Registry and from the RFCs that define the services (for example RFC 6409 for mail submission, RFC 8314 for 465, RFC 7858 for DNS over TLS, RFC 5425 for syslog over TLS and RFC 9114 for HTTP/3), plus the documented defaults of widely used software. It is not an export of the registry. Each row is one port and one transport label: TCP, UDP, or TCP/UDP when both are in use. The status label Registered with IANA marks numbers assigned to that service; Commonly used marks product defaults and does not say whether the registry also lists the number. The ranges follow RFC 6335 §6: 0-1023, 1024-49151 and 49152-65535. Search accepts a port number, a list of numbers, a range (8000-9000 finds 6 listed ports), or words that must all appear in the service, description, notes, category or status of a row; the words tcp and udp match the protocol. The category chips and the protocol and status selectors narrow the same result. The page makes no network requests to look anything up: the table is part of the page, and the filter runs in your browser. It cannot tell you whether a port is open anywhere. Counts and example results on this page are computed from the list, not typed in. Notes about security describe the protocol, not any particular product version, so check your own software’s documentation.

Sources

More: Web, URLs, images and networkAll developer toolsAll toolsHome & DIY calculators