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
2258 TCP rcts Rotorcraft Communications Test System Terry Eldridge 2006-08 Assigned
2258 UDP rcts Rotorcraft Communications Test System Terry Eldridge 2006-08 Assigned
2259 TCP bid-serv BIF identifiers resolution service Li Zhiping (CAICT) 2023-03-06 Assigned
2259 UDP bid-serv BIF identifiers resolution service Li Zhiping (CAICT) 2023-03-06 Assigned
2260 TCP apc-2260 APC 2260 American Power Conversion 2002-02 Assigned
2260 UDP apc-2260 APC 2260 American Power Conversion 2002-02 Assigned
2261 TCP comotionmaster CoMotion Master Server Assigned
2261 UDP comotionmaster CoMotion Master Server Assigned
2262 TCP comotionback CoMotion Backup Server Friedman Wagner-Dobler 2005-09 Assigned
2262 UDP comotionback CoMotion Backup Server Friedman Wagner-Dobler 2005-09 Assigned
2263 TCP ecwcfg ECweb Configuration Service Anders Hjelm 2006-03 Assigned
2263 UDP ecwcfg ECweb Configuration Service Anders Hjelm 2006-03 Assigned
2264 TCP apx500api-1 Audio Precision Apx500 API Port 1 Assigned
2264 UDP apx500api-1 Audio Precision Apx500 API Port 1 Assigned
2265 TCP apx500api-2 Audio Precision Apx500 API Port 2 Robert Wright, Founder and Principal Engineer (Audio Precision Inc.) Assigned
2265 UDP apx500api-2 Audio Precision Apx500 API Port 2 Robert Wright, Founder and Principal Engineer (Audio Precision Inc.) Assigned
2266 TCP mfserver M-Files Server Samppa Lahtinen 2004-06 Assigned
2266 UDP mfserver M-files Server Samppa Lahtinen 2004-06 Assigned
2267 TCP ontobroker OntoBroker Dr. Michael Erdmann 2004-12 Assigned
2267 UDP ontobroker OntoBroker Dr. Michael Erdmann 2004-12 Assigned
2268 TCP amt AMT IESG 2004-12 [RFC7450] Assigned
2268 UDP amt AMT IESG 2004-12 [RFC7450] Assigned
2269 TCP mikey MIKEY Karl Norrman 2004-12 Assigned
2269 UDP mikey MIKEY Karl Norrman 2004-12 Assigned
2270 TCP starschool starSchool Adam Ernst 2004-12 Assigned
2270 UDP starschool starSchool Adam Ernst 2004-12 Assigned
2271 TCP mmcals Secure Meeting Maker Scheduling Assigned
2271 UDP mmcals Secure Meeting Maker Scheduling Assigned
2272 TCP mmcal Meeting Maker Scheduling Andrew H Derbyshire 2004-12 Assigned
2272 UDP mmcal Meeting Maker Scheduling Andrew H Derbyshire 2004-12 Assigned
2273 TCP mysql-im MySQL Instance Manager Petr Chardin 2004-12 Assigned
2273 UDP mysql-im MySQL Instance Manager Petr Chardin 2004-12 Assigned
2274 TCP pcttunnell PCTTunneller ProControl Technology AB 2004-12 Assigned
2274 UDP pcttunnell PCTTunneller ProControl Technology AB 2004-12 Assigned
2275 TCP ibridge-data iBridge Conferencing Assigned
2275 UDP ibridge-data iBridge Conferencing Assigned
2276 TCP ibridge-mgmt iBridge Management Patrick Fisher 2004-12 Assigned
2276 UDP ibridge-mgmt iBridge Management Patrick Fisher 2004-12 Assigned
2277 TCP bluectrlproxy Bt device control proxy Mark de Rooi 2004-12 Assigned
2277 UDP bluectrlproxy Bt device control proxy Mark de Rooi 2004-12 Assigned
2278 TCP s3db Simple Stacked Sequences Database David Brandon 2006-08 Assigned
2278 UDP s3db Simple Stacked Sequences Database David Brandon 2006-08 Assigned
2279 TCP xmquery xmquery Niels Christiansen Assigned
2279 UDP xmquery xmquery Niels Christiansen Assigned
2280 TCP lnvpoller LNVPOLLER Assigned
2280 UDP lnvpoller LNVPOLLER Assigned
2281 TCP lnvconsole LNVCONSOLE Assigned
2281 UDP lnvconsole LNVCONSOLE Assigned
2282 TCP lnvalarm LNVALARM Assigned
2282 UDP lnvalarm LNVALARM 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 ↗