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
1786 TCP funk-logger funk-logger Assigned
1786 UDP funk-logger funk-logger Assigned
1787 TCP funk-license funk-license Cimarron Boozer; Eric Wilde Assigned
1787 UDP funk-license funk-license Cimarron Boozer; Eric Wilde Assigned
1788 TCP psmond psmond Will Golson Assigned
1788 UDP psmond psmond Will Golson Assigned
1789 TCP hello hello D. J. Bernstein Assigned
1789 UDP hello hello D. J. Bernstein Assigned
1790 TCP nmsp Narrative Media Streaming Protocol Paul Santinelli Jr. Assigned
1790 UDP nmsp Narrative Media Streaming Protocol Paul Santinelli Jr. Assigned
1791 TCP ea1 EA1 Kirk MacLean Assigned
1791 UDP ea1 EA1 Kirk MacLean Assigned
1792 TCP ibm-dt-2 ibm-dt-2 Sam Borman Assigned
1792 UDP ibm-dt-2 ibm-dt-2 Sam Borman Assigned
1793 TCP rsc-robot rsc-robot Andrew Jay Schneider Assigned
1793 UDP rsc-robot rsc-robot Andrew Jay Schneider Assigned
1794 TCP cera-bcm cera-bcm Leo Moesgaard Assigned
1794 UDP cera-bcm cera-bcm Leo Moesgaard Assigned
1795 TCP dpi-proxy dpi-proxy Charles Gordon Assigned
1795 UDP dpi-proxy dpi-proxy Charles Gordon Assigned
1796 TCP vocaltec-admin Vocaltec Server Administration Scott Petrack Assigned
1796 UDP vocaltec-admin Vocaltec Server Administration Scott Petrack Assigned
1797 TCP uma UMA Martin Kirk Assigned
1797 UDP uma UMA Martin Kirk Assigned
1798 TCP etp Event Transfer Protocol Mike Wray Assigned
1798 UDP etp Event Transfer Protocol Mike Wray Assigned
1799 TCP netrisk NETRISK Kevin Green Assigned
1799 UDP netrisk NETRISK Kevin Green Assigned
1800 TCP ansys-lm ANSYS-License manager Suzanne Lorrin Assigned
1800 UDP ansys-lm ANSYS-License manager Suzanne Lorrin Assigned
1801 TCP msmq Microsoft Message Que Amnon Horowitz Assigned
1801 UDP msmq Microsoft Message Que Amnon Horowitz Assigned
1802 TCP concomp1 ConComp1 Ed Vincent Assigned
1802 UDP concomp1 ConComp1 Ed Vincent Assigned
1803 TCP hp-hcip-gwy HP-HCIP-GWY Allen Baker Assigned
1803 UDP hp-hcip-gwy HP-HCIP-GWY Allen Baker Assigned
1804 TCP enl ENL Brian Olson Assigned
1804 UDP enl ENL Brian Olson Assigned
1805 TCP enl-name ENL-Name Brian Olson Assigned
1805 UDP enl-name ENL-Name Brian Olson Assigned
1806 TCP musiconline Musiconline Craig Weeks Assigned
1806 UDP musiconline Musiconline Craig Weeks Assigned
1807 TCP fhsp Fujitsu Hot Standby Protocol Eiki Iwata Assigned
1807 UDP fhsp Fujitsu Hot Standby Protocol Eiki Iwata Assigned
1808 TCP oracle-vp2 Oracle-VP2 Craig Fowler Assigned
1808 UDP oracle-vp2 Oracle-VP2 Craig Fowler Assigned
1809 TCP oracle-vp1 Oracle-VP1 Craig Fowler Assigned
1809 UDP oracle-vp1 Oracle-VP1 Craig Fowler Assigned
1810 TCP jerand-lm Jerand License Manager Robert Monat Assigned
1810 UDP jerand-lm Jerand License Manager Robert Monat 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 ↗