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
2575 UDP hl7 HL7 Tim Jacobs Assigned
2576 TCP tclprodebugger TCL Pro Debugger Assigned
2576 UDP tclprodebugger TCL Pro Debugger Assigned
2577 TCP scipticslsrvr Scriptics Lsrvr Brent Welch Assigned
2577 UDP scipticslsrvr Scriptics Lsrvr Brent Welch Assigned
2578 TCP rvs-isdn-dcp RVS ISDN DCP Michael Zirpel Assigned
2578 UDP rvs-isdn-dcp RVS ISDN DCP Michael Zirpel Assigned
2579 TCP mpfoncl mpfoncl Itaru Kimura Assigned
2579 UDP mpfoncl mpfoncl Itaru Kimura Assigned
2580 TCP tributary Tributary Louis Lu Assigned
2580 UDP tributary Tributary Louis Lu Assigned
2581 TCP argis-te ARGIS TE Assigned
2581 UDP argis-te ARGIS TE Assigned
2582 TCP argis-ds ARGIS DS John Legh-Page Assigned
2582 UDP argis-ds ARGIS DS John Legh-Page Assigned
2583 TCP mon MON Jim Trocki Assigned
2583 UDP mon MON Jim Trocki Assigned
2584 TCP cyaserv cyaserv Morgan Jones Assigned
2584 UDP cyaserv cyaserv Morgan Jones Assigned
2585 TCP netx-server NETX Server Assigned
2585 UDP netx-server NETX Server Assigned
2586 TCP netx-agent NETX Agent Brett Dolecheck Assigned
2586 UDP netx-agent NETX Agent Brett Dolecheck Assigned
2587 TCP masc MASC Pavlin Ivanov Radoslavov Assigned
2587 UDP masc MASC Pavlin Ivanov Radoslavov Assigned
2588 TCP privilege Privilege Gil Hecht Assigned
2588 UDP privilege Privilege Gil Hecht Assigned
2589 TCP quartus-tcl quartus tcl Subroto Datta Assigned
2589 UDP quartus-tcl quartus tcl Subroto Datta Assigned
2590 TCP idotdist idotdist Jason Hunter Assigned
2590 UDP idotdist idotdist Jason Hunter Assigned
2591 TCP maytagshuffle Maytag Shuffle Ken Ksiazek Assigned
2591 UDP maytagshuffle Maytag Shuffle Ken Ksiazek Assigned
2592 TCP netrek netrek Al Guetzlaff Assigned
2592 UDP netrek netrek Al Guetzlaff Assigned
2593 TCP mns-mail MNS Mail Notice Service Rumiko Kikuta Assigned
2593 UDP mns-mail MNS Mail Notice Service Rumiko Kikuta Assigned
2594 TCP dts Data Base Server Andreas Roene Assigned
2594 UDP dts Data Base Server Andreas Roene Assigned
2595 TCP worldfusion1 World Fusion 1 Assigned
2595 UDP worldfusion1 World Fusion 1 Assigned
2596 TCP worldfusion2 World Fusion 2 World Fusion Assigned
2596 UDP worldfusion2 World Fusion 2 World Fusion Assigned
2597 TCP homesteadglory Homestead Glory John Tokash Assigned
2597 UDP homesteadglory Homestead Glory John Tokash Assigned
2598 TCP citriximaclient Citrix MA Client Myk Willis Assigned
2598 UDP citriximaclient Citrix MA Client Myk Willis Assigned
2599 TCP snapd Snap Discovery Kevin Osborn Assigned
2599 UDP snapd Snap Discovery Kevin Osborn Assigned
2600 TCP hpstgmgr HPSTGMGR Kevin Collins 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 ↗