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 |
|---|---|---|---|---|---|---|---|---|
| 4109 | UDP | izm | Instantiated Zero-control Messaging | David Miller | 2007-02 | — | Assigned | → |
| 4110 | TCP | g2tag | G2 RFID Tag Telemetry Data | David Goodall | 2007-02 | — | Assigned | → |
| 4110 | UDP | g2tag | G2 RFID Tag Telemetry Data | David Goodall | 2007-02 | — | Assigned | → |
| 4111 | TCP | xgrid | Xgrid | David Kramer | 2004-11 | — | Assigned | → |
| 4111 | UDP | xgrid | Xgrid | David Kramer | 2004-11 | — | Assigned | → |
| 4112 | TCP | apple-vpns-rp | Apple VPN Server Reporting Protocol | Christophe Allie | 2006-08 | — | Assigned | → |
| 4112 | UDP | apple-vpns-rp | Apple VPN Server Reporting Protocol | Christophe Allie | 2006-08 | — | Assigned | → |
| 4113 | TCP | aipn-reg | AIPN LS Registration | Qiang Zhang | 2006-10 | — | Assigned | → |
| 4113 | UDP | aipn-reg | AIPN LS Registration | Qiang Zhang | 2006-10 | — | Assigned | → |
| 4114 | TCP | jomamqmonitor | JomaMQMonitor | Marcel Hofstetter | 2003-01 | — | Assigned | → |
| 4114 | UDP | jomamqmonitor | JomaMQMonitor | Marcel Hofstetter | 2003-01 | — | Assigned | → |
| 4115 | TCP | cds | CDS Transfer Agent | Neil Coggins | 2006-07 | — | Assigned | → |
| 4115 | UDP | cds | CDS Transfer Agent | Neil Coggins | 2006-07 | — | Assigned | → |
| 4116 | TCP | smartcard-tls | smartcard-TLS | Ilan Mahalal | 2006-04 | — | Assigned | → |
| 4116 | UDP | smartcard-tls | smartcard-TLS | Ilan Mahalal | 2006-04 | — | Assigned | → |
| 4117 | TCP | hillrserv | Hillr Connection Manager | Freddy A. Ayuso-Henson | 2008-05-22 | — | Assigned | → |
| 4117 | UDP | hillrserv | Hillr Connection Manager | Freddy A. Ayuso-Henson | 2008-05-22 | — | Assigned | → |
| 4118 | TCP | netscript | Netadmin Systems NETscript service | Göran Runfeldt | 2006-12 | — | Assigned | → |
| 4118 | UDP | netscript | Netadmin Systems NETscript service | Göran Runfeldt | 2006-12 | — | Assigned | → |
| 4119 | TCP | assuria-slm | Assuria Log Manager | Nick Connor | 2006-12 | — | Assigned | → |
| 4119 | UDP | assuria-slm | Assuria Log Manager | Nick Connor | 2006-12 | — | Assigned | → |
| 4120 | TCP | minirem | MiniRem Remote Telemetry and Control | MobilePro Systems | 2017-09-28 | — | Assigned | → |
| 4120 | UDP | — | Reserved | — | — | — | Reserved | → |
| 4121 | TCP | e-builder | e-Builder Application Communication | James Caza | 2006-12 | — | Assigned | → |
| 4121 | UDP | e-builder | e-Builder Application Communication | James Caza | 2006-12 | — | Assigned | → |
| 4122 | TCP | fprams | Fiber Patrol Alarm Service | Zhizhong Zhuang | 2006-12 | — | Assigned | → |
| 4122 | UDP | fprams | Fiber Patrol Alarm Service | Zhizhong Zhuang | 2006-12 | — | Assigned | → |
| 4123 | TCP | z-wave | Z-Wave Protocol | Sigma Designs, Inc. | 2007-02 | — | Assigned | → |
| 4123 | UDP | z-wave | Z-Wave Protocol | Sigma Designs, Inc. | 2007-02 | — | Assigned | → |
| 4124 | TCP | tigv2 | Rohill TetraNode Ip Gateway v2 | Bert Bouwers | 2007-05 | — | Assigned | → |
| 4124 | UDP | tigv2 | Rohill TetraNode Ip Gateway v2 | Bert Bouwers | 2007-05 | — | Assigned | → |
| 4125 | TCP | opsview-envoy | Opsview Envoy | Ton Voon | 2008-09-26 | — | Assigned | → |
| 4125 | UDP | opsview-envoy | Opsview Envoy | Ton Voon | 2008-09-26 | — | Assigned | → |
| 4126 | TCP | ddrepl | Data Domain Replication Service | Pratik Wadher | 2007-05 | — | Assigned | → |
| 4126 | UDP | ddrepl | Data Domain Replication Service | Pratik Wadher | 2007-05 | — | Assigned | → |
| 4127 | TCP | unikeypro | NetUniKeyServer | Raymond Chaw | 2007-05 | — | Assigned | → |
| 4127 | UDP | unikeypro | NetUniKeyServer | Raymond Chaw | 2007-05 | — | Assigned | → |
| 4128 | TCP | nufw | NuFW decision delegation protocol | — | — | — | Assigned | → |
| 4128 | UDP | nufw | NuFW decision delegation protocol | — | — | — | Assigned | → |
| 4129 | TCP | nuauth | NuFW authentication protocol | Eric Leblond | 2007-06 | — | Assigned | → |
| 4129 | UDP | nuauth | NuFW authentication protocol | Eric Leblond | 2007-06 | — | Assigned | → |
| 4130 | TCP | fronet | FRONET message protocol | Christer Nygren | 2007-08-07 | — | Assigned | → |
| 4130 | UDP | fronet | FRONET message protocol | Christer Nygren | 2007-08-07 | — | Assigned | → |
| 4131 | TCP | stars | Global Maintech Stars | Harry Goldschmitt | 2007-06 | — | Assigned | → |
| 4131 | UDP | stars | Global Maintech Stars | Harry Goldschmitt | 2007-06 | — | Assigned | → |
| 4132 | TCP | nuts-dem | NUTS Daemon IANA assigned this well-formed service name as a replacement for "nuts_dem". | — | — | — | Assigned | → |
| 4132 | TCP | nuts_dem | NUTS Daemon | — | — | — | Assigned | → |
| 4132 | UDP | nuts-dem | NUTS Daemon IANA assigned this well-formed service name as a replacement for "nuts_dem". | — | — | — | Assigned | → |
| 4132 | UDP | nuts_dem | NUTS Daemon | — | — | — | Assigned | → |
| 4133 | TCP | nuts-bootp | NUTS Bootp Server IANA assigned this well-formed service name as a replacement for "nuts_bootp". | Martin Freiss | — | — | 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