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
1076 UDP dab-sti-c DAB STI-C World DAB Assigned
1077 TCP imgames IMGames Jean A. Ames Assigned
1077 UDP imgames IMGames Jean A. Ames Assigned
1078 TCP avocent-proxy Avocent Proxy Protocol Steven W. Clark Assigned
1078 UDP avocent-proxy Avocent Proxy Protocol Steven W. Clark Assigned
1079 TCP asprovatalk ASPROVATalk Chiew Farn Chung Assigned
1079 UDP asprovatalk ASPROVATalk Chiew Farn Chung Assigned
1080 TCP socks Socks Ying-Da Lee Assigned
1080 UDP socks Socks Ying-Da Lee Assigned
1081 TCP pvuniwien PVUNIWIEN Peter Lipp Assigned
1081 UDP pvuniwien PVUNIWIEN Peter Lipp Assigned
1082 TCP amt-esd-prot AMT-ESD-PROT AMTEC S.p.A Assigned
1082 UDP amt-esd-prot AMT-ESD-PROT AMTEC S.p.A Assigned
1083 TCP ansoft-lm-1 Anasoft License Manager Assigned
1083 UDP ansoft-lm-1 Anasoft License Manager Assigned
1084 TCP ansoft-lm-2 Anasoft License Manager Assigned
1084 UDP ansoft-lm-2 Anasoft License Manager Assigned
1085 TCP webobjects Web Objects Andy Belk Assigned
1085 UDP webobjects Web Objects Andy Belk Assigned
1086 TCP cplscrambler-lg CPL Scrambler Logging Assigned
1086 UDP cplscrambler-lg CPL Scrambler Logging Assigned
1087 TCP cplscrambler-in CPL Scrambler Internal Assigned
1087 UDP cplscrambler-in CPL Scrambler Internal Assigned
1088 TCP cplscrambler-al CPL Scrambler Alarm Log Richard Corn Assigned
1088 UDP cplscrambler-al CPL Scrambler Alarm Log Richard Corn Assigned
1089 TCP ff-annunc FF Annunciation Assigned
1089 UDP ff-annunc FF Annunciation Assigned
1090 TCP ff-fms FF Fieldbus Message Specification Assigned
1090 UDP ff-fms FF Fieldbus Message Specification Assigned
1091 TCP ff-sm FF System Management Fieldbus Foundation Assigned
1091 UDP ff-sm FF System Management Fieldbus Foundation Assigned
1092 TCP obrpd Open Business Reporting Protocol William Randolph Royere III Assigned
1092 UDP obrpd Open Business Reporting Protocol William Randolph Royere III Assigned
1093 TCP proofd PROOFD Assigned
1093 UDP proofd PROOFD Assigned
1094 TCP rootd ROOTD Fons Rademakers Assigned
1094 UDP rootd ROOTD Fons Rademakers Assigned
1095 TCP nicelink NICELink Jordi Lisbona Assigned
1095 UDP nicelink NICELink Jordi Lisbona Assigned
1096 TCP cnrprotocol Common Name Resolution Protocol Michael Mealling Assigned
1096 UDP cnrprotocol Common Name Resolution Protocol Michael Mealling Assigned
1097 TCP sunclustermgr Sun Cluster Manager Ashit Patel Assigned
1097 UDP sunclustermgr Sun Cluster Manager Ashit Patel Assigned
1098 TCP rmiactivation RMI Activation Assigned
1098 UDP rmiactivation RMI Activation Assigned
1099 TCP rmiregistry RMI Registry Mark Hodapp Assigned
1099 UDP rmiregistry RMI Registry Mark Hodapp Assigned
1100 TCP mctp MCTP Vitaly Revsin Assigned
1100 UDP mctp MCTP Vitaly Revsin Assigned
1101 TCP pt2-discover PT2-DISCOVER Ralph Kammerlander 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 ↗