Common Ports Reference

A comprehensive, searchable database of 80+ common network ports used in networking, system administration, and security. Search by port number, service name, or keyword to quickly find the port information you need for firewall rules, port forwarding, and security auditing.

Port	Proto	Service	Description	Security

Understanding Network Ports

A network port is a logical endpoint for network communication. Ports allow a single IP address to host multiple services — your computer can run a web server on port 80 and an email server on port 25 simultaneously. Ports are numbered from 0 to 65535 and divided into three ranges.

Ports are essential for port forwarding, firewall configuration, and network security. Use our Port Checker to verify whether a specific port is open on your network.

Port Number Ranges

Range	Name	Numbers	Usage
Well-Known	System Ports	0 – 1023	Standard services (HTTP, SSH, DNS, etc.)
Registered	User Ports	1024 – 49151	Application-specific (MySQL, RDP, etc.)
Dynamic	Ephemeral Ports	49152 – 65535	Temporary client-side connections

Most Critical Ports for Home Networks

If you're managing a home network or small office, these are the ports you'll interact with most frequently when configuring your router at 192.168.1.1:

Port	Service	When You Need It
80/443	HTTP/HTTPS	Web browsing — always open outbound
53	DNS	Domain resolution — essential for all internet use
3074	Xbox Live	Port forward for Open NAT gaming
25565	Minecraft	Forward for hosting a Minecraft server
32400	Plex	Forward for remote Plex access
1194/51820	VPN	Forward for hosting VPN server at home
5060	SIP/VoIP	Forward for VoIP phone systems

Pro Tip: Never expose database ports (3306, 5432, 27017) or remote access ports (3389, 5900) directly to the internet. Always use a VPN or SSH tunnel for remote access. Use our Port Checker to audit which ports are visible from the internet, and configure your NAT firewall to block unnecessary inbound traffic.

TCP vs UDP Explained

Ports operate over two transport protocols. Understanding the difference is important when creating firewall rules or port forwarding configurations:

Feature	TCP	UDP
Connection	Connection-oriented (3-way handshake)	Connectionless
Reliability	Guaranteed delivery, ordering	Best-effort, no guarantees
Speed	Slower (overhead)	Faster (minimal overhead)
Use Cases	Web, email, file transfer, databases	DNS, VoIP, gaming, streaming, VPN
Firewall Handling	Stateful tracking easy	Harder to track state

When setting up port forwarding, ensure you select the correct protocol (TCP, UDP, or Both). Many gaming services require both TCP and UDP on the same port. Check the NAT type requirements for your specific application.

Note: Ports are not inherently secure or insecure — the service running on the port determines security. Port 443 (HTTPS) is considered secure because it uses TLS encryption, while port 80 (HTTP) is not because data is transmitted in plain text. Always prefer encrypted alternatives (SSH over Telnet, SFTP over FTP, HTTPS over HTTP). Check your network security with our Port Checker.

Port Security Best Practices

Close unused ports — Only open ports for services you actively use. Audit with our Port Checker.
Use encrypted alternatives — SSH (22) over Telnet (23), SFTP over FTP (21), HTTPS (443) over HTTP (80).
Change default ports — Move SSH, RDP, and admin panels to non-standard ports to reduce automated attacks.
Enable your router firewall — Configure at 192.168.1.1. Block all inbound traffic except explicitly forwarded ports.
Monitor port connections — Use network traffic monitoring to detect unexpected connections.
Understand NAT — Your router's NAT firewall blocks unsolicited inbound connections by default. Port forwarding creates deliberate exceptions.

Checking If a Port Is Open

Use our Port Checker tool or command-line utilities to verify port accessibility:

# Windows — Check listening ports
netstat -an | findstr "LISTENING"

# Linux/macOS — Check listening ports
ss -tlnp
# or
netstat -tlnp

# Test remote port
nc -zv example.com 443

# PowerShell
Test-NetConnection -ComputerName example.com -Port 443

Key Takeaways

Ports 0-1023 are well-known system ports assigned to standard services like HTTP (80) and SSH (22).
Never expose database or remote access ports directly to the internet.
Always use encrypted service alternatives: HTTPS over HTTP, SSH over Telnet, SFTP over FTP.
Use our Port Checker to audit your network's open ports.
When port forwarding, specify the correct protocol (TCP, UDP, or both) for each service.
Your router's NAT firewall blocks inbound connections by default — port forwarding creates exceptions.

Video: Network Ports Explained

Related Tools & Guides

Frequently Asked Questions

What is the difference between TCP and UDP ports?

TCP ports provide reliable, ordered delivery with error checking — used for web, email, and file transfers. UDP ports provide fast, connectionless delivery — used for DNS, gaming, VoIP, and streaming. Many services use both protocols on the same port number.

Which ports should I never expose to the internet?

Database ports (3306/MySQL, 5432/PostgreSQL, 27017/MongoDB), file sharing ports (445/SMB, 139/NetBIOS), and unencrypted remote access (23/Telnet, 5900/VNC). These are common targets for automated attacks and should only be accessible via VPN or SSH tunnel.

How do I check which ports are open on my router?

Use our Port Checker to scan from outside your network. Log in to your router at 192.168.1.1 to review port forwarding rules. From inside your network, use netstat or ss commands to list listening ports.

Why do I need to forward ports for gaming?

Online games use specific ports for matchmaking and game traffic. Your router's NAT firewall blocks incoming connections by default, resulting in Strict or Moderate NAT types. Port forwarding opens these ports for a specific device, achieving Open NAT for better connectivity.

Can two services use the same port?

No, two services cannot listen on the same port and protocol simultaneously on the same IP address. However, the same port number can be used on different protocols (TCP and UDP) or different IP addresses. This is why web servers use 80 for HTTP and 443 for HTTPS — different ports for different services.

About Tommy N.

Tommy is the founder of RouterHax and a network engineer with 10+ years of experience in home and enterprise networking. He specializes in router configuration, WiFi optimization, and network security. When not writing guides, he's testing the latest mesh WiFi systems and helping readers troubleshoot their home networks.