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
2308 TCP sdhelp sdhelp Annette Klecha Assigned
2308 UDP sdhelp sdhelp Annette Klecha Assigned
2309 TCP sdserver SD Server Assigned
2309 UDP sdserver SD Server Assigned
2310 TCP sdclient SD Client Jeurgen Broesamle Assigned
2310 UDP sdclient SD Client Jeurgen Broesamle Assigned
2311 TCP messageservice Message Service Assigned
2311 UDP messageservice Message Service Assigned
2312 TCP wanscaler WANScaler Communication Service Allen Samuels 2006-11 Assigned
2312 UDP wanscaler WANScaler Communication Service Allen Samuels 2006-11 Assigned
2313 TCP iapp IAPP (Inter Access Point Protocol) Henri Moelard Assigned
2313 UDP iapp IAPP (Inter Access Point Protocol) Henri Moelard Assigned
2314 TCP cr-websystems CR WebSystems Robin Giese Assigned
2314 UDP cr-websystems CR WebSystems Robin Giese Assigned
2315 TCP precise-sft Precise Sft. Michael Landwehr Assigned
2315 UDP precise-sft Precise Sft. Michael Landwehr Assigned
2316 TCP sent-lm SENT License Manager Pisharath Krishnan Assigned
2316 UDP sent-lm SENT License Manager Pisharath Krishnan Assigned
2317 TCP attachmate-g32 Attachmate G32 Bryce Bhatnagar Assigned
2317 UDP attachmate-g32 Attachmate G32 Bryce Bhatnagar Assigned
2318 TCP cadencecontrol Cadence Control Buck Caldwell Assigned
2318 UDP cadencecontrol Cadence Control Buck Caldwell Assigned
2319 TCP infolibria InfoLibria Chris Chiotasso Assigned
2319 UDP infolibria InfoLibria Chris Chiotasso Assigned
2320 TCP siebel-ns Siebel NS Gilberto Arnaiz Assigned
2320 UDP siebel-ns Siebel NS Gilberto Arnaiz Assigned
2321 TCP rdlap RDLAP Robert Wiebe Assigned
2321 UDP rdlap RDLAP Robert Wiebe Assigned
2322 TCP ofsd ofsd Assigned
2322 UDP ofsd ofsd Assigned
2323 TCP 3d-nfsd 3d-nfsd Mike Sherrill Assigned
2323 UDP 3d-nfsd 3d-nfsd Mike Sherrill Assigned
2324 TCP cosmocall Cosmocall Steve Dellutri Assigned
2324 UDP cosmocall Cosmocall Steve Dellutri Assigned
2325 TCP ansysli ANSYS Licensing Interconnect Suzanne Lorrin Assigned
2325 UDP ansysli ANSYS Licensing Interconnect Suzanne Lorrin Assigned
2326 TCP idcp IDCP Keisokugiken Corp. Assigned
2326 UDP idcp IDCP Keisokugiken Corp. Assigned
2327 TCP xingcsm xingcsm Dave Spencer Assigned
2327 UDP xingcsm xingcsm Dave Spencer Assigned
2328 TCP netrix-sftm Netrix SFTM Garrett Herschleb Assigned
2328 UDP netrix-sftm Netrix SFTM Garrett Herschleb Assigned
2329 TCP nvd NVD Peter Weyman Assigned
2329 UDP nvd NVD Peter Weyman Assigned
2330 TCP tscchat TSCCHAT Mike Jackson Assigned
2330 UDP tscchat TSCCHAT Mike Jackson Assigned
2331 TCP agentview AGENTVIEW Ram Iyer Assigned
2331 UDP agentview AGENTVIEW Ram Iyer Assigned
2332 TCP rcc-host RCC Host Martin Shoemaker Assigned
2332 UDP rcc-host RCC Host Martin Shoemaker 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 ↗