Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2026-09-02
- 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| dhcpv6-server | 547 | tcp | DHCPv6 Server | [IESG] | [IETF_Chair] | 2018-05-21 | [RFC5460] | ||||
| dhcpv6-server | 547 | udp | DHCPv6 Server | [IESG] | [IETF_Chair] | 2018-05-21 | [RFC9915] | ||||
| gdoi | 848 | tcp | GDOI | [RFC3547] | |||||||
| gdoi | 848 | udp | GDOI | [RFC3547] | |||||||
| laplink | 1547 | tcp | laplink | [Michael_Crawford] | [Michael_Crawford] | ||||||
| laplink | 1547 | udp | laplink | [Michael_Crawford] | [Michael_Crawford] | ||||||
| vytalvaultvsmp | 2547 | tcp | vytalvaultvsmp | ||||||||
| vytalvaultvsmp | 2547 | udp | vytalvaultvsmp | ||||||||
| symantec-sim | 3547 | tcp | Symantec SIM | [George_Dzieciol] | [George_Dzieciol] | 2002-07 | |||||
| symantec-sim | 3547 | udp | Symantec SIM | [George_Dzieciol] | [George_Dzieciol] | 2002-07 | |||||
| lanner-lm | 4547 | tcp | Lanner License Manager | [Les_Enstone] | [Les_Enstone] | ||||||
| lanner-lm | 4547 | udp | Lanner License Manager | [Les_Enstone] | [Les_Enstone] | ||||||
| apsolab-col | 5470 | tcp | The Apsolab company's data collection protocol (native api) | [Apsolab_Inc] | [Jean-Francois_Gauthier] | 2014-11-10 | |||||
| 5470 | udp | Reserved | |||||||||
| apsolab-cols | 5471 | tcp | The Apsolab company's secure data collection protocol (native api) | [Apsolab_Inc] | [Jean-Francois_Gauthier] | 2014-11-10 | |||||
| 5471 | udp | Reserved | |||||||||
| apsolab-tag | 5472 | tcp | The Apsolab company's dynamic tag protocol | [Apsolab_Inc] | [Jean-Francois_Gauthier] | 2014-11-10 | |||||
| 5472 | udp | Reserved | |||||||||
| apsolab-tags | 5473 | tcp | The Apsolab company's secure dynamic tag protocol | [Apsolab_Inc] | [Jean-Francois_Gauthier] | 2014-11-10 | |||||
| 5473 | udp | Reserved | |||||||||
| apsolab-rpc | 5474 | udp | The Apsolab company's status query protocol | [Apsolab_Inc] | [Jean-Francois_Gauthier] | 2014-11-10 | |||||
| 5474 | tcp | Reserved | |||||||||
| apsolab-data | 5475 | tcp | The Apsolab company's data retrieval protocol | [Apsolab_Inc] | [Jean-Francois_Gauthier] | 2014-11-10 | |||||
| 5475 | udp | Reserved | |||||||||
| 5476-5499 | Unassigned | ||||||||||
| apc-6547 | 6547 | tcp | APC 6547 | [American_Power_Conve] | [American_Power_Conve] | ||||||
| apc-6547 | 6547 | udp | APC 6547 | [American_Power_Conve] | [American_Power_Conve] | ||||||
| cwmp | 7547 | tcp | Broadband Forum CWMP | [Broadband_Forum] | [Broadband_Forum] | 2006-01 | 2019-12-13 | ||||
| cwmp | 7547 | udp | Broadband Forum CWMP | [Broadband_Forum] | [Broadband_Forum] | 2006-01 | 2019-12-13 | ||||
| 10545-10547 | Unassigned | ||||||||||
| 12547-12752 | Unassigned | ||||||||||
| 23547-23999 | Unassigned | ||||||||||
| 25101-25470 | Unassigned | ||||||||||
| rna | 25471 | sctp | RNSAP User Adaptation for Iurh | [Dario_S_Tonesi] | [Dario_S_Tonesi] | 2011-02-07 | |||||
| 25472-25575 | Unassigned |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [American_Power_Conve] | American Power Conversion | mailto:ports&apcc.com | 2002-02 | |
| [Apsolab_Inc] | Apsolab Inc. | mailto:admin&apsolab.com | 2014-11-10 | |
| [Broadband_Forum] | Broadband Forum | mailto:help&broadband-forum.org | 2020-03-17 | |
| [Dario_S_Tonesi] | Dario S. Tonesi | mailto:dario.tonesi&nsn.com | 2011-02-07 | |
| [George_Dzieciol] | George Dzieciol | mailto:gdzieciol&symantec.com | 2002-07 | |
| [IESG] | IESG | mailto:iesg&ietf.org | ||
| [IETF_Chair] | IETF Chair | IETF | mailto:chair&ietf.org | |
| [Jean-Francois_Gauthier] | Jean-Francois Gauthier | Apsolab Inc. | mailto:jfgauthier&apsolab.com | 2014-11-10 |
| [Les_Enstone] | Les Enstone | mailto:lenstone&lanner.co.uk | ||
| [Michael_Crawford] | Michael Crawford | mailto:MichaelC&dev.travsoft.com |