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
4329 UDP Reserved Reserved
4330 TCP dey-sapi DEY Storage Administration REST API DEY Storage Systems, Inc. 2013-03-01 Assigned
4330 UDP Reserved Reserved
4331 TCP ktickets-rest ktickets REST API for event management and ticketing systems (embedded POS devices) KeyTicket Solutions 2014-04-04 Assigned
4331 UDP Reserved Reserved
4332 TCP getty-focus Getty Images FOCUS service Matthew Margolis 2019-04-18 Assigned
4332 UDP Reserved Reserved
4333 TCP ahsp ArrowHead Service Protocol (AHSP) QuantuMatriX Technologies 2014-04-10 Assigned
4333 UDP ahsp ArrowHead Service Protocol (AHSP) QuantuMatriX Technologies 2014-04-10 Assigned
4333 SCTP ahsp ArrowHead Service Protocol (AHSP) QuantuMatriX Technologies 2014-04-10 Assigned
4334 TCP netconf-ch-ssh NETCONF Call Home (SSH) IESG 2016-01-12 [RFC8071] Assigned
4334 UDP Reserved Reserved
4335 TCP netconf-ch-tls NETCONF Call Home (TLS) IESG 2016-01-12 [RFC8071] Assigned
4335 UDP Reserved Reserved
4336 TCP restconf-ch-tls RESTCONF Call Home (TLS) IESG 2016-01-12 [RFC8071] Assigned
4336 UDP Reserved Reserved
4337-4339 Not specified Unassigned Unassigned
4340 TCP gaia Gaia Connector Protocol Philippe Detournay 2007-11-12 Assigned
4340 UDP gaia Gaia Connector Protocol Philippe Detournay 2007-11-12 Assigned
4341 TCP Reserved 2007-11-12 Reserved
4341 UDP lisp-data LISP Data Packets IESG 2007-11-12 [RFC9300] Assigned
4342 TCP Reserved Reserved
4342 UDP lisp-control LISP Control Packets IETF 2007-05 [RFC9301] Assigned
4343 TCP unicall UNICALL James Powell Assigned
4343 UDP unicall UNICALL James Powell Assigned
4344 TCP vinainstall VinaInstall Jay Slupesky Assigned
4344 UDP vinainstall VinaInstall Jay Slupesky Assigned
4345 TCP m4-network-as Macro 4 Network AS Paul Wren Assigned
4345 UDP m4-network-as Macro 4 Network AS Paul Wren Assigned
4346 TCP elanlm ELAN LM Paul Ballew Assigned
4346 UDP elanlm ELAN LM Paul Ballew Assigned
4347 TCP lansurveyor LAN Surveyor Michael Swan Assigned
4347 UDP lansurveyor LAN Surveyor Michael Swan Assigned
4348 TCP itose ITOSE Michael Haeuptle Assigned
4348 UDP itose ITOSE Michael Haeuptle Assigned
4349 TCP fsportmap File System Port Map Ron Minnich Assigned
4349 UDP fsportmap File System Port Map Ron Minnich Assigned
4350 TCP net-device Net Device Glenn Peterson Assigned
4350 UDP net-device Net Device Glenn Peterson Assigned
4351 TCP plcy-net-svcs PLCY Net Services J.J. Ekstrom Assigned
4351 UDP plcy-net-svcs PLCY Net Services J.J. Ekstrom Assigned
4352 TCP pjlink Projector Link Mitsuo Kodama 2005-06 Assigned
4352 UDP pjlink Projector Link Mitsuo Kodama 2005-06 Assigned
4353 TCP f5-iquery F5 iQuery Tom Kee Assigned
4353 UDP f5-iquery F5 iQuery Tom Kee Assigned
4354 TCP qsnet-trans QSNet Transmitter Assigned
4354 UDP qsnet-trans QSNet Transmitter Assigned
4355 TCP qsnet-workst QSNet Workstation Assigned
4355 UDP qsnet-workst QSNet Workstation Assigned
4356 TCP qsnet-assist QSNet Assistant 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 ↗