Networking reference

TCP & UDP Port Numbers – Service & Protocol Lookup

Search the complete IANA service-name and port-number registry by port, protocol, service, assignee or RFC, including TCP, UDP, SCTP, DCCP and unqualified entries.

Search this dataset

Use exact codes, names or any declared searchable field.

TCP & UDP Port Numbers – Service & Protocol LookupShowing 50 of 14,533 records
PortProtocolServiceDescriptionAssigneeRegistration dateReference/RFCStatusRecord details
1936 TCP jetcmeserver JetCmeServer Server Port Assigned
1936 UDP jetcmeserver JetCmeServer Server Port Assigned
1937 TCP jwserver JetVWay Server Port Assigned
1937 UDP jwserver JetVWay Server Port Assigned
1938 TCP jwclient JetVWay Client Port Assigned
1938 UDP jwclient JetVWay Client Port Assigned
1939 TCP jvserver JetVision Server Port Assigned
1939 UDP jvserver JetVision Server Port Assigned
1940 TCP jvclient JetVision Client Port Stephen Tsun Assigned
1940 UDP jvclient JetVision Client Port Stephen Tsun Assigned
1941 TCP dic-aida DIC-Aida Frans S.C. Witte Assigned
1941 UDP dic-aida DIC-Aida Frans S.C. Witte Assigned
1942 TCP res Real Enterprise Service Bob Janssen Assigned
1942 UDP res Real Enterprise Service Bob Janssen Assigned
1943 TCP beeyond-media Beeyond Media Bob Deblier Assigned
1943 UDP beeyond-media Beeyond Media Bob Deblier Assigned
1944 TCP close-combat close-combat David Hua Assigned
1944 UDP close-combat close-combat David Hua Assigned
1945 TCP dialogic-elmd dialogic-elmd Roger Kay Assigned
1945 UDP dialogic-elmd dialogic-elmd Roger Kay Assigned
1946 TCP tekpls tekpls Brian Abramson Assigned
1946 UDP tekpls tekpls Brian Abramson Assigned
1947 TCP sentinelsrm SentinelSRM Michael Zunke 2010-07-23 Assigned
1947 UDP sentinelsrm SentinelSRM Michael Zunke 2010-07-23 Assigned
1948 TCP eye2eye eye2eye Trevor Bell Assigned
1948 UDP eye2eye eye2eye Trevor Bell Assigned
1949 TCP ismaeasdaqlive ISMA Easdaq Live Stephen Dunne Assigned
1949 UDP ismaeasdaqlive ISMA Easdaq Live Stephen Dunne Assigned
1950 TCP ismaeasdaqtest ISMA Easdaq Test Stephen Dunne Assigned
1950 UDP ismaeasdaqtest ISMA Easdaq Test Stephen Dunne Assigned
1951 TCP bcs-lmserver bcs-lmserver Andy Warner Assigned
1951 UDP bcs-lmserver bcs-lmserver Andy Warner Assigned
1952 TCP mpnjsc mpnjsc Takenori Miyahara Assigned
1952 UDP mpnjsc mpnjsc Takenori Miyahara Assigned
1953 TCP rapidbase Rapid Base Antoni Wolski Assigned
1953 UDP rapidbase Rapid Base Antoni Wolski Assigned
1954 TCP abr-api ABR-API (diskbridge) Assigned
1954 UDP abr-api ABR-API (diskbridge) Assigned
1955 TCP abr-secure ABR-Secure Data (diskbridge) Graham Wooden Assigned
1955 UDP abr-secure ABR-Secure Data (diskbridge) Graham Wooden Assigned
1956 TCP vrtl-vmf-ds Vertel VMF DS Alan Akahoshi Assigned
1956 UDP vrtl-vmf-ds Vertel VMF DS Alan Akahoshi Assigned
1957 TCP unix-status unix-status Thomas Erskine Assigned
1957 UDP unix-status unix-status Thomas Erskine Assigned
1958 TCP dxadmind CA Administration Daemon John Birrell Assigned
1958 UDP dxadmind CA Administration Daemon John Birrell Assigned
1959 TCP simp-all SIMP Channel Tim Hunnewell Assigned
1959 UDP simp-all SIMP Channel Tim Hunnewell Assigned
1960 TCP nasmanager Merit DAC NASmanager Richard S. Conto Assigned
1960 UDP nasmanager Merit DAC NASmanager Richard S. Conto Assigned

Look up a port number, service name, transport protocol, assignee or RFC in IANA's current registry. The table keeps every row in the 17 August 2026 snapshot, so one port can appear more than once when it has separate TCP, UDP or other registrations.

How to use the port lookup

Enter a number such as 22, 53, 80, 443, 3306 or 8080 to find exact registrations and any registered range containing that port. You can also search for a service such as ssh or mysql, a protocol, an assignee, or reference text such as RFC9110. Use the Protocol and Status filters when a search returns several rows.

Blank values mean the source registry does not provide that field. They have not been guessed. Assignee identifiers are resolved against the people and organisations directory in IANA's XML registry where a readable name is available.

Port ranges and status labels

  • System ports: 0–1023. These are also commonly called well-known ports.
  • User ports: 1024–49151. IANA can register services in this range.
  • Dynamic or private ports: 49152–65535. IANA does not assign services from this range.

Status is a page-level label derived from the source row. Reserved and Unassigned follow IANA's description. Rows whose source text identifies a de-registration or removal are labelled Deprecated or removed. A row with a service name but no port is labelled Service name only. All other rows are labelled Assigned.

Why the same port can have several entries

TCP and UDP are different transport protocols, so the same number can be registered for both without representing the same network conversation. The registry also includes SCTP, DCCP, aliases, historic records and registrations without a specified transport protocol. They remain in this database so the source is not reduced to a hand-picked list.

Common port questions

What service normally uses port 22?

IANA registers ssh on port 22 for TCP and UDP, with an additional SCTP registration. In everyday networks, TCP port 22 is the familiar SSH remote-access service.

Why does port 53 show TCP and UDP?

The domain service is registered on port 53 for both TCP and UDP. DNS software chooses the transport according to the operation and response requirements.

What is the difference between ports 80 and 443?

IANA associates port 80 with HTTP-related service names and port 443 with HTTPS. A registration describes the conventional use; it does not inspect or guarantee the traffic running there.

What uses port 3306?

The registry lists mysql on port 3306 for TCP and UDP. MySQL client connections are ordinarily associated with TCP, but this page retains both official registry rows.

Is port 8080 always an HTTP proxy?

No. IANA registers http-alt on port 8080 for TCP and UDP, but applications can use ports differently. Identify the listening process and configuration before drawing a security conclusion.

Should I open a port because it is registered here?

No. Open only the ports required by a known application and restrict source networks where possible. A registry entry is not a firewall recommendation.

IANA updates the registry as assignments change. Use Report incorrect data if this snapshot no longer matches the official record, and include the IANA or RFC link so the change can be verified.

Provenance

Data sources

Internet Assigned Numbers Authority

Service Name and Transport Protocol Port Number Registry

Primary officialVisit source ↗
Internet Assigned Numbers Authority

Service Name and Transport Protocol Port Number Registry (CSV)

Primary officialVisit source ↗
Internet Assigned Numbers Authority

Service Name and Transport Protocol Port Number Registry (XML)

Primary officialVisit source ↗
Internet Engineering Task Force

RFC 6335: Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry

Primary standardVisit source ↗
Internet Engineering Task Force

RFC 7605: Recommendations on Using Assigned Transport Port Numbers

Primary standardVisit source ↗
Internet Assigned Numbers Authority

Licensing Terms

Primary officialVisit source ↗