Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2026-08-17
- 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
- [RFC6335]
- 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 [RFC6335]. 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 [RFC6335]. According to Section 8.1.2 of [RFC6335], System Ports are assigned by the "IETF Review" or "IESG Approval" procedures described in [RFC8126]. User Ports are assigned by IANA using the "IETF Review" process, the "IESG Approval" process, or the "Expert Review" process, as per [RFC6335]. Dynamic Ports are not assigned. The registration procedures for service names and port numbers are described in [RFC6335]. 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
Plain text
| Service Name | Port Number | Transport Protocol | Description | Assignee | Contact | Registration Date | Modification Date | Reference | Service Code | Unauthorized Use Reported | Assignment Notes |
|---|---|---|---|---|---|---|---|---|---|---|---|
| rda | 630 | tcp | RDA | [John_Hadjioannou] | [John_Hadjioannou] | ||||||
| rda | 630 | udp | RDA | [John_Hadjioannou] | [John_Hadjioannou] | ||||||
| oraclenet8cman | 1630 | tcp | Oracle Net8 Cman | [Tong_Ming_Lee] | [Tong_Ming_Lee] | ||||||
| oraclenet8cman | 1630 | udp | Oracle Net8 Cman | [Tong_Ming_Lee] | [Tong_Ming_Lee] | ||||||
| sitaramgmt | 2630 | tcp | Sitara Management | ||||||||
| sitaramgmt | 2630 | udp | Sitara Management | ||||||||
| cs-remote-db | 3630 | tcp | C&S Remote Database Port | ||||||||
| cs-remote-db | 3630 | udp | C&S Remote Database Port | ||||||||
| precise-comm | 5630 | tcp | PreciseCommunication | [Alon_Tamir] | [Alon_Tamir] | 2006-04 | |||||
| precise-comm | 5630 | udp | PreciseCommunication | [Alon_Tamir] | [Alon_Tamir] | 2006-04 | |||||
| bmc-grx | 6300 | tcp | BMC GRX | [Portnoy_Boxman] | [Portnoy_Boxman] | ||||||
| bmc-grx | 6300 | udp | BMC GRX | [Portnoy_Boxman] | [Portnoy_Boxman] | ||||||
| bmc-ctd-ldap | 6301 | tcp | BMC CONTROL-D LDAP SERVER IANA assigned this well-formed service name as a replacement for "bmc_ctd_ldap". |
[Portnoy_Boxman_2] | [Portnoy_Boxman_2] | 2006-09 | |||||
| bmc_ctd_ldap | 6301 | tcp | BMC CONTROL-D LDAP SERVER | [Portnoy_Boxman_2] | [Portnoy_Boxman_2] | 2006-09 | This entry is an alias to "bmc-ctd-ldap". This entry is now historic, not usable for use with many common service discovery mechanisms. | ||||
| bmc-ctd-ldap | 6301 | udp | BMC CONTROL-D LDAP SERVER IANA assigned this well-formed service name as a replacement for "bmc_ctd_ldap". |
[Portnoy_Boxman_2] | [Portnoy_Boxman_2] | 2006-09 | |||||
| bmc_ctd_ldap | 6301 | udp | BMC CONTROL-D LDAP SERVER | [Portnoy_Boxman_2] | [Portnoy_Boxman_2] | 2006-09 | This entry is an alias to "bmc-ctd-ldap". This entry is now historic, not usable for use with many common service discovery mechanisms. | ||||
| 6302-6305 | Unassigned | ||||||||||
| ufmp | 6306 | tcp | Unified Fabric Management Protocol | [Mellanox] | [Shachar_Dor] | 2009-12-17 | 2019-07-02 | ||||
| ufmp | 6306 | udp | Unified Fabric Management Protocol | [Mellanox] | [Shachar_Dor] | 2009-12-17 | 2019-07-02 | ||||
| 6307-6314 | Unassigned | ||||||||||
| 6630 | Unassigned | ||||||||||
| hawk | 7630 | tcp | HA Web Konsole | [Tim_Serong] | [Tim_Serong] | 2010-03-31 | |||||
| 7630 | udp | Reserved | |||||||||
| peoctlr | 9630 | tcp | Peovica Controller | [Adrian_Hungate] | [Adrian_Hungate] | 2009-09-14 | |||||
| 9630 | udp | Reserved | |||||||||
| 10549-10630 | Unassigned | ||||||||||
| 16163-16308 | Unassigned | ||||||||||
| etb4j | 16309 | tcp | etb4j | [Christopher_R_Smith] | [Christopher_R_Smith] | 2004-11 | |||||
| etb4j | 16309 | udp | etb4j | [Christopher_R_Smith] | [Christopher_R_Smith] | 2004-11 |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Adrian_Hungate] | Adrian Hungate | mailto:adrian&tlspu.com | 2014-07-11 | |
| [Alon_Tamir] | Alon Tamir | mailto:alon_tamir&symantec.com | 2006-04 | |
| [Christopher_R_Smith] | Christopher R. Smith | mailto:csmith4&us.ibm.com | 2004-11 | |
| [John_Hadjioannou] | John Hadjioannou | mailto:john&minster.co.uk | ||
| [Mellanox] | Mellanox Technologies, Inc. | mailto:info&mellanox.com | 2019-07-02 | |
| [Portnoy_Boxman] | Portnoy Boxman | mailto:portnoy_boxman&bmc.com | 2005-01 | |
| [Portnoy_Boxman_2] | Portnoy Boxman | mailto:Portnoy_Boxman&bmc.com | 2006-09 | |
| [Shachar_Dor] | Shachar Dor | Mellanox Technologies, Inc. | mailto:shachard&mellanox.com | 2019-07-02 |
| [Tim_Serong] | Tim Serong | mailto:tserong&novell.com | 2010-03-31 | |
| [Tong_Ming_Lee] | Tong-Ming Lee | mailto:tmlee&us.oracle.com |