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
6483 TCP SunVTS-RMI SunVTS RMI Sumit Arora 2007-06 Assigned
6483 UDP SunVTS-RMI SunVTS RMI Sumit Arora 2007-06 Assigned
6484 TCP sun-sr-jms Service Registry Default JMS Domain Paul Sterk 2006-03 Assigned
6484 UDP sun-sr-jms Service Registry Default JMS Domain Paul Sterk 2006-03 Assigned
6485 TCP sun-sr-iiop Service Registry Default IIOP Domain Paul Sterk 2006-03 Assigned
6485 UDP sun-sr-iiop Service Registry Default IIOP Domain Paul Sterk 2006-03 Assigned
6486 TCP sun-sr-iiops Service Registry Default IIOPS Domain Paul Sterk 2006-03 Assigned
6486 UDP sun-sr-iiops Service Registry Default IIOPS Domain Paul Sterk 2006-03 Assigned
6487 TCP sun-sr-iiop-aut Service Registry Default IIOPAuth Domain Paul Sterk 2006-03 Assigned
6487 UDP sun-sr-iiop-aut Service Registry Default IIOPAuth Domain Paul Sterk 2006-03 Assigned
6488 TCP sun-sr-jmx Service Registry Default JMX Domain Paul Sterk 2006-03 Assigned
6488 UDP sun-sr-jmx Service Registry Default JMX Domain Paul Sterk 2006-03 Assigned
6489 TCP sun-sr-admin Service Registry Default Admin Domain Paul Sterk 2006-03 Assigned
6489 UDP sun-sr-admin Service Registry Default Admin Domain Paul Sterk 2006-03 Assigned
6490-6499 Not specified Unassigned Unassigned
6500 TCP boks BoKS Master Magnus Nystrom Assigned
6500 UDP boks BoKS Master Magnus Nystrom Assigned
6501 TCP boks-servc BoKS Servc IANA assigned this well-formed service name as a replacement for "boks_servc". Magnus Nystrom Assigned
6501 TCP boks_servc BoKS Servc Magnus Nystrom Assigned
6501 UDP boks-servc BoKS Servc IANA assigned this well-formed service name as a replacement for "boks_servc". Magnus Nystrom Assigned
6501 UDP boks_servc BoKS Servc Magnus Nystrom Assigned
6502 TCP boks-servm BoKS Servm IANA assigned this well-formed service name as a replacement for "boks_servm". Magnus Nystrom Assigned
6502 TCP boks_servm BoKS Servm Magnus Nystrom Assigned
6502 UDP boks-servm BoKS Servm IANA assigned this well-formed service name as a replacement for "boks_servm". Magnus Nystrom Assigned
6502 UDP boks_servm BoKS Servm Magnus Nystrom Assigned
6503 TCP boks-clntd BoKS Clntd IANA assigned this well-formed service name as a replacement for "boks_clntd". Magnus Nystrom Assigned
6503 TCP boks_clntd BoKS Clntd Magnus Nystrom Assigned
6503 UDP boks-clntd BoKS Clntd IANA assigned this well-formed service name as a replacement for "boks_clntd". Magnus Nystrom Assigned
6503 UDP boks_clntd BoKS Clntd Magnus Nystrom Assigned
6504 Not specified Unassigned Unassigned
6505 TCP badm-priv BoKS Admin Private Port IANA assigned this well-formed service name as a replacement for "badm_priv". Magnus Nystrom Assigned
6505 TCP badm_priv BoKS Admin Private Port Magnus Nystrom Assigned
6505 UDP badm-priv BoKS Admin Private Port IANA assigned this well-formed service name as a replacement for "badm_priv". Magnus Nystrom Assigned
6505 UDP badm_priv BoKS Admin Private Port Magnus Nystrom Assigned
6506 TCP badm-pub BoKS Admin Public Port IANA assigned this well-formed service name as a replacement for "badm_pub". Magnus Nystrom Assigned
6506 TCP badm_pub BoKS Admin Public Port Magnus Nystrom Assigned
6506 UDP badm-pub BoKS Admin Public Port IANA assigned this well-formed service name as a replacement for "badm_pub". Magnus Nystrom Assigned
6506 UDP badm_pub BoKS Admin Public Port Magnus Nystrom Assigned
6507 TCP bdir-priv BoKS Dir Server, Private Port IANA assigned this well-formed service name as a replacement for "bdir_priv". Magnus Nystrom Assigned
6507 TCP bdir_priv BoKS Dir Server, Private Port Magnus Nystrom Assigned
6507 UDP bdir-priv BoKS Dir Server, Private Port IANA assigned this well-formed service name as a replacement for "bdir_priv". Magnus Nystrom Assigned
6507 UDP bdir_priv BoKS Dir Server, Private Port Magnus Nystrom Assigned
6508 TCP bdir-pub BoKS Dir Server, Public Port IANA assigned this well-formed service name as a replacement for "bdir_pub". Magnus Nystrom Assigned
6508 TCP bdir_pub BoKS Dir Server, Public Port Magnus Nystrom Assigned
6508 UDP bdir-pub BoKS Dir Server, Public Port IANA assigned this well-formed service name as a replacement for "bdir_pub". Magnus Nystrom Assigned
6508 UDP bdir_pub BoKS Dir Server, Public Port Magnus Nystrom Assigned
6509 TCP mgcs-mfp-port MGCS-MFP Port Minoru Ozaki Assigned
6509 UDP mgcs-mfp-port MGCS-MFP Port Minoru Ozaki Assigned
6510 TCP mcer-port MCER Port Portnoy Boxman Assigned
6510 UDP mcer-port MCER Port Portnoy Boxman 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 ↗