Suggested next steps
Continue this workflow
Move to a practical next or previous step without transferring your entered values.
About Common Port Service Lookup – Standard TCP & UDP Ports
Look up standard and widely observed service associations for TCP and UDP port numbers.
Quickly identify common services (such as SSH, HTTPS, DNS, MySQL, and Redis) along with protocol differences and standard IANA numeric ranges.
Input is processed locally in your browser and is not sent to Navorika.
How the calculation works
Curated local reference
Searches a vetted table of standardized network services and protocol designations.
Protocol specificity
Distinguishes between connection-oriented TCP services and connectionless UDP services sharing the same numeric port.
Numeric range classification
Categorizes ports into System/Well-Known (0–1023), User/Registered (1024–49151), and Dynamic/Private (49152–65535).
How to use this tool
- 1Enter an integer port number from 0 through 65535.
- 2Select the transport layer protocol (TCP, UDP, or Both).
- 3Review the common service name, standard purpose, and protocol assignment.
- 4Inspect the port range classification for firewall and network policy compliance.
- 5Copy the lookup summary or export the result.
Understanding the result
Port 22 is commonly used for SSH (Secure Shell) over TCP, but has no standard UDP assignment.
Port 53 serves DNS queries primarily over UDP for speed, but switches to TCP for large responses (>512 bytes) and zone transfers.
If a port has no common service listed, it indicates that no widely recognized service uses it by default in this reference table.
Important limitations
- A port number lookup does not verify whether an active service or daemon is currently running on any host.
- Services can be configured to listen on arbitrary non-standard ports (e.g. running SSH on port 2222).
- This reference focuses on common assignments and does not attempt to reproduce all 65,536 IANA registration entries.
Explore this topic
Frequently asked questions
Can two applications use the same port number at the same time?
Generally, only one application can bind to a given combination of IP address, port number, and transport protocol (TCP or UDP) simultaneously, though modern sockets support options like SO_REUSEPORT.
Why do DNS and LDAP use both TCP and UDP?
They utilize UDP for lightweight, low-latency client queries and fall back to TCP when payloads exceed UDP packet limits, require fragmentation, or perform stateful replication.
Does this tool scan my computer or network?
No. This is purely a reference search tool operating against a local database. No network packets or socket connection attempts are ever initiated.
Related tools
Selected from curated relationships first, then the same subtopic and category.