Use: Remote GUI access to Linux/Windows (cross-platform).
⚠️
Security: Often misconfigured without authentication. Never expose directly.
6443Kubernetes APITCPRegistered
Kubernetes API server
Use: kubectl and control-plane communication.
8443HTTPS AlternateTCPRegistered
Alternative HTTPS port
Use: Tomcat HTTPS, some admin panels.
8883MQTT (TLS)TCPRegistered
MQTT over TLS
Use: Secure IoT messaging.
9090PrometheusTCPRegistered
Prometheus server web UI
Use: Metrics collection and querying.
9093AlertmanagerTCPRegistered
Prometheus Alertmanager
Use: Alert handling for Prometheus.
9200ElasticsearchTCPRegistered
Elasticsearch REST API
Use: Search engine and analytics.
⚠️
Security: Often exposed without auth. Data leak risk. Restrict access.
9300Elasticsearch ClusterTCPRegistered
Elasticsearch inter-node communication
Use: Cluster communication between Elasticsearch nodes.
9339Google PlayTCPRegistered
Google Play services
Use: Android app store communication.
10250KubeletTCPRegistered
Kubernetes kubelet API
Use: Node-level operations in Kubernetes.
11211MemcachedTCP/UDPRegistered
Memcached caching system
Use: In-memory caching layer.
⚠️
Security: No authentication by default. Used in amplification DDoS attacks.
15672RabbitMQ MgmtTCPRegistered
RabbitMQ management UI
Use: RabbitMQ web dashboard.
51820WireGuardUDPDynamic
WireGuard VPN
Use: Modern, fast VPN protocol.
📖 Most Common Ports (Quick Reference)
🔒 100% private: Reference data is bundled locally. Based on IANA Service Name and Transport Protocol Port Number Registry.
About Port Number Reference
Network ports are 16-bit numbers (0–65535) that identify specific services or processes on a host. When a client connects to a server, it specifies both an IP address and a port. Ports are divided into three ranges: well-known ports (0–1023), registered ports (1024–49151), and dynamic/private ports (49152–65535). Certain ports are permanently assigned by IANA to specific services (80 for HTTP, 443 for HTTPS, 22 for SSH, 3306 for MySQL). Knowing which ports are commonly used — and which are security risks if exposed — is essential for firewall configuration, server hardening, and network troubleshooting. This reference lists the most important ports with their services, protocols, and security notes.
How It Works
Search by port number (e.g., "443") or service name (e.g., "ssh").
Filter by category (web, database, email, file transfer, security, etc.).
Click any row for detailed info: protocol, description, common use.
Danger ports (commonly attacked) are flagged with a ⚠️ warning.
✨ Key Features
✓100+ well-known and registered ports
✓Search by number or service name
✓Filter by category (web, database, email, file, security, dev, other)
✓TCP/UDP protocol indicator
✓Service description and common use
✓Security warnings for commonly-attacked ports
✓Port range reference (well-known, registered, dynamic)
✓RFC and IANA references
✓One-click copy of port number
✓100% client-side — no data sent to any server
🎯 Common Use Cases
→Configuring a firewall (which ports to open/close)
→Debugging "connection refused" errors
→Setting up a new server (what ports should be exposed)
→Hardening a production system (closing dangerous ports)
→Understanding a network scan (nmap output)
→Learning which service runs on which port
→Verifying that a custom port does not conflict with known services
→Checking the security posture of a cloud VM
💡 Advanced Tips & Pro Insights
▸Well-known ports (0–1023) require root/admin privileges to bind on Unix systems. Use ports >1024 for user applications.
▸Always prefer HTTPS (443) over HTTP (80). Port 80 should redirect to 443.
▸Ports commonly attacked: 21 (FTP), 23 (Telnet), 135/137-139/445 (Windows SMB), 1433 (MSSQL), 3306 (MySQL), 3389 (RDP), 5432 (PostgreSQL), 6379 (Redis), 27017 (MongoDB). Never expose these directly to the internet without a firewall.
▸Redis, MongoDB, and Elasticsearch have no authentication by default — exposing them is a critical security risk. Many cloud breaches come from open Redis/MongoDB ports.
▸For remote access, prefer SSH (22) with key-based auth, or VPN, instead of RDP (3389) or VNC (5900).
▸Use "nmap localhost" or "netstat -tuln" to see which ports your server is listening on.
Frequently Asked Questions
Is this port reference free?▾
Yes, this port number reference is completely free with no signup, email, or usage limits.
Is my data safe?▾
Yes, 100% safe. All lookups happen in your browser. Reference data is bundled locally. Nothing is sent to any server.
What is a network port?▾
A network port is a 16-bit number (0–65535) that identifies a specific service or process on a host. Combined with an IP address, it uniquely identifies a communication endpoint.
What are the port ranges?▾
Well-known ports: 0–1023 (assigned by IANA to common services). Registered ports: 1024–49151 (assigned for specific applications). Dynamic/private ports: 49152–65535 (ephemeral, assigned by the OS for client connections).
What is the difference between TCP and UDP ports?▾
TCP is connection-oriented (reliable, ordered). UDP is connectionless (fast, no guarantees). The same port number can be used by TCP and UDP independently — e.g., DNS uses both 53/tcp and 53/udp.
Which ports should I open on a web server?▾
For a typical web server: 22 (SSH, restricted to your IP), 80 (HTTP, redirect to HTTPS), 443 (HTTPS). Close everything else. Add 25/587 for email, or 3306 for MySQL only if accessed remotely (strongly discouraged).
Why is Telnet (port 23) dangerous?▾
Telnet sends data — including passwords — in plaintext. Anyone on the network can sniff credentials. Use SSH instead. Telnet should be disabled on any modern system.
What is an ephemeral port?▾
Ephemeral (dynamic) ports are temporary ports assigned by the OS when a client initiates an outgoing connection. They range from 49152–65535 on most systems. They are released after the connection closes.