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
401 UDP ups Uninterruptible Power Supply Charles Bennett 2008-08-29 Assigned
402 TCP genie Genie Protocol Mark Hankin Assigned
402 UDP genie Genie Protocol Mark Hankin Assigned
403 TCP decap decap Assigned
403 UDP decap decap Assigned
404 TCP nced nced Assigned
404 UDP nced nced Assigned
405 TCP ncld ncld Richard Jones Assigned
405 UDP ncld ncld Richard Jones Assigned
406 TCP imsp Interactive Mail Support Protocol John Myers Assigned
406 UDP imsp Interactive Mail Support Protocol John Myers Assigned
407 TCP timbuktu Timbuktu Marc Epard Assigned
407 UDP timbuktu Timbuktu Marc Epard Assigned
408 TCP prm-sm Prospero Resource Manager Sys. Man. Assigned
408 UDP prm-sm Prospero Resource Manager Sys. Man. Assigned
409 TCP prm-nm Prospero Resource Manager Node Man. B. Clifford Neuman Assigned
409 UDP prm-nm Prospero Resource Manager Node Man. B. Clifford Neuman Assigned
410 TCP decladebug DECLadebug Remote Debug Protocol Hewlett Packard Assigned
410 UDP decladebug DECLadebug Remote Debug Protocol Hewlett Packard Assigned
411 TCP rmt Remote MT Protocol Peter Eriksson Assigned
411 UDP rmt Remote MT Protocol Peter Eriksson Assigned
412 TCP synoptics-trap Trap Convention Port Illan Raab Assigned
412 UDP synoptics-trap Trap Convention Port Illan Raab Assigned
413 TCP smsp Storage Management Services Protocol Murthy Srinivas Assigned
413 UDP smsp Storage Management Services Protocol Murthy Srinivas Assigned
414 TCP infoseek InfoSeek Steve Kirsch Assigned
414 UDP infoseek InfoSeek Steve Kirsch Assigned
415 TCP bnet BNet Jim Mertz Assigned
415 UDP bnet BNet Jim Mertz Assigned
416 TCP silverplatter Silverplatter Peter Ciuffetti Assigned
416 UDP silverplatter Silverplatter Peter Ciuffetti Assigned
417 TCP onmux Onmux Stephen Hanna Assigned
417 UDP onmux Onmux Stephen Hanna Assigned
418 TCP hyper-g Hyper-G Frank Kappe Assigned
418 UDP hyper-g Hyper-G Frank Kappe Assigned
419 TCP ariel1 Ariel 1 Joel Karafin Assigned
419 UDP ariel1 Ariel 1 Joel Karafin Assigned
420 TCP smpte SMPTE Si Becker Assigned
420 UDP smpte SMPTE Si Becker Assigned
421 TCP ariel2 Ariel 2 Assigned
421 UDP ariel2 Ariel 2 Assigned
422 TCP ariel3 Ariel 3 Joel Karafin Assigned
422 UDP ariel3 Ariel 3 Joel Karafin Assigned
423 TCP opc-job-start IBM Operations Planning and Control Start Assigned
423 UDP opc-job-start IBM Operations Planning and Control Start Assigned
424 TCP opc-job-track IBM Operations Planning and Control Track Conny Larsson Assigned
424 UDP opc-job-track IBM Operations Planning and Control Track Conny Larsson Assigned
425 TCP icad-el ICAD Larry Stone Assigned
425 UDP icad-el ICAD Larry Stone Assigned
426 TCP smartsdp smartsdp Marie-Pierre Belanger 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 ↗