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
1662 TCP netview-aix-2 netview-aix-2 Assigned
1662 UDP netview-aix-2 netview-aix-2 Assigned
1663 TCP netview-aix-3 netview-aix-3 Assigned
1663 UDP netview-aix-3 netview-aix-3 Assigned
1664 TCP netview-aix-4 netview-aix-4 Assigned
1664 UDP netview-aix-4 netview-aix-4 Assigned
1665 TCP netview-aix-5 netview-aix-5 Assigned
1665 UDP netview-aix-5 netview-aix-5 Assigned
1666 TCP netview-aix-6 netview-aix-6 Assigned
1666 UDP netview-aix-6 netview-aix-6 Assigned
1667 TCP netview-aix-7 netview-aix-7 Assigned
1667 UDP netview-aix-7 netview-aix-7 Assigned
1668 TCP netview-aix-8 netview-aix-8 Assigned
1668 UDP netview-aix-8 netview-aix-8 Assigned
1669 TCP netview-aix-9 netview-aix-9 Assigned
1669 UDP netview-aix-9 netview-aix-9 Assigned
1670 TCP netview-aix-10 netview-aix-10 Assigned
1670 UDP netview-aix-10 netview-aix-10 Assigned
1671 TCP netview-aix-11 netview-aix-11 Assigned
1671 UDP netview-aix-11 netview-aix-11 Assigned
1672 TCP netview-aix-12 netview-aix-12 Martha Crisson Assigned
1672 UDP netview-aix-12 netview-aix-12 Martha Crisson Assigned
1673 TCP proshare-mc-1 Intel Proshare Multicast Assigned
1673 UDP proshare-mc-1 Intel Proshare Multicast Assigned
1674 TCP proshare-mc-2 Intel Proshare Multicast Mark Lewis Assigned
1674 UDP proshare-mc-2 Intel Proshare Multicast Mark Lewis Assigned
1675 TCP pdp Pacific Data Products Gary Morton Assigned
1675 UDP pdp Pacific Data Products Gary Morton Assigned
1676 TCP netcomm1 netcomm1 Assigned
1676 UDP netcomm2 netcomm2 Bulent Kasman Assigned
1677 TCP groupwise groupwise Brent Bradshaw Assigned
1677 UDP groupwise groupwise Brent Bradshaw Assigned
1678 TCP prolink prolink Brian Abramson Assigned
1678 UDP prolink prolink Brian Abramson Assigned
1679 TCP darcorp-lm darcorp-lm DARcorp Assigned
1679 UDP darcorp-lm darcorp-lm DARcorp Assigned
1680 TCP microcom-sbp microcom-sbp Boris B. Maiden Assigned
1680 UDP microcom-sbp microcom-sbp Boris B. Maiden Assigned
1681 TCP sd-elmd sd-elmd Bryan Otey Assigned
1681 UDP sd-elmd sd-elmd Bryan Otey Assigned
1682 TCP lanyon-lantern lanyon-lantern Robin Lewis Assigned
1682 UDP lanyon-lantern lanyon-lantern Robin Lewis Assigned
1683 TCP ncpm-hip ncpm-hip Ken Hearn Assigned
1683 UDP ncpm-hip ncpm-hip Ken Hearn Assigned
1684 TCP snaresecure SnareSecure Marty Batchelder Assigned
1684 UDP snaresecure SnareSecure Marty Batchelder Assigned
1685 TCP n2nremote n2nremote Kin Chan Assigned
1685 UDP n2nremote n2nremote Kin Chan Assigned
1686 TCP cvmon cvmon Carol Ann Krug Assigned
1686 UDP cvmon cvmon Carol Ann Krug 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 ↗