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
1613 TCP netbill-keyrep NetBill Key Repository Assigned
1613 UDP netbill-keyrep NetBill Key Repository Assigned
1614 TCP netbill-cred NetBill Credential Server Assigned
1614 UDP netbill-cred NetBill Credential Server Assigned
1615 TCP netbill-auth NetBill Authorization Server Assigned
1615 UDP netbill-auth NetBill Authorization Server Assigned
1616 TCP netbill-prod NetBill Product Server Marvin Sirbu Assigned
1616 UDP netbill-prod NetBill Product Server Marvin Sirbu Assigned
1617 TCP nimrod-agent Nimrod Inter-Agent Communication Charles Lynn Assigned
1617 UDP nimrod-agent Nimrod Inter-Agent Communication Charles Lynn Assigned
1618 TCP skytelnet skytelnet Byron Jones Assigned
1618 UDP skytelnet skytelnet Byron Jones Assigned
1619 TCP xs-openstorage xs-openstorage XuiS Software Ltd. Assigned
1619 UDP xs-openstorage xs-openstorage XuiS Software Ltd. Assigned
1620 TCP faxportwinport faxportwinport Chris Wells Assigned
1620 UDP faxportwinport faxportwinport Chris Wells Assigned
1621 TCP softdataphone softdataphone Dror Gill Assigned
1621 UDP softdataphone softdataphone Dror Gill Assigned
1622 TCP ontime ontime Keith Rhodes Assigned
1622 UDP ontime ontime Keith Rhodes Assigned
1623 TCP jaleosnd jaleosnd Christian Schormann Assigned
1623 UDP jaleosnd jaleosnd Christian Schormann Assigned
1624 TCP udp-sr-port udp-sr-port Herb Jensen Assigned
1624 UDP udp-sr-port udp-sr-port Herb Jensen Assigned
1625 TCP svs-omagent svs-omagent Alberto Berlen Assigned
1625 UDP svs-omagent svs-omagent Alberto Berlen Assigned
1626 TCP shockwave Shockwave Sarah Allen Assigned
1626 UDP shockwave Shockwave Sarah Allen Assigned
1627 TCP t128-gateway T.128 Gateway Phil May Assigned
1627 UDP t128-gateway T.128 Gateway Phil May Assigned
1628 TCP lontalk-norm LonTalk normal Assigned
1628 UDP lontalk-norm LonTalk normal Assigned
1629 TCP lontalk-urgnt LonTalk urgent Bob Dolin 2008-04-10 Assigned
1629 UDP lontalk-urgnt LonTalk urgent Bob Dolin 2008-04-10 Assigned
1630 TCP oraclenet8cman Oracle Net8 Cman Tong-Ming Lee Assigned
1630 UDP oraclenet8cman Oracle Net8 Cman Tong-Ming Lee Assigned
1631 TCP visitview Visit view Tom Whittaker Assigned
1631 UDP visitview Visit view Tom Whittaker Assigned
1632 TCP pammratc PAMMRATC Assigned
1632 UDP pammratc PAMMRATC Assigned
1633 TCP pammrpc PAMMRPC John Britton Assigned
1633 UDP pammrpc PAMMRPC John Britton Assigned
1634 TCP loaprobe Log On America Probe James Tavares (Log On America) Assigned
1634 UDP loaprobe Log On America Probe James Tavares (Log On America) Assigned
1635 TCP edb-server1 EDB Server 1 Carlos Portela Assigned
1635 UDP edb-server1 EDB Server 1 Carlos Portela Assigned
1636 TCP isdc ISP shared public data control Assigned
1636 UDP isdc ISP shared public data control Assigned
1637 TCP islc ISP shared local data control Assigned
1637 UDP islc ISP shared local data control 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 ↗