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
261 UDP nsiiops IIOP Name Service over TLS/SSL Jeff Stewart Assigned
262 TCP arcisdms Arcisdms Russell Crook Assigned
262 UDP arcisdms Arcisdms Russell Crook Assigned
263 TCP hdap HDAP Troy Gau Assigned
263 UDP hdap HDAP Troy Gau Assigned
264 TCP bgmp BGMP Dave Thaler Assigned
264 UDP bgmp BGMP Dave Thaler Assigned
265 TCP x-bone-ctl X-Bone CTL Joe Touch Assigned
265 UDP x-bone-ctl X-Bone CTL Joe Touch Assigned
266 TCP sst SCSI on ST Donald D. Woelz Assigned
266 UDP sst SCSI on ST Donald D. Woelz Assigned
267 TCP td-service Tobit David Service Layer Assigned
267 UDP td-service Tobit David Service Layer Assigned
268 TCP td-replica Tobit David Replica Franz-Josef Leuders Assigned
268 UDP td-replica Tobit David Replica Franz-Josef Leuders Assigned
269 TCP manet MANET Protocols [RFC5498] Assigned
269 UDP manet MANET Protocols [RFC5498] Assigned
270 TCP Reserved Reserved
270 UDP gist Q-mode encapsulation for GIST messages [RFC5971] Assigned
271 TCP pt-tls IETF Network Endpoint Assessment (NEA) Posture Transport Protocol over TLS (PT-TLS) IESG 2012-07-31 [RFC6876] Assigned
271 UDP Reserved Reserved
272-279 Not specified Unassigned Unassigned
280 TCP http-mgmt http-mgmt Adrian Pell Assigned
280 UDP http-mgmt http-mgmt Adrian Pell Assigned
281 TCP personal-link Personal Link Dan Cummings Assigned
281 UDP personal-link Personal Link Dan Cummings Assigned
282 TCP cableport-ax Cable Port A/X Craig Langfahl Assigned
282 UDP cableport-ax Cable Port A/X Craig Langfahl Assigned
283 TCP rescap rescap Paul Hoffman Assigned
283 UDP rescap rescap Paul Hoffman Assigned
284 TCP corerjd corerjd Chris Thornhill Assigned
284 UDP corerjd corerjd Chris Thornhill Assigned
285 Not specified Unassigned Unassigned
286 TCP fxp FXP Communication James Darnall Assigned
286 UDP fxp FXP Communication James Darnall Assigned
287 TCP k-block K-BLOCK Simon P Jackson Assigned
287 UDP k-block K-BLOCK Simon P Jackson Assigned
288-299 Not specified Unassigned Unassigned
300 TCP tacacss TLS Secure Login Host Protocol (TACACSS) IESG 2025-07-15 [RFC9887] Assigned
300 UDP Reserved Reserved
301-307 Not specified Unassigned Unassigned
308 TCP novastorbakcup Novastor Backup Brian Dickman Assigned
308 UDP novastorbakcup Novastor Backup Brian Dickman Assigned
309 TCP entrusttime EntrustTime Peter Whittaker Assigned
309 UDP entrusttime EntrustTime Peter Whittaker Assigned
310 TCP bhmds bhmds John Kelly Assigned
310 UDP bhmds bhmds John Kelly Assigned
311 TCP asip-webadmin AppleShare IP WebAdmin Ann Huang Assigned
311 UDP asip-webadmin AppleShare IP WebAdmin Ann Huang Assigned
312 TCP vslmp VSLMP Gerben Wierda 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 ↗