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
22538-22554 Not specified Unassigned Unassigned
22555 TCP vocaltec-wconf Vocaltec Web Conference Scott Petrack Assigned
22555 UDP vocaltec-phone Vocaltec Internet Phone Scott Petrack Assigned
22556-22762 Not specified Unassigned Unassigned
22763 TCP talikaserver Talika Main Server Laxman C. Marathe 2006-12 Assigned
22763 UDP talikaserver Talika Main Server Laxman C. Marathe 2006-12 Assigned
22764-22799 Not specified Unassigned Unassigned
22800 TCP aws-brf Telerate Information Platform LAN Timo Sivonen Assigned
22800 UDP aws-brf Telerate Information Platform LAN Timo Sivonen Assigned
22801-22950 Not specified Unassigned Unassigned
22951 TCP brf-gw Telerate Information Platform WAN Timo Sivonen Assigned
22951 UDP brf-gw Telerate Information Platform WAN Timo Sivonen Assigned
22952-22999 Not specified Unassigned Unassigned
23000 TCP inovaport1 Inova LightLink Server Type 1 Chris Koeritz 2006-10 Assigned
23000 UDP inovaport1 Inova LightLink Server Type 1 Chris Koeritz 2006-10 Assigned
23001 TCP inovaport2 Inova LightLink Server Type 2 Chris Koeritz 2006-10 Assigned
23001 UDP inovaport2 Inova LightLink Server Type 2 Chris Koeritz 2006-10 Assigned
23002 TCP inovaport3 Inova LightLink Server Type 3 Chris Koeritz 2006-10 Assigned
23002 UDP inovaport3 Inova LightLink Server Type 3 Chris Koeritz 2006-10 Assigned
23003 TCP inovaport4 Inova LightLink Server Type 4 Chris Koeritz 2006-10 Assigned
23003 UDP inovaport4 Inova LightLink Server Type 4 Chris Koeritz 2006-10 Assigned
23004 TCP inovaport5 Inova LightLink Server Type 5 Chris Koeritz 2006-10 Assigned
23004 UDP inovaport5 Inova LightLink Server Type 5 Chris Koeritz 2006-10 Assigned
23005 TCP inovaport6 Inova LightLink Server Type 6 Chris Koeritz 2006-10 Assigned
23005 UDP inovaport6 Inova LightLink Server Type 6 Chris Koeritz 2006-10 Assigned
23006-23052 Not specified Unassigned Unassigned
23053 TCP gntp Generic Notification Transport Protocol The Growl Project 2012-02-07 Assigned
23053 UDP Reserved Reserved
23054-23271 Not specified Unassigned Unassigned
23272 TCP Reserved Reserved
23272 UDP s102 S102 application Kimmo Kymalainen 2009-08-26 Assigned
23273-23293 Not specified Unassigned Unassigned
23294 TCP 5afe-dir 5AFE SDN Directory Ayoda GmbH 2016-04-01 Assigned
23294 UDP 5afe-disc 5AFE SDN Directory discovery Ayoda GmbH 2016-04-01 Assigned
23295-23332 Not specified Unassigned Unassigned
23333 TCP elxmgmt Emulex HBAnyware Remote Management Maziar Tamadon 2007-11-06 Assigned
23333 UDP elxmgmt Emulex HBAnyware Remote Management Maziar Tamadon 2007-11-06 Assigned
23334-23399 Not specified Unassigned Unassigned
23400 TCP novar-dbase Novar Data Keith Kilroy 2006-02 Assigned
23400 UDP novar-dbase Novar Data Keith Kilroy 2006-02 Assigned
23401 TCP novar-alarm Novar Alarm Keith Kilroy 2006-02 Assigned
23401 UDP novar-alarm Novar Alarm Keith Kilroy 2006-02 Assigned
23402 TCP novar-global Novar Global Keith Kilroy 2006-02 Assigned
23402 UDP novar-global Novar Global Keith Kilroy 2006-02 Assigned
23403-23455 Not specified Unassigned Unassigned
23456 TCP aequus Aequus Service James Anson 2009-02-12 Assigned
23456 UDP Reserved Reserved
23457 TCP aequus-alt Aequus Service Mgmt James Anson 2009-02-12 Assigned
23457 UDP Reserved Reserved
23458-23545 Not specified Unassigned Unassigned

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 ↗