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
1324 TCP delta-mcp delta-mcp Quinton Tormanen Assigned
1324 UDP delta-mcp delta-mcp Quinton Tormanen Assigned
1325 TCP dx-instrument Thermo Fisher Scientific Instrumentation (Formally Dionex) Thermo Fisher Scientific Assigned
1325 UDP dx-instrument Thermo Fisher Scientific Instrumentation (Formally Dionex) Thermo Fisher Scientific Assigned
1326 TCP wimsic WIMSIC James Brown Assigned
1326 UDP wimsic WIMSIC James Brown Assigned
1327 TCP ultrex Ultrex Tim Walsh Assigned
1327 UDP ultrex Ultrex Tim Walsh Assigned
1328 TCP ewall EWALL Jeff Busma Assigned
1328 UDP ewall EWALL Jeff Busma Assigned
1329 TCP netdb-export netdb-export Konstantinos Kostis Assigned
1329 UDP netdb-export netdb-export Konstantinos Kostis Assigned
1330 TCP streetperfect StreetPerfect Michael R. Young Assigned
1330 UDP streetperfect StreetPerfect Michael R. Young Assigned
1331 TCP intersan intersan Barry H. Feild Assigned
1331 UDP intersan intersan Barry H. Feild Assigned
1332 TCP pcia-rxp-b PCIA RXP-B James Dabbs Assigned
1332 UDP pcia-rxp-b PCIA RXP-B James Dabbs Assigned
1333 TCP passwrd-policy Password Policy Tonio Pirotta Assigned
1333 UDP passwrd-policy Password Policy Tonio Pirotta Assigned
1334 TCP writesrv writesrv Marvin Toungate Assigned
1334 UDP writesrv writesrv Marvin Toungate Assigned
1335 TCP digital-notary Digital Notary Protocol Wes Doonan Assigned
1335 UDP digital-notary Digital Notary Protocol Wes Doonan Assigned
1336 TCP ischat Instant Service Chat Mike Clise Assigned
1336 UDP ischat Instant Service Chat Mike Clise Assigned
1337 TCP menandmice-dns menandmice DNS Sigfus Magnusson Assigned
1337 UDP menandmice-dns menandmice DNS Sigfus Magnusson Assigned
1338 TCP wmc-log-svc WMC-log-svr Scott Anderson Assigned
1338 UDP wmc-log-svc WMC-log-svr Scott Anderson Assigned
1339 TCP kjtsiteserver kjtsiteserver Jason Aubain Assigned
1339 UDP kjtsiteserver kjtsiteserver Jason Aubain Assigned
1340 TCP naap NAAP Henry Haverinen Assigned
1340 UDP naap NAAP Henry Haverinen Assigned
1341 TCP qubes QuBES Eric Grange Assigned
1341 UDP qubes QuBES Eric Grange Assigned
1342 TCP esbroker ESBroker Alexander Medvinsky Assigned
1342 UDP esbroker ESBroker Alexander Medvinsky Assigned
1343 TCP re101 re101 Doriano Blengino Assigned
1343 UDP re101 re101 Doriano Blengino Assigned
1344 TCP icap ICAP Jeremy Elson Assigned
1344 UDP icap ICAP Jeremy Elson Assigned
1345 TCP vpjp VPJP Michael Collins Assigned
1345 UDP vpjp VPJP Michael Collins Assigned
1346 TCP alta-ana-lm Alta Analytics License Manager Assigned
1346 UDP alta-ana-lm Alta Analytics License Manager Assigned
1347 TCP bbn-mmc multi media conferencing Assigned
1347 UDP bbn-mmc multi media conferencing Assigned
1348 TCP bbn-mmx multi media conferencing Assigned
1348 UDP bbn-mmx multi media conferencing 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 ↗