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
2550 UDP ads ADS Michael O'Connor Assigned
2551 TCP isg-uda-server ISG UDA Server Dror Harari Assigned
2551 UDP isg-uda-server ISG UDA Server Dror Harari Assigned
2552 TCP call-logging Call Logging Dean Webb Assigned
2552 UDP call-logging Call Logging Dean Webb Assigned
2553 TCP efidiningport efidiningport Lynn Carter Assigned
2553 UDP efidiningport efidiningport Lynn Carter Assigned
2554 TCP vcnet-link-v10 VCnet-Link v10 Csaba Mate Assigned
2554 UDP vcnet-link-v10 VCnet-Link v10 Csaba Mate Assigned
2555 TCP compaq-wcp Compaq WCP Ferruccio Barletta Assigned
2555 UDP compaq-wcp Compaq WCP Ferruccio Barletta Assigned
2556 TCP nicetec-nmsvc nicetec-nmsvc Assigned
2556 UDP nicetec-nmsvc nicetec-nmsvc Assigned
2557 TCP nicetec-mgmt nicetec-mgmt Joerg Paulus Assigned
2557 UDP nicetec-mgmt nicetec-mgmt Joerg Paulus Assigned
2558 TCP pclemultimedia PCLE Multi Media Jacob Gsoedl Assigned
2558 UDP pclemultimedia PCLE Multi Media Jacob Gsoedl Assigned
2559 TCP lstp LSTP Waiki Wright Assigned
2559 UDP lstp LSTP Waiki Wright Assigned
2560 TCP labrat labrat John Harvey Assigned
2560 UDP labrat labrat John Harvey Assigned
2561 TCP mosaixcc MosaixCC Steven Frare Assigned
2561 UDP mosaixcc MosaixCC Steven Frare Assigned
2562 TCP delibo Delibo NovaWiz LTD Assigned
2562 UDP delibo Delibo NovaWiz LTD Assigned
2563 TCP cti-redwood CTI Redwood Songwon Chi Assigned
2563 UDP cti-redwood CTI Redwood Songwon Chi Assigned
2564 TCP hp-3000-telnet HP 3000 NS/VT block mode telnet Assigned
2564 UDP hp-3000-telnet HP 3000 NS/VT block mode telnet Assigned
2565 TCP coord-svr Coordinator Server Richard Steiger Assigned
2565 UDP coord-svr Coordinator Server Richard Steiger Assigned
2566 TCP pcs-pcw pcs-pcw W. Jordan Fitzhugh Assigned
2566 UDP pcs-pcw pcs-pcw W. Jordan Fitzhugh Assigned
2567 TCP clp Cisco Line Protocol Susan Hinrichs Assigned
2567 UDP clp Cisco Line Protocol Susan Hinrichs Assigned
2568 TCP spamtrap SPAM TRAP Charles Bennett 2008-08-29 Assigned
2568 UDP spamtrap SPAM TRAP Charles Bennett 2008-08-29 Assigned
2569 TCP sonuscallsig Sonus Call Signal Mark Garti Assigned
2569 UDP sonuscallsig Sonus Call Signal Mark Garti Assigned
2570 TCP hs-port HS Port Uri Doron Assigned
2570 UDP hs-port HS Port Uri Doron Assigned
2571 TCP cecsvc CECSVC Roger Pao Assigned
2571 UDP cecsvc CECSVC Roger Pao Assigned
2572 TCP ibp IBP Jonathan Downes Assigned
2572 UDP ibp IBP Jonathan Downes Assigned
2573 TCP trustestablish Trust Establish Yosi Mass Assigned
2573 UDP trustestablish Trust Establish Yosi Mass Assigned
2574 TCP blockade-bpsp Blockade BPSP VP - Research & Development Assigned
2574 UDP blockade-bpsp Blockade BPSP VP - Research & Development Assigned
2575 TCP hl7 HL7 Tim Jacobs 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 ↗