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.
| Port | Protocol | Service | Description | Assignee | Registration date | Reference/RFC | Status | Record details |
|---|---|---|---|---|---|---|---|---|
| — | UDP | nextcap | Proprietary communication protocol for NextCap capture solution | NextDay Aps | 2012-04-24 | — | Service name only | → |
| — | TCP | nfs-domainroot | NFS service for the domain root, the root of an organization's published file namespace. | IESG | 2012-04-24 | [RFC6641] | Service name only | → |
| — | TCP | ngr-keydist | NGR Key Distribution | nyantec | 2017-04-18 | — | Service name only | → |
| — | TCP | ni | National Instruments Network Device | National Instruments | 2011-10-24 | — | Service name only | → |
| — | TCP | ni-ftp | NI FTP | Steve Kille | 2017-05-18 | — | Service name only | → |
| — | UDP | ni-ftp | NI FTP | Steve Kille | 2017-05-18 | — | Service name only | → |
| — | TCP | ni-mail | NI MAIL | Steve Kille | 2017-05-18 | — | Service name only | → |
| — | UDP | ni-mail | NI MAIL | Steve Kille | 2017-05-18 | — | Service name only | → |
| — | TCP | ni-rt | National Instruments Real-Time Target | National Instruments | 2011-10-24 | — | Service name only | → |
| — | TCP | ni-sysapi | National Instruments System API Service | National Instruments | 2011-10-24 | — | Service name only | → |
| — | TCP | nodel | Lightweight event based control protocol utilising JavaScript Object Notation | Lumicom | 2013-02-07 | — | Service name only | → |
| — | TCP | nq | Network Quality test server endpoint | Stuart Cheshire | 2022-07-11 | — | Service name only | → |
| — | Not specified | ntlx-arch | American Dynamics Intellex Archive Management Service | Gary Sands | — | — | Service name only | → |
| — | Not specified | ntlx-ent | American Dynamics Intellex Enterprise Management Service | Gary Sands | — | — | Service name only | → |
| — | Not specified | ntlx-video | American Dynamics Intellex Video Service | Gary Sands | — | — | Service name only | → |
| — | UDP | ntx | Tenasys | Carl Ellis | — | — | Service name only | → |
| — | TCP | nusdp | Nuance Unity Service Discovery Protocol | Nuance Communications, Inc. | 2017-04-20 | — | Service name only | → |
| — | TCP | oak | Oak Device Services | Oak Labs, Inc. | 2017-02-09 | — | Service name only | → |
| — | UDP | oak | Oak Device Services | Oak Labs, Inc. | 2017-02-09 | — | Service name only | → |
| — | Not specified | obf | Observations Framework | Matthew Baker | — | — | Service name only | → |
| — | Not specified | objective | Means for clients to locate servers in an Objective (http://www.objective.com) instance. | Marc Bailey | — | — | Service name only | → |
| — | TCP | oca | Insecure OCP.1 protocol, which is the insecure TCP/IP implementation of the Object Control Architecture | OCA Alliance | 2012-10-11 | — | Service name only | → |
| — | UDP | oca | Insecure OCP.1 protocol, which is the insecure TCP/IP implementation of the Object Control Architecture | OCA Alliance | 2012-10-11 | — | Service name only | → |
| — | TCP | ocasec | Secure OCP.1 protocol, which is the secure TCP/IP implementation of the Object Control Architecture | OCA Alliance | 2012-10-11 | — | Service name only | → |
| — | UDP | ocasec | Secure OCP.1 protocol, which is the secure TCP/IP implementation of the Object Control Architecture | OCA Alliance | 2012-10-11 | — | Service name only | → |
| — | TCP | ocaws | Insecure OCP.1 hosted on a WebSocket | OCA Alliance | 2017-05-19 | — | Service name only | → |
| — | Not specified | oce | Oce Common Exchange Protocol | Dion Slijp | — | — | Service name only | → |
| — | Not specified | od-master | OpenDirectory Master | Jason Thorpe | — | — | Service name only | → |
| — | Not specified | odabsharing | OD4Contact | Objective Decision | — | — | Service name only | → |
| — | Not specified | odisk | Optical Disk Sharing | Bob Bradley | — | — | Service name only | → |
| — | Not specified | officetime-sync | OfficeTime Synchronization Protocol | Support | — | — | Service name only | → |
| — | Not specified | ofocus-conf | OmniFocus setting configuration | Timothy J. Wood | — | — | Service name only | → |
| — | Not specified | ofocus-sync | OmniFocus document synchronization | Timothy J. Wood | — | — | Service name only | → |
| — | TCP | ok-connect | Peer-to-peer nearby audio communication | Educacion Global, Inc | 2026-08-17 | — | Service name only | → |
| — | TCP | ok-control | Peer control and application data | Educacion Global, Inc | 2026-08-17 | — | Service name only | → |
| — | TCP | ola | Web Interface for the Open Lighting Architecture Software | Open Lighting Project | 2013-12-09 | — | Service name only | → |
| — | UDP | olpc-activity1 | One Laptop per Child activity | One Laptop per Child/Collabora Ltd. | — | — | Service name only | → |
| — | Not specified | oma-bcast-sg | OMA BCAST Service Guide Discovery Service | Stefan Ekenberg | — | — | Service name only | → |
| — | TCP | omadm-bootstrap | Open Mobile Alliance (OMA) Device Management (DM) Bootstrap Server Discovery Service | Open Mobile Alliance | 2011-08-19 | — | Service name only | → |
| — | Not specified | omni-bookmark | OmniWeb | The Omni Group | — | — | Service name only | → |
| — | Not specified | omni-live | Service for remote control of Omnisphere virtual instrument | Glenn Olander | — | — | Service name only | → |
| — | TCP | omnistate | Resource state update notifications | The Omni Group | 2020-07-10 | — | Service name only | → |
| — | TCP | onenet-info | OneNet Application Information Service | National Marine Electronics Association | 2019-12-09 | — | Service name only | → |
| — | TCP | onenet-pairing | OneNet Pairing | National Marine Electronics Association | 2019-12-09 | — | Service name only | → |
| — | UDP | onenet-pgn | OneNet PGN Transport Service | National Marine Electronics Association | 2019-12-09 | — | Service name only | → |
| — | Not specified | openbase | OpenBase SQL | — | — | — | Service name only | → |
| — | UDP | opencu | Conferencing Protocol | Marc Manthey | — | — | Service name only | → |
| — | TCP | openpath | Discovery of OpenPath appliances | OpenPath Security Inc | 2018-01-11 | — | Service name only | → |
| — | Not specified | oprofile | oprofile server protocol | Rob Bradford | — | — | Service name only | → |
| — | TCP | oro | ORO Core server REST configuration and control API | ORO | — | — | Service name only | → |
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