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
70 TCP gopher Gopher Mark McCahill Assigned
70 UDP gopher Gopher Mark McCahill Assigned
71 TCP netrjs-1 Remote Job Service Assigned
71 UDP netrjs-1 Remote Job Service Assigned
72 TCP netrjs-2 Remote Job Service Assigned
72 UDP netrjs-2 Remote Job Service Assigned
73 TCP netrjs-3 Remote Job Service Assigned
73 UDP netrjs-3 Remote Job Service Assigned
74 TCP netrjs-4 Remote Job Service Bob Braden Assigned
74 UDP netrjs-4 Remote Job Service Bob Braden Assigned
75 TCP any private dial out service Jon Postel Assigned
75 UDP any private dial out service Jon Postel Assigned
76 TCP deos Distributed External Object Store Robert Ullmann Assigned
76 UDP deos Distributed External Object Store Robert Ullmann Assigned
77 TCP any private RJE service Jon Postel Assigned
77 UDP any private RJE service Jon Postel Assigned
78 TCP vettcp vettcp Christopher Leong Assigned
78 UDP vettcp vettcp Christopher Leong Assigned
79 TCP finger Finger David Zimmerman Assigned
79 UDP finger Finger David Zimmerman Assigned
80 TCP http World Wide Web HTTP IESG [RFC9110] Assigned
80 UDP http World Wide Web HTTP IESG [RFC9110] Assigned
80 TCP www World Wide Web HTTP IESG [RFC9110] Assigned
80 UDP www World Wide Web HTTP IESG [RFC9110] Assigned
80 TCP www-http World Wide Web HTTP Tim Berners-Lee Assigned
80 UDP www-http World Wide Web HTTP Tim Berners-Lee Assigned
80 SCTP http HTTP Randall Stewart (IETF TSVWG) [RFC9260] Assigned
81 Not specified Unassigned Unassigned
82 TCP xfer XFER Utility Thomas M. Smith Assigned
82 UDP xfer XFER Utility Thomas M. Smith Assigned
83 TCP mit-ml-dev MIT ML Device David Reed Assigned
83 UDP mit-ml-dev MIT ML Device David Reed Assigned
84 TCP ctf Common Trace Facility Hugh Thomas Assigned
84 UDP ctf Common Trace Facility Hugh Thomas Assigned
85 TCP mit-ml-dev MIT ML Device David Reed Assigned
85 UDP mit-ml-dev MIT ML Device David Reed Assigned
86 TCP mfcobol Micro Focus Cobol Simon Edwards Assigned
86 UDP mfcobol Micro Focus Cobol Simon Edwards Assigned
87 TCP any private terminal link Jon Postel Assigned
87 UDP any private terminal link Jon Postel Assigned
88 TCP kerberos Kerberos B. Clifford Neuman [RFC4120] Assigned
88 UDP kerberos Kerberos B. Clifford Neuman [RFC4120] Assigned
89 TCP su-mit-tg SU/MIT Telnet Gateway Mark Crispin Assigned
89 UDP su-mit-tg SU/MIT Telnet Gateway Mark Crispin Assigned
90 TCP dnsix DNSIX Securit Attribute Token Map Charles Watt Assigned
90 UDP dnsix DNSIX Securit Attribute Token Map Charles Watt Assigned
91 TCP mit-dov MIT Dover Spooler Eliot Moss Assigned
91 UDP mit-dov MIT Dover Spooler Eliot Moss Assigned
92 TCP npp Network Printing Protocol Louis Mamakos Assigned
92 UDP npp Network Printing Protocol Louis Mamakos 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 ↗