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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| hello-port | 652 | tcp | HELLO_PORT | [Patrick_Cipiere] | [Patrick_Cipiere] | ||||||
| hello-port | 652 | udp | HELLO_PORT | [Patrick_Cipiere] | [Patrick_Cipiere] | ||||||
| xnmp | 1652 | tcp | xnmp | [Ali_Saleh] | [Ali_Saleh] | ||||||
| xnmp | 1652 | udp | xnmp | [Ali_Saleh] | [Ali_Saleh] | ||||||
| interpathpanel | 2652 | tcp | InterPathPanel | [Stephen_Misel] | [Stephen_Misel] | ||||||
| interpathpanel | 2652 | udp | InterPathPanel | [Stephen_Misel] | [Stephen_Misel] | ||||||
| vxcrnbuport | 3652 | tcp | VxCR NBU Default Port | [Boris_Star] | [Boris_Star] | 2003-01 | |||||
| vxcrnbuport | 3652 | udp | VxCR NBU Default Port | [Boris_Star] | [Boris_Star] | 2003-01 | |||||
| 6641-6652 | Unassigned | ||||||||||
| 36463-36523 | Unassigned | ||||||||||
| febooti-aw | 36524 | tcp | Febooti Automation Workshop | [Maris_Bormanis] | [Maris_Bormanis] | 2011-06-10 | |||||
| 36524 | udp | Reserved | |||||||||
| 36525-36601 | Unassigned | ||||||||||
| 48620-48652 | Unassigned |
Contact Information
| ID | Name | Contact URI | Last Updated |
|---|---|---|---|
| [Ali_Saleh] | Ali Saleh | mailto:scomm&cerf.net | |
| [Boris_Star] | Boris Star | mailto:boris.star&veritas.com | 2003-01 |
| [Maris_Bormanis] | Maris Bormanis | mailto:info&febooti.com | 2011-06-10 |
| [Patrick_Cipiere] | Patrick Cipiere | mailto:Patrick.Cipiere&udcast.com | |
| [Stephen_Misel] | Stephen Misel | mailto:steve.misel&interpath.net |