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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| vsinet | 996 | tcp | vsinet | [Rob_Juergens] | [Rob_Juergens] | ||||||
| vsinet | 996 | udp | vsinet | [Rob_Juergens] | [Rob_Juergens] | ||||||
| tr-rsrb-port | 1996 | tcp | cisco Remote SRB port | ||||||||
| tr-rsrb-port | 1996 | udp | cisco Remote SRB port | ||||||||
| vsixml | 2996 | tcp | vsixml | [Rob_Juergens] | [Rob_Juergens] | ||||||
| vsixml | 2996 | udp | vsixml | [Rob_Juergens] | [Rob_Juergens] | ||||||
| abcsoftware | 3996 | tcp | abcsoftware-01 | [Andrew_Zimmerman] | [Andrew_Zimmerman] | 2004-06 | |||||
| abcsoftware | 3996 | udp | abcsoftware-01 | [Andrew_Zimmerman] | [Andrew_Zimmerman] | 2004-06 | |||||
| 6981-6996 | Unassigned | ||||||||||
| 8992-8996 | Unassigned | ||||||||||
| 9957-9965 | Unassigned | ||||||||||
| odnsp | 9966 | tcp | OKI Data Network Setting Protocol | [Masato_Sato] | [Masato_Sato] | 2006-05 | |||||
| odnsp | 9966 | udp | OKI Data Network Setting Protocol | [Masato_Sato] | [Masato_Sato] | 2006-05 | |||||
| 9967-9977 | Unassigned | ||||||||||
| palace-5 | 9996 | tcp | Palace-5 | [Douglas_Crockford] | [Douglas_Crockford] | ||||||
| palace-5 | 9996 | udp | Palace-5 | [Douglas_Crockford] | [Douglas_Crockford] | ||||||
| 11972-11996 | Unassigned | ||||||||||
| 16996-17006 | Unassigned |
Contact Information
| ID | Name | Contact URI | Last Updated |
|---|---|---|---|
| [Andrew_Zimmerman] | Andrew Zimmerman | mailto:andrew&zimmerman.net | 2004-06 |
| [Douglas_Crockford] | Douglas Crockford | mailto:douglas&crockford.com | |
| [Masato_Sato] | Masato Sato | mailto:satou203&oki.com | 2006-05 |
| [Rob_Juergens] | Rob Juergens | mailto:robj&vsi.com |