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
1200 TCP scol SCOL Cryo-Networks Assigned
1200 UDP scol SCOL Cryo-Networks Assigned
1201 TCP nucleus-sand Nucleus Sand Database Server James Marsh Assigned
1201 UDP nucleus-sand Nucleus Sand Database Server James Marsh Assigned
1202 TCP caiccipc caiccipc Vince Re Assigned
1202 UDP caiccipc caiccipc Vince Re Assigned
1203 TCP ssslic-mgr License Validation Assigned
1203 UDP ssslic-mgr License Validation Assigned
1204 TCP ssslog-mgr Log Request Listener Eric Bruno Assigned
1204 UDP ssslog-mgr Log Request Listener Eric Bruno Assigned
1205 TCP accord-mgc Accord-MGC Roni Even Assigned
1205 UDP accord-mgc Accord-MGC Roni Even Assigned
1206 TCP anthony-data Anthony Data Paul Dollemore Assigned
1206 UDP anthony-data Anthony Data Paul Dollemore Assigned
1207 TCP metasage MetaSage Peter Anvelt Assigned
1207 UDP metasage MetaSage Peter Anvelt Assigned
1208 TCP seagull-ais SEAGULL AIS Lee Breisacher Assigned
1208 UDP seagull-ais SEAGULL AIS Lee Breisacher Assigned
1209 TCP ipcd3 IPCD3 Mark Ciskey Assigned
1209 UDP ipcd3 IPCD3 Mark Ciskey Assigned
1210 TCP eoss EOSS Robert Armes Assigned
1210 UDP eoss EOSS Robert Armes Assigned
1211 TCP groove-dpp Groove DPP Ken Moore Assigned
1211 UDP groove-dpp Groove DPP Ken Moore Assigned
1212 TCP lupa lupa Barney Wolff Assigned
1212 UDP lupa lupa Barney Wolff Assigned
1213 TCP mpc-lifenet Medtronic/Physio-Control LIFENET Physio-Control, Inc. Assigned
1213 UDP mpc-lifenet Medtronic/Physio-Control LIFENET Physio-Control, Inc. Assigned
1214 TCP kazaa KAZAA Ahti Heinla Assigned
1214 UDP kazaa KAZAA Ahti Heinla Assigned
1215 TCP scanstat-1 scanSTAT 1.0 William Scheding Assigned
1215 UDP scanstat-1 scanSTAT 1.0 William Scheding Assigned
1216 TCP etebac5 ETEBAC 5 Jean-Louis Barbut Assigned
1216 UDP etebac5 ETEBAC 5 Jean-Louis Barbut Assigned
1217 TCP hpss-ndapi HPSS NonDCE Gateway Michael Gleicher Assigned
1217 UDP hpss-ndapi HPSS NonDCE Gateway Michael Gleicher Assigned
1218 TCP aeroflight-ads AeroFlight-ADs Assigned
1218 UDP aeroflight-ads AeroFlight-ADs Assigned
1219 TCP aeroflight-ret AeroFlight-Ret Eric Johnson Assigned
1219 UDP aeroflight-ret AeroFlight-Ret Eric Johnson Assigned
1220 TCP qt-serveradmin QT SERVER ADMIN Chris LeCroy Assigned
1220 UDP qt-serveradmin QT SERVER ADMIN Chris LeCroy Assigned
1221 TCP sweetware-apps SweetWARE Apps David Dunetz Assigned
1221 UDP sweetware-apps SweetWARE Apps David Dunetz Assigned
1222 TCP nerv SNI R&D network Martin Freiss Assigned
1222 UDP nerv SNI R&D network Martin Freiss Assigned
1223 TCP tgp TrulyGlobal Protocol Gur Kimchi 2008-05-20 Assigned
1223 UDP tgp TrulyGlobal Protocol Gur Kimchi 2008-05-20 Assigned
1224 TCP vpnz VPNz Tom Strack Assigned
1224 UDP vpnz VPNz Tom Strack 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 ↗