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 | library | Delicious Library 2 Collection Data Sharing Protocol | William Shipley | — | — | Service name only | → |
| — | Not specified | libratone | Protocol for setup and control of Libratone products | Libratone A/S | 2011-10-27 | — | Service name only | → |
| — | Not specified | licor | LI-COR Biosciences instrument discovery | Software LI-COR Biosciences | 2011-10-18 | — | Service name only | → |
| — | Not specified | llrp-secure | RFID reader Low Level Reader Protocol over SSL/TLS | Jason Schoon | — | — | Service name only | → |
| — | Not specified | lobby | Gobby | 0x539 dev group | — | — | Service name only | → |
| — | UDP | logicnode | Logic Pro Distributed Audio | Nikolaus Gerteis | — | — | Service name only | → |
| — | TCP | logsheetserver | logSheet Server Synchronization Server | X2 Studios Ltd | 2020-05-06 | — | Service name only | → |
| — | Not specified | lonbridge | Echelon LonBridge Server | Rich Blomseth | — | — | Service name only | → |
| — | Not specified | lontalk | LonTalk over IP (ANSI 852) | Michael Tennefoss | — | — | Service name only | → |
| — | Not specified | lonworks | Echelon LNS Remote Client | Michael Tennefoss | — | — | Service name only | → |
| — | Not specified | lsys-appserver | Linksys One Application Server API | Frank Zerangue | — | — | Service name only | → |
| — | Not specified | lsys-camera | Linksys One Camera API | Frank Zerangue | — | — | Service name only | → |
| — | Not specified | lsys-ezcfg | LinkSys EZ Configuration | Frank Zerangue | — | — | Service name only | → |
| — | Not specified | lsys-oamp | LinkSys Operations, Administration, Management, and Provisioning | Frank Zerangue | — | — | Service name only | → |
| — | TCP | lumiere | A protocol to remotely control DMX512 devices over the network | Gangsta Ltd. | 2011-10-13 | — | Service name only | → |
| — | TCP | lumis-lca | Lumis Cache Appliance Protocol | Lumis | 2011-10-24 | — | Service name only | → |
| — | Not specified | lux-dtp | Lux Solis Data Transport Protocol | Laurence Flath | — | — | Service name only | → |
| — | Not specified | lxi | LXI | Nick Barendt | — | — | Service name only | → |
| — | Not specified | lyrics | iPod Lyrics Service | Gary Giebler | — | — | Service name only | → |
| — | TCP | M30S1PT | Moritz30-Project Standard protocol 1 Plain Text | Moritz30 | 2015-12-07 | — | Service name only | → |
| — | UDP | M30S1PT | Moritz30-Project Standard protocol 1 Plain Text | Moritz30 | 2015-12-07 | — | Service name only | → |
| — | Not specified | macfoh | MacFOH | Shaun Wexler | — | — | Service name only | → |
| — | Not specified | macfoh-admin | MacFOH admin services | Shaun Wexler | — | — | Service name only | → |
| — | UDP | macfoh-audio | MacFOH audio stream | Shaun Wexler | — | — | Service name only | → |
| — | UDP | macfoh-events | MacFOH show control events | Shaun Wexler | — | — | Service name only | → |
| — | UDP | macfoh-data | MacFOH realtime data | Shaun Wexler | — | — | Service name only | → |
| — | Not specified | macfoh-db | MacFOH database | Shaun Wexler | — | — | Service name only | → |
| — | Not specified | macfoh-remote | MacFOH Remote | Shaun Wexler | — | — | Service name only | → |
| — | Not specified | macminder | Mac Minder | Luma Code | — | — | Service name only | → |
| — | Not specified | maestro | Maestro Music Sharing Service | Luke Steffen | — | — | Service name only | → |
| — | Not specified | magicdice | Magic Dice Game Protocol | Mike Yenco | — | — | Service name only | → |
| — | Not specified | mandos | Mandos Password Server | Mandos Maintainers | — | — | Service name only | → |
| — | TCP | mas | Pravala Mobility and Aggregation Service | Pravala Networks ULC | 2016-06-01 | — | Service name only | → |
| — | UDP | mas | Pravala Mobility and Aggregation Service | Pravala Networks ULC | 2016-06-01 | — | Service name only | → |
| — | Not specified | matrix | MATRIX Remote AV Switching | Ken Jibiki | — | — | Service name only | → |
| — | TCP | matterc | Matter Commissionable Node Discovery | Connectivity Standards Alliance | 2021-05-21 | — | Service name only | → |
| — | UDP | matterc | Matter Commissionable Node Discovery | Connectivity Standards Alliance | 2021-05-21 | — | Service name only | → |
| — | TCP | matterd | Matter Commissioner Discovery | Connectivity Standards Alliance | 2021-05-21 | — | Service name only | → |
| — | UDP | matterd | Matter Commissioner Discovery | Connectivity Standards Alliance | 2021-05-21 | — | Service name only | → |
| — | TCP | mavlink | MAVLink Micro Air Vehicle Communication Protocol | Roderick Mann | 2011-10-20 | — | Service name only | → |
| — | UDP | mazepseudo-game | Peer to peer communication between instances of the Maze Pseudo game. | Mad Elf Software, Inc. | 2016-02-02 | — | Service name only | → |
| — | Not specified | mbconsumer | MediaBroker++ Consumer | Nate Rivard | — | — | Service name only | → |
| — | Not specified | mbproducer | MediaBroker++ Producer | Nate Rivard | — | — | Service name only | → |
| — | Not specified | mbserver | MediaBroker++ Server | Nate Rivard | — | — | Service name only | → |
| — | Not specified | mconnect | ClairMail Connect | Sachin Desai | — | — | Service name only | → |
| — | Not specified | mcrcp | MediaCentral | equinux | — | — | Service name only | → |
| — | Not specified | mediaboard1 | MediaBoardONE Asset and Information Manager data sharing and synchronization protocol | Thomas K. Fischer | — | — | Service name only | → |
| — | TCP | mediatap | Mediatap streaming protocol | Mediatap GbR | 2011-10-11 | — | Service name only | → |
| — | TCP | mercurydock | Mercury Dock Assistant | Spider Electronics | 2014-03-10 | — | Service name only | → |
| — | Not specified | mesamis | Mes Amis | David Priest | — | — | 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