Port Search & Filters
Examples: "80", "ssh", "HTTP", "database", "tcp:22", "udp:53"
Quick Categories
Port Reference Results ({{ filteredPorts.length }} {{ filteredPorts.length === 1 ? 'port' : 'ports' }})
🔍 No ports match your search criteria
Try adjusting your filters or search terms
🔌 TCP/UDP Port Reference Database
Use the search and filters to find port information
Statistics
ℹ️ About TCP/UDP Port Reference
What are TCP and UDP Ports?
TCP (Transmission Control Protocol) and UDP (User Datagram Protocol) ports are numerical identifiers used to distinguish different network services running on the same host. Ports range from 0 to 65535 and are categorized into three ranges: well-known ports (0-1023), registered ports (1024-49151), and dynamic/private ports (49152-65535).
TCP provides reliable, ordered delivery of data with connection establishment and error checking. UDP provides faster, connectionless communication without delivery guarantees.
Port Categories
- System ports (0-1023): Reserved for core services such as HTTP, HTTPS, SSH, FTP, DNS, and SMTP.
- User ports (1024-49151): Assigned by IANA for registered applications and protocols.
- Dynamic/private ports (49152-65535): Available for client-side ephemeral connections and private use.
Common Use Cases
- Network troubleshooting and security analysis
- Firewall rule configuration
- Service discovery and port scanning analysis
- Application development and testing
- System administration and monitoring
- Penetration testing and vulnerability assessment
Authoritative references
- The IANA Service Name and Transport Protocol Port Number Registry is the source of assigned service names and port ranges.
- RFC 6335 defines the modern service-name and port-number registry procedures.
- RFC 9293 specifies TCP, while RFC 768 specifies UDP.
Security Considerations
Open ports represent potential entry points to systems. Follow the principle of least privilege by opening only necessary ports, restricting exposure with firewalls, and regularly auditing listening services. A port number alone does not prove which application is running, so treat this reference as a starting point and confirm live services with banner checks, TLS inspection, or authenticated host inventory.
API Usage Example:
POST /api/tools/network/tcp-udp-port-reference
Content-Type: application/json
{
"search": "443",
"protocol": "tcp",
"range": "well-known",
"category": "web",
"limit": 10
}