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 |
|---|---|---|---|---|---|---|---|---|
| 4661 | TCP | kar2ouche | Kar2ouche Peer location service | Andy Krouwel | — | — | Assigned | → |
| 4661 | UDP | kar2ouche | Kar2ouche Peer location service | Andy Krouwel | — | — | Assigned | → |
| 4662 | TCP | oms | OrbitNet Message Service | Roy Davies | 2005-08 | — | Assigned | → |
| 4662 | UDP | oms | OrbitNet Message Service | Roy Davies | 2005-08 | — | Assigned | → |
| 4663 | TCP | noteit | Note It! Message Service | Pedro Alpedrinha | 2006-02 | — | Assigned | → |
| 4663 | UDP | noteit | Note It! Message Service | Pedro Alpedrinha | 2006-02 | — | Assigned | → |
| 4664 | TCP | ems | Rimage Messaging Server | David V. Raskin | 2006-02 | — | Assigned | → |
| 4664 | UDP | ems | Rimage Messaging Server | David V. Raskin | 2006-02 | — | Assigned | → |
| 4665 | TCP | contclientms | Container Client Message Service | Bruce Thompson | 2006-02 | — | Assigned | → |
| 4665 | UDP | contclientms | Container Client Message Service | Bruce Thompson | 2006-02 | — | Assigned | → |
| 4666 | TCP | eportcomm | E-Port Message Service | — | — | — | Assigned | → |
| 4666 | UDP | eportcomm | E-Port Message Service | — | — | — | Assigned | → |
| 4667 | TCP | mmacomm | MMA Comm Services | — | — | — | Assigned | → |
| 4667 | UDP | mmacomm | MMA Comm Services | — | — | — | Assigned | → |
| 4668 | TCP | mmaeds | MMA EDS Service | Robert Shaffer | 2006-02 | — | Assigned | → |
| 4668 | UDP | mmaeds | MMA EDS Service | Robert Shaffer | 2006-02 | — | Assigned | → |
| 4669 | TCP | eportcommdata | E-Port Data Service | Robert Shaffer | 2006-02 | — | Assigned | → |
| 4669 | UDP | eportcommdata | E-Port Data Service | Robert Shaffer | 2006-02 | — | Assigned | → |
| 4670 | TCP | light | Light packets transfer protocol | Adam Golovenko | 2006-10 | — | Assigned | → |
| 4670 | UDP | light | Light packets transfer protocol | Adam Golovenko | 2006-10 | — | Assigned | → |
| 4671 | TCP | acter | Bull RSF action server | Christian Caudrelier | 2006-02 | — | Assigned | → |
| 4671 | UDP | acter | Bull RSF action server | Christian Caudrelier | 2006-02 | — | Assigned | → |
| 4672 | TCP | rfa | remote file access server | — | — | — | Assigned | → |
| 4672 | UDP | rfa | remote file access server | — | — | — | Assigned | → |
| 4673 | TCP | cxws | CXWS Operations | Phil Abercrombie | 2005-08 | — | Assigned | → |
| 4673 | UDP | cxws | CXWS Operations | Phil Abercrombie | 2005-08 | — | Assigned | → |
| 4674 | TCP | appiq-mgmt | AppIQ Agent Management | Phil Abercrombie | 2005-08 | — | Assigned | → |
| 4674 | UDP | appiq-mgmt | AppIQ Agent Management | Phil Abercrombie | 2005-08 | — | Assigned | → |
| 4675 | TCP | dhct-status | BIAP Device Status | — | — | — | Assigned | → |
| 4675 | UDP | dhct-status | BIAP Device Status | — | — | — | Assigned | → |
| 4676 | TCP | dhct-alerts | BIAP Generic Alert | Louis Slothouber | 2005-08 | — | Assigned | → |
| 4676 | UDP | dhct-alerts | BIAP Generic Alert | Louis Slothouber | 2005-08 | — | Assigned | → |
| 4677 | TCP | bcs | Business Continuity Servi | Siew Sim | 2005-08 | — | Assigned | → |
| 4677 | UDP | bcs | Business Continuity Servi | Siew Sim | 2005-08 | — | Assigned | → |
| 4678 | TCP | traversal | boundary traversal | Kevin Lu | 2005-08 | — | Assigned | → |
| 4678 | UDP | traversal | boundary traversal | Kevin Lu | 2005-08 | — | Assigned | → |
| 4679 | TCP | mgesupervision | MGE UPS Supervision | — | — | — | Assigned | → |
| 4679 | UDP | mgesupervision | MGE UPS Supervision | — | — | — | Assigned | → |
| 4680 | TCP | mgemanagement | MGE UPS Management | Lecuivre J | 2005-08 | — | Assigned | → |
| 4680 | UDP | mgemanagement | MGE UPS Management | Lecuivre J | 2005-08 | — | Assigned | → |
| 4681 | TCP | parliant | Parliant Telephony System | Colin Henein | 2005-08 | — | Assigned | → |
| 4681 | UDP | parliant | Parliant Telephony System | Colin Henein | 2005-08 | — | Assigned | → |
| 4682 | TCP | finisar | finisar | Christina Mercier | 2005-08 | — | Assigned | → |
| 4682 | UDP | finisar | finisar | Christina Mercier | 2005-08 | — | Assigned | → |
| 4683 | TCP | spike | Spike Clipboard Service | Scott Herscher | 2005-08 | — | Assigned | → |
| 4683 | UDP | spike | Spike Clipboard Service | Scott Herscher | 2005-08 | — | Assigned | → |
| 4684 | TCP | rfid-rp1 | RFID Reader Protocol 1.0 | Michael Mealling | 2005-08 | — | Assigned | → |
| 4684 | UDP | rfid-rp1 | RFID Reader Protocol 1.0 | Michael Mealling | 2005-08 | — | Assigned | → |
| 4685 | TCP | autopac | Autopac Protocol | Peter Hallenbeck | 2005-08 | — | Assigned | → |
| 4685 | UDP | autopac | Autopac Protocol | Peter Hallenbeck | 2005-08 | — | 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