About Port Reference — Detailed Guide
The Common Port Reference guide catalogs IANA-assigned well-known ports (0-1023), registered ports (1024-49151), and popular developer service ports across TCP and UDP transport protocols.
Each listing provides the official service label, transport layer protocol, architectural usage description, and security hardening recommendations. Built with an offline client-side database, search results render instantaneously without server calls.
Key Features & Capabilities
- Comprehensive directory of well-known ports, databases, cache layers, and messaging brokers
- Clear designation of transport protocols (TCP, UDP, or dual-protocol support)
- Security warnings highlighting critical attack vectors for sensitive ports (SSH, RDP, Redis, MySQL)
- 100% offline client-side dictionary supporting bidirectional numeric and service-name search
How to Use
- 1
Type a port number (e.g. 5432, 27017) or service name (e.g. Postgres, MongoDB) into the search bar.
- 2
Review matching records detailing transport protocol, standard functionality, and security context.
- 3
Use the reference to properly configure firewall ingress rules and container port mappings.
Common Use Cases
- → Configuring cloud security group inbound rules in AWS, Azure, or GCP compute instances
- → Troubleshooting port binding collisions during local Docker and server development
- → Auditing open port exposure and attack surfaces during infrastructure vulnerability reviews
Related Tools
IP Lookup
Lookup IP address geolocation, ISP, ASN, timezone, and network details.
DNS Lookup
Query DNS records including A, AAAA, CNAME, MX, TXT, and NS records for any domain.
URL Parser
Parse URL into protocol, host, port, path, query parameters, and hash components.
HTTP Status Codes
Search and reference HTTP status codes with comprehensive descriptions and usage guides.
HTTP Headers
Reference common HTTP request and response headers with security best practice guidelines.
MIME Types
Lookup MIME types by file extension or discover associated extensions for any content type.
Frequently Asked Questions & Privacy
Can TCP and UDP protocols share the same numeric port number?
Yes. TCP and UDP maintain separate transport layer namespaces. For example, DNS utilizes port 53 across both UDP (standard queries) and TCP (zone transfers).
Why is it dangerous to leave port 6379 (Redis) open to the public Internet?
Redis instances historically run without mandatory authentication and can write arbitrary files to disk, making public exposure a common vector for automated cryptomining worms.