We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
Look up service names and descriptions for TCP/UDP port numbers. Covers IANA standard ports for network management, development, and security.
This is a locally maintained static reference table, not a live official directory, current policy or complete collection. Records without a named source and update date remain unverified.
No data
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
This page searches a curated table of selected TCP/UDP service entries. Search by a port number, service name, or words in a description to find matching rows; read the displayed port or protocol, name, and description together. For instance, a row for 22 may identify ssh, while entries with explicit /tcp or /udp suffixes show which transport protocol that row names.
The IANA Service Name and Transport Protocol Port Number Registry is the authoritative source for registered service and port associations. RFC 6335 describes the 16-bit port space and divides it into System (0–1023), User (1024–49151), and Dynamic (49152–65535) ranges. Those ranges describe number allocation; they do not indicate that a service is currently running on a host.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Type a number such as 22, a service name such as ssh, or a term from a description. Search matches text in the table, so a short keyword can be more useful than a full sentence.
Check the name and description along with the port or protocol field. If the row says 2430/tcp or 2430/udp, keep that suffix when recording the result. A bare number is only the display shown for that row; it does not prove that both protocols apply.
Select a column heading to change sort order, use the column menu to show or hide fields, and move between result pages if there are more matches. Clear the search text to return to the full list.
A result is a table association, not an answer about the state of a particular computer. If a port appears more than once, compare the complete protocol and service fields rather than choosing a row by number alone.
Use cases
See how the tool fits into real work and everyday tasks.
An administrator can look up a port value from an application or firewall log, then compare the candidate service with the host, process, protocol, and surrounding traffic.
A developer can search a service name while documenting a connection requirement and record the protocol suffix when the table provides one.
A security reviewer can use the association as one clue, then verify the intended application and listening process before approving a rule change.
Q&A
Find concise answers to common questions and confusing cases.
No. This is a static reference table; it does not contact a host or test whether a port is open, reachable, or in use by a process.
A number can appear in separate entries for different transport protocols or service associations. Compare the complete port/protocol field and service name for each row.
No. It contains a selected set of entries, not every value in the port-number space or a live copy of the full IANA registry. No match does not establish that a port is unassigned or unused.
Yes. A registry association does not prove what a specific host is running. Applications can be configured differently, so check the system and software configuration when diagnosing real traffic.
Notes
Review scope, result limitations, and important precautions before use.
This lookup does not scan your device or a remote host and cannot identify an open port, public reachability, running process, or safe traffic. A familiar service name is only a reference clue. Before changing a firewall rule or diagnosing an incident, verify the transport protocol, host configuration, process, and relevant logs. Check IANA directly when you need the current registry status or an entry missing from this curated list.
The table's search and category labels are for finding entries. They do not replace the registry's official assignment status, and a row without a protocol suffix should not be read as confirming both TCP and UDP.
Related
Discover related tools, collections, and available API capabilities.