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
3284 UDP 4talk 4Talk Tony Bushnell Assigned
3285 TCP plato Plato Jim Battin Assigned
3285 UDP plato Plato Jim Battin Assigned
3286 TCP e-net E-Net Steven Grigsby Assigned
3286 UDP e-net E-Net Steven Grigsby Assigned
3287 TCP directvdata DIRECTVDATA Michael Friedman Assigned
3287 UDP directvdata DIRECTVDATA Michael Friedman Assigned
3288 TCP cops COPS Shai Herzog Assigned
3288 UDP cops COPS Shai Herzog Assigned
3289 TCP enpc ENPC SEIKO EPSON Assigned
3289 UDP enpc ENPC SEIKO EPSON Assigned
3290 TCP caps-lm CAPS LOGISTICS TOOLKIT - LM Joseph Krebs Assigned
3290 UDP caps-lm CAPS LOGISTICS TOOLKIT - LM Joseph Krebs Assigned
3291 TCP sah-lm S A Holditch & Associates - LM Randy Hudgens Assigned
3291 UDP sah-lm S A Holditch & Associates - LM Randy Hudgens Assigned
3292 TCP cart-o-rama Cart O Rama Phillip Dillinger Assigned
3292 UDP cart-o-rama Cart O Rama Phillip Dillinger Assigned
3293 TCP fg-fps fg-fps Assigned
3293 UDP fg-fps fg-fps Assigned
3294 TCP fg-gip fg-gip Jean-Marc Frailong Assigned
3294 UDP fg-gip fg-gip Jean-Marc Frailong Assigned
3295 TCP dyniplookup Dynamic IP Lookup Eugene Osovetsky Assigned
3295 UDP dyniplookup Dynamic IP Lookup Eugene Osovetsky Assigned
3296 TCP rib-slm Rib License Manager Kristean Heisler Assigned
3296 UDP rib-slm Rib License Manager Kristean Heisler Assigned
3297 TCP cytel-lm Cytel License Manager Yogesh P. Gajjar Assigned
3297 UDP cytel-lm Cytel License Manager Yogesh P. Gajjar Assigned
3298 TCP deskview DeskView Manfred Randelzofer Assigned
3298 UDP deskview DeskView Manfred Randelzofer Assigned
3299 TCP pdrncs pdrncs Paul Wissenbach Assigned
3299 UDP pdrncs pdrncs Paul Wissenbach Assigned
3300 TCP ceph Ceph monitor Sage Weil 2015-06-29 Assigned
3300 UDP Reserved Reserved
3301 TCP tarantool Tarantool in-memory computing platform Tarantool 2022-06-10 Assigned
3301 UDP tarantool Tarantool in-memory computing platform Tarantool 2022-06-10 Assigned
3302 TCP mcs-fastmail MCS Fastmail Patti Jo Newsom Assigned
3302 UDP mcs-fastmail MCS Fastmail Patti Jo Newsom Assigned
3303 TCP opsession-clnt OP Session Client Assigned
3303 UDP opsession-clnt OP Session Client Assigned
3304 TCP opsession-srvr OP Session Server Amir Blich Assigned
3304 UDP opsession-srvr OP Session Server Amir Blich Assigned
3305 TCP odette-ftp ODETTE-FTP David Nash [RFC5024] Assigned
3305 UDP odette-ftp ODETTE-FTP David Nash [RFC5024] Assigned
3306 TCP mysql MySQL Monty Assigned
3306 UDP mysql MySQL Monty Assigned
3307 TCP opsession-prxy OP Session Proxy Amir Blich Assigned
3307 UDP opsession-prxy OP Session Proxy Amir Blich Assigned
3308 TCP tns-server TNS Server Assigned
3308 UDP tns-server TNS Server Assigned
3309 TCP tns-adv TNS ADV Jerome Albin 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 ↗