HandyTools Hub

Common Port Reference

Search 70+ common TCP/UDP ports with descriptions.

Your data never leaves your browser

Port Protocol Service Description
80 TCP HTTP Standard unencrypted web traffic. Usually redirects to HTTPS (443) on modern sites.
443 TCP HTTPS HTTP over TLS/SSL. The default for secure websites and APIs.
591 TCP FileMaker HTTP FileMaker Pro web publishing over HTTP (alternate for port 80).
8000 TCP HTTP Alt / Django Common alternative HTTP port; default for Django and many Python dev servers.
8008 TCP HTTP Alt Official IANA alternative for HTTP; used by some appliances and admin panels.
8080 TCP HTTP Alt / Proxy The most common HTTP alternative — Tomcat, proxies, caching services, and dev servers.
8443 TCP HTTPS Alt Alternative HTTPS port, typical for Tomcat SSL and admin consoles.
20 TCP FTP (Data) FTP data transfer channel in active mode.
21 TCP FTP (Control) FTP command/control channel. Plain-text credentials — prefer SFTP or FTPS.
22 TCP SSH / SFTP Secure Shell for encrypted logins, tunneling, and SFTP file transfer.
69 UDP TFTP Trivial File Transfer Protocol. Lightweight, no auth — used for PXE boot and device firmware.
115 TCP SFTP (legacy) Simple File Transfer Protocol, an early predecessor — not the SSH-based SFTP.
873 TCP rsync rsync daemon protocol for fast incremental file synchronization.
989 TCP FTPS (Data) FTP data channel over TLS/SSL.
990 TCP FTPS (Control) FTP control channel over TLS/SSL (implicit FTPS).
2049 TCP/UDP NFS Network File System for sharing directories between Unix/Linux systems.
25 TCP SMTP Server-to-server email relay. Often blocked for outbound use by ISPs and cloud hosts.
110 TCP POP3 Post Office Protocol v3 — downloads mail to one device, usually deleting it from the server.
143 TCP IMAP Internet Message Access Protocol — mail stays on the server and syncs across devices.
465 TCP SMTPS SMTP over implicit TLS. Deprecated once, now re-standardized for message submission.
587 TCP SMTP (Submission) Message submission with STARTTLS. The recommended port for sending mail from clients.
993 TCP IMAPS IMAP over TLS/SSL. The standard for secure mailbox access.
995 TCP POP3S POP3 over TLS/SSL for encrypted mail retrieval.
53 TCP/UDP DNS Domain Name System. UDP for queries, TCP for zone transfers and large responses.
67 UDP DHCP (Server) DHCP server side — hands out IP addresses and network configuration to clients.
68 UDP DHCP (Client) DHCP client side — receives address leases and renewals from the server.
88 TCP/UDP Kerberos Kerberos authentication, central to Active Directory domains.
123 UDP NTP Network Time Protocol for clock synchronization across systems.
137 TCP/UDP NetBIOS-NS NetBIOS name service on legacy Windows networks.
138 UDP NetBIOS-DGM NetBIOS datagram service on legacy Windows networks.
139 TCP NetBIOS-SSN NetBIOS session service; older SMB file sharing transport.
161 UDP SNMP Simple Network Management Protocol for monitoring routers, switches, and servers.
162 UDP SNMP Trap Receives asynchronous SNMP trap alerts from managed devices.
179 TCP BGP Border Gateway Protocol — the routing protocol of the internet backbone.
389 TCP/UDP LDAP Lightweight Directory Access Protocol for directory services like Active Directory.
445 TCP SMB Server Message Block — Windows file and printer sharing (SMB direct over TCP).
514 UDP Syslog Syslog for forwarding log messages to a central collector.
515 TCP LPD Line Printer Daemon protocol for network printing.
631 TCP/UDP IPP / CUPS Internet Printing Protocol, used by CUPS on Linux and macOS.
636 TCP LDAPS LDAP over TLS/SSL for encrypted directory access.
1194 TCP/UDP OpenVPN Default port for OpenVPN tunnels (usually UDP).
1723 TCP PPTP Point-to-Point Tunneling Protocol VPN. Legacy and considered insecure.
5060 TCP/UDP SIP Session Initiation Protocol for VoIP call setup.
5061 TCP SIP over TLS Encrypted SIP signaling.
23 TCP Telnet Unencrypted remote terminal. Obsolete and insecure — use SSH instead.
3389 TCP/UDP RDP Remote Desktop Protocol for Windows remote administration.
5900 TCP VNC Virtual Network Computing for graphical remote desktop access.
1433 TCP Microsoft SQL Server Default MSSQL database engine port.
1434 UDP MSSQL Browser SQL Server Browser service for resolving named instances.
1521 TCP Oracle DB Oracle Database listener default port.
3306 TCP MySQL / MariaDB Default port for MySQL and MariaDB servers.
5432 TCP PostgreSQL Default PostgreSQL server port.
5984 TCP CouchDB Apache CouchDB HTTP API.
6379 TCP Redis Redis in-memory data store. Never expose to the public internet without auth.
9042 TCP Cassandra (CQL) Apache Cassandra native CQL transport.
9200 TCP Elasticsearch Elasticsearch REST/HTTP API.
9300 TCP Elasticsearch (Transport) Elasticsearch inter-node cluster communication.
11211 TCP/UDP Memcached Memcached distributed memory caching system.
27017 TCP MongoDB Default MongoDB server port.
27018 TCP MongoDB (Shard) MongoDB shard server default port.
1883 TCP MQTT MQTT lightweight publish/subscribe messaging, common in IoT.
4222 TCP NATS NATS messaging system client connections.
5672 TCP AMQP (RabbitMQ) Advanced Message Queuing Protocol — default RabbitMQ port.
8883 TCP MQTT over TLS Secure MQTT over TLS/SSL.
9092 TCP Kafka Apache Kafka broker default port.
15672 TCP RabbitMQ Management RabbitMQ web management console and HTTP API.
61613 TCP STOMP (ActiveMQ) STOMP text-based messaging protocol on ActiveMQ.
2181 TCP Zookeeper Apache Zookeeper coordination service client port.
2375 TCP Docker (unencrypted) Docker REST API without TLS. Extremely dangerous if exposed publicly.
2376 TCP Docker (TLS) Docker REST API over TLS — the secure way to expose the Docker daemon.
3000 TCP Dev Server Default for many dev servers: React (create-react-app), Rails, Grafana, Express demos.
5000 TCP Dev Server Default for Flask and many Python/Node dev servers (also Docker Registry, UPnP on some systems).
5601 TCP Kibana Kibana web UI for visualizing Elasticsearch data.
6443 TCP Kubernetes API Kubernetes API server default port.
8081 TCP HTTP Alt Common secondary admin/proxy port; React Native Metro runs on 8081 by default.
8500 TCP Consul HashiCorp Consul HTTP API and web UI.
9000 TCP PHP-FPM / SonarQube Used by PHP-FPM, SonarQube, Portainer, and many admin panels.
10250 TCP Kubelet API Kubernetes kubelet HTTPS API on each node.
1080 TCP SOCKS Proxy SOCKS proxy protocol, widely used for tunneling traffic.
3128 TCP Squid Proxy Squid caching web proxy default port.

Port Reference is a searchable, category-filtered directory of the TCP and UDP ports you actually run into — web and mail standards, databases, message queues, dev servers, and infrastructure services. Instead of searching forum threads to remember whether Elasticsearch is 9200 or 9300, look it up in seconds. It is built for developers configuring firewalls, DevOps engineers reading connection logs, and anyone auditing what is listening on a machine.

How to Use

  • Search: Type a port number like 443 or a keyword like redis to filter instantly.
  • Filter by category: Narrow the table to web, email, databases, remote access, messaging, and more.
  • Copy: Click Copy next to any row to copy the port number to your clipboard.

Features

  • 70+ well-known TCP/UDP ports with plain-language descriptions
  • Search by port number, service name, or description
  • Category chips for web, file transfer, email, network, remote access, databases, messaging, and dev tools
  • One-click copy of any port number
  • Runs entirely in your browser — no data is sent anywhere

Well-Known vs. Registered vs. Dynamic Ports

Port numbers run from 0 to 65535 and are split into three ranges. Ports 0–1023 are the “well-known” ports assigned by IANA to core protocols — 22 SSH, 25 SMTP, 53 DNS, 80 HTTP, 443 HTTPS. Ports 1024–49151 are “registered” ports, where applications like MySQL (3306), PostgreSQL (5432), Redis (6379), and MongoDB (27017) live. Ports 49152–65535 are dynamic or ephemeral ports that your OS hands out temporarily to the client side of each connection.

A common gotcha: many services use both TCP and UDP on the same number (DNS on 53 is the classic example), and some defaults are dangerous to expose. Docker’s unencrypted API on 2375, Redis on 6379, and Elasticsearch on 9200 have all been behind major breaches when left open to the internet. When in doubt, bind to localhost and firewall everything else.

Use Cases

  • Writing firewall rules or security groups and double-checking which port a service needs
  • Decoding netstat or ss output to identify what is listening on a server
  • Configuring connection strings for databases and message queues
  • Studying for networking certifications (Network+, CCNA, Security+)

Frequently Asked Questions

What is port 443 used for?

Port 443 is the standard port for HTTPS — web traffic encrypted with TLS/SSL. Nearly every modern website and API uses it.

What is the difference between port 80 and 8080?

Port 80 is the official HTTP port for unencrypted web traffic. Port 8080 is an unofficial alternative commonly used by dev servers, proxies, and admin panels like Tomcat.

Which port does SSH use?

SSH uses TCP port 22. The same port also carries SFTP file transfers and SSH tunneling.

Is port 465 or 587 better for sending email?

Port 587 with STARTTLS is the recommended port for email submission from clients. Port 465 (implicit TLS) is also valid again, but port 25 is only for server-to-server relay.

Why should I never expose port 6379 or 27017 publicly?

Redis (6379) and MongoDB (27017) often run without authentication by default. Exposing them to the internet is a classic source of data breaches — bind them to localhost or put them behind a firewall.