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
1961 TCP bts-appserver BTS APPSERVER Carl Obsorn Assigned
1961 UDP bts-appserver BTS APPSERVER Carl Obsorn Assigned
1962 TCP biap-mp BIAP-MP Louis Slothouber Assigned
1962 UDP biap-mp BIAP-MP Louis Slothouber Assigned
1963 TCP webmachine WebMachine Tim Jowers Assigned
1963 UDP webmachine WebMachine Tim Jowers Assigned
1964 TCP solid-e-engine SOLID E ENGINE Ari Valtanen Assigned
1964 UDP solid-e-engine SOLID E ENGINE Ari Valtanen Assigned
1965 TCP tivoli-npm Tivoli NPM Ivana Cuozzo Assigned
1965 UDP tivoli-npm Tivoli NPM Ivana Cuozzo Assigned
1966 TCP slush Slush Damien Miller Assigned
1966 UDP slush Slush Damien Miller Assigned
1967 TCP sns-quote SNS Quote Robert Ellman Assigned
1967 UDP sns-quote SNS Quote Robert Ellman Assigned
1968 TCP lipsinc LIPSinc Assigned
1968 UDP lipsinc LIPSinc Assigned
1969 TCP lipsinc1 LIPSinc 1 Robert Armington Assigned
1969 UDP lipsinc1 LIPSinc 1 Robert Armington Assigned
1970 TCP netop-rc NetOp Remote Control Assigned
1970 UDP netop-rc NetOp Remote Control Assigned
1971 TCP netop-school NetOp School NetOp Technical Support Assigned
1971 UDP netop-school NetOp School NetOp Technical Support Assigned
1972 TCP intersys-cache Cache Mark Hanson Assigned
1972 UDP intersys-cache Cache Mark Hanson Assigned
1973 TCP dlsrap Data Link Switching Remote Access Protocol Steve T. Chiang Assigned
1973 UDP dlsrap Data Link Switching Remote Access Protocol Steve T. Chiang Assigned
1974 TCP drp DRP Richard Alan Johnson Assigned
1974 UDP drp DRP Richard Alan Johnson Assigned
1975 TCP tcoflashagent TCO Flash Agent Assigned
1975 UDP tcoflashagent TCO Flash Agent Assigned
1976 TCP tcoregagent TCO Reg Agent Assigned
1976 UDP tcoregagent TCO Reg Agent Assigned
1977 TCP tcoaddressbook TCO Address Book Allan Panitch Assigned
1977 UDP tcoaddressbook TCO Address Book Allan Panitch Assigned
1978 TCP unisql UniSQL Assigned
1978 UDP unisql UniSQL Assigned
1979 TCP unisql-java UniSQL Java Keith Yarbrough Assigned
1979 UDP unisql-java UniSQL Java Keith Yarbrough Assigned
1980 TCP panquest-xact PanQuest XACT Chris Vertonghen Assigned
1980 UDP panquest-xact PanQuest XACT Chris Vertonghen Assigned
1981 TCP p2pq p2pQ Warren Alexander Assigned
1981 UDP p2pq p2pQ Warren Alexander Assigned
1982 TCP estamp Evidentiary Timestamp Todd Glassey Assigned
1982 UDP estamp Evidentiary Timestamp Todd Glassey Assigned
1983 TCP lhtp Loophole Test Protocol Kade Hansson Assigned
1983 UDP lhtp Loophole Test Protocol Kade Hansson Assigned
1984 TCP bb BB Sean MacGuire Assigned
1984 UDP bb BB Sean MacGuire Assigned
1985 TCP hsrp Hot Standby Router Protocol [RFC2281] Assigned
1985 UDP hsrp Hot Standby Router Protocol [RFC2281] 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 ↗