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 |
|---|---|---|---|---|---|---|---|---|
| — | Not specified | hpr-bldlnx | HP Remote Build System for Linux-based Systems | Jeffrey J. Walls | — | — | Service name only | → |
| — | Not specified | hpr-bldwin | HP Remote Build System for Microsoft Windows Systems | Jeffrey J. Walls | — | — | Service name only | → |
| — | Not specified | hpr-db | Identifies systems that house databases for the Remote Build System and Remote Test System | Jeffrey J. Walls | — | — | Service name only | → |
| — | Not specified | hpr-rep | HP Remote Repository for Build and Test Results | Jeffrey J. Walls | — | — | Service name only | → |
| — | Not specified | hpr-toollnx | HP Remote System that houses compilers and tools for Linux-based Systems | Jeffrey J. Walls | — | — | Service name only | → |
| — | Not specified | hpr-toolwin | HP Remote System that houses compilers and tools for Microsoft Windows Systems | Jeffrey J. Walls | — | — | Service name only | → |
| — | Not specified | hpr-tstlnx | HP Remote Test System for Linux-based Systems | Jeffrey J. Walls | — | — | Service name only | → |
| — | Not specified | hpr-tstwin | HP Remote Test System for Microsoft Windows Systems | Jeffrey J. Walls | — | — | Service name only | → |
| — | Not specified | hs-off | Hobbyist Software Off Discovery | Rob Jonson | — | — | Service name only | → |
| — | Not specified | htsp | Home Tv Streaming Protocol | Andreas Öman | — | — | Service name only | → |
| — | TCP | https | HTTP over SSL/TLS | Tim Berners-Lee | — | — | Service name only | → |
| — | UDP | htvncconf | HomeTouch Vnc Configuration | Yuval Rakavy | 2012-07-10 | — | Service name only | → |
| — | TCP | hue | Philips hue protocol | Signify | 2017-11-01 | — | Service name only | → |
| — | TCP | huesync | Philips Hue Sync control protocol | Signify | 2019-07-31 | — | Service name only | → |
| — | Not specified | hyperstream | Atempo HyperStream deduplication server | Laurent Charmet | — | — | Service name only | → |
| — | Not specified | iad1 | BBN IAD | — | — | — | Service name only | → |
| — | Not specified | iad2 | BBN IAD | — | — | — | Service name only | → |
| — | Not specified | iad3 | BBN IAD | — | — | — | Service name only | → |
| — | TCP | iaudit | Braemar Inventory audit | Braemar Consulting | 2014-03-05 | — | Service name only | → |
| — | Not specified | ibiz | iBiz Server | IGG Software | — | — | Service name only | → |
| — | Not specified | ica-networking | Image Capture Networking | Baskaran Subramaniam | — | — | Service name only | → |
| — | Not specified | ican | Northrup Grumman/TASC/ICAN Protocol | Laurent Mihalkovic | — | — | Service name only | → |
| — | Not specified | ichalkboard | iChalk | Math Game House Software | — | — | Service name only | → |
| — | Not specified | ichat | iChat 1.0 | Jens Alfke | — | — | Service name only | → |
| — | Not specified | ici | ICI | Brent Hines | — | — | Service name only | → |
| — | Not specified | iconquer | iConquer | Andrew Zamler-Carhart | — | — | Service name only | → |
| — | TCP | icontrolbox | A Remote Control Application service used to control Computers on a Local Area Network | Umair Cheema | 2013-07-08 | — | Service name only | → |
| — | Not specified | idata | Generic Data Acquisition and Control Protocol | Carson Fenimore | — | — | Service name only | → |
| — | Not specified | idcws | Intermec Device Configuration Web Services | Thaddeus Ternes | — | — | Service name only | → |
| — | TCP | ideaquest | IDEAQUEST Safety Monitoring System | IDEAQUEST Inc. | 2016-12-12 | — | Service name only | → |
| — | Not specified | idsync | SplashID Synchronization Service | Justin Cepelak | — | — | Service name only | → |
| — | Not specified | iffl | iFFL Bonjour service for communication between client and server applications. | Kevin Gregory | 2016-03-20 | — | Service name only | → |
| — | Not specified | ifolder | Published iFolder | Brady Anderson | — | — | Service name only | → |
| — | Not specified | ihouse | Idle Hands iHouse Protocol | Toby Smith | — | — | Service name only | → |
| — | Not specified | ii-drills | Instant Interactive Drills | Ricky Sharp | — | — | Service name only | → |
| — | Not specified | ii-konane | Instant Interactive Konane | Ricky Sharp | — | — | Service name only | → |
| — | Not specified | ilynx | iLynX | iOS Software | — | — | Service name only | → |
| — | TCP | im | Instant Messaging | — | — | [RFC3861] | Service name only | → |
| — | UDP | im | Instant Messaging | — | — | [RFC3861] | Service name only | → |
| — | TCP | imagescal | ImagesCal App Data Sharing | 3 Lights Software LLC | 2014-07-22 | — | Service name only | → |
| — | Not specified | imidi | iMidi | Robert Grant | — | — | Service name only | → |
| — | TCP | imgsync | Protocol synchronizing Image data | Canon Inc | 2013-03-28 | — | Service name only | → |
| — | TCP | ims-ni | Noise Inspector | IMS merilni sistemi d.o.o. | 2012-08-24 | — | Service name only | → |
| — | Not specified | indigo-dvr | Indigo Security Digital Video Recorders | Haram Lee | — | — | Service name only | → |
| — | TCP | infboard | InfBoard interactive whiteboard protocol | Eric Sean Conner | 2011-10-17 | — | Service name only | → |
| — | TCP | informacast | Listing Singlewire InformaCast servers | Singlewire Software, LLC | 2019-03-11 | — | Service name only | → |
| — | TCP | innergroup | Service for a Communications App | Santo Porpiglia | 2015-05-28 | — | Service name only | → |
| — | Not specified | inova-ontrack | Inova Solutions OnTrack Display Protocol | — | — | — | Service name only | → |
| — | TCP | iot | Internet-of-things (IoT) JSON telegram service | SEVENSTAX GmbH | 2015-11-05 | — | Service name only | → |
| — | TCP | iota | iotaMed medical records server | Man In The Middle AB | 2011-10-18 | — | 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