Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2026-09-28
- Expert(s)
-
TCP/UDP: Joe Touch; Eliot Lear, Kumiko Ono, Wes Eddy, Brian Trammell, and Michael Scharf SCTP: Michael Tuexen DCCP: Eddie Kohler and Yoshifumi Nishida
- Reference
- [RFC 6335]
- Note
-
Service names and port numbers are used to distinguish between different services that run over transport protocols such as TCP, UDP, DCCP, and SCTP. Service names are assigned on a first-come, first-served process, as documented in [RFC 6335]. Port numbers are assigned in various ways, based on three ranges: System Ports (0-1023), User Ports (1024-49151), and the Dynamic and/or Private Ports (49152-65535); the different uses of these ranges are described in [RFC 6335]. According to Section 8.1.2 of [RFC 6335], System Ports are assigned by the "IETF Review" or "IESG Approval" procedures described in [RFC 8126]. User Ports are assigned by IANA using the "IETF Review" process, the "IESG Approval" process, or the "Expert Review" process, as per [RFC 6335]. Dynamic Ports are not assigned. The registration procedures for service names and port numbers are described in [RFC 6335]. Assigned ports both System and User ports SHOULD NOT be used without or prior to IANA registration. ************************************************************************ * PLEASE NOTE THE FOLLOWING: * * * * ASSIGNMENT OF A PORT NUMBER DOES NOT IN ANY WAY IMPLY AN * * ENDORSEMENT OF AN APPLICATION OR PRODUCT, AND THE FACT THAT NETWORK * * TRAFFIC IS FLOWING TO OR FROM A REGISTERED PORT DOES NOT MEAN THAT * * IT IS "GOOD" TRAFFIC, NOR THAT IT NECESSARILY CORRESPONDS TO THE * * ASSIGNED SERVICE. FIREWALL AND SYSTEM ADMINISTRATORS SHOULD * * CHOOSE HOW TO CONFIGURE THEIR SYSTEMS BASED ON THEIR KNOWLEDGE OF * * THE TRAFFIC IN QUESTION, NOT WHETHER THERE IS A PORT NUMBER * * REGISTERED OR NOT. * ************************************************************************
- Request an Assignment
-
[https://www.iana.org/protocols/apply]
- Available Formats
-

CSV
XML
HTML
TXT
| Service Name | Port Number | Transport Protocol | Description | Assignee | Contact | Registration Date | Modification Date | Reference | Service Code | Unauthorized Use Reported | Assignment Notes |
|---|---|---|---|---|---|---|---|---|---|---|---|
| ms-la | 3535 | tcp | MS-LA | [Eric_Ledoux] | [Eric_Ledoux] | ||||||
| ms-la | 3535 | udp | MS-LA | [Eric_Ledoux] | [Eric_Ledoux] | ||||||
| 35101-35353 | Unassigned | ||||||||||
| kitim | 35354 | tcp | KIT Messenger | [Rudi_Visser] | [Rudi_Visser] | 2011-07-07 | |||||
| 35354 | udp | Reserved | |||||||||
| altova-lm | 35355 | tcp | Altova License Management | [Alexander_Falk_2] | [Alexander_Falk_2] | 2011-07-07 | |||||
| altova-lm-disc | 35355 | udp | Altova License Management Discovery | [Alexander_Falk_2] | [Alexander_Falk_2] | 2011-07-07 | |||||
| guttersnex | 35356 | tcp | Gutters Note Exchange | [Squee_Application_Development] | [Tristan_Seifert_2] | 2011-07-19 | |||||
| 35356 | udp | Reserved | |||||||||
| openstack-id | 35357 | tcp | OpenStack ID Service | [Rackspace_Hosting] | [Ziad_Sawalha] | 2011-08-15 | |||||
| 35357 | udp | Reserved | |||||||||
| 35358-36000 | Unassigned |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Alexander_Falk_2] | Alexander Falk | Altova, Inc. | mailto:al&altova.com | 2011-07-07 |
| [Eric_Ledoux] | Eric Ledoux | mailto:ericleµsoft.com | ||
| [Rackspace_Hosting] | Rackspace Hosting | mailto:ziad.sawalha&rackspace.com | 2011-08-15 | |
| [Rudi_Visser] | Rudi Visser | mailto:rudi.visser&ljund.eu | 2011-07-07 | |
| [Squee_Application_Development] | Squee! Application Development | mailto:tristan&squee.co | 2011-07-19 | |
| [Tristan_Seifert_2] | Tristan Seifert | Squee! Application Development | mailto:tristan&squee.co | 2011-07-19 |
| [Ziad_Sawalha] | Ziad Sawalha | Rackspace Hosting | mailto:ziad.sawalha&rackspace.com | 2011-08-15 |