Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2026-09-07
- 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| sfs-config | 452 | tcp | Cray SFS config server | [Walter_Poxon] | [Walter_Poxon] | ||||||
| sfs-config | 452 | udp | Cray SFS config server | [Walter_Poxon] | [Walter_Poxon] | ||||||
| gtegsc-lm | 1452 | tcp | GTE Government Systems License Man | [Mike_Gregory] | [Mike_Gregory] | ||||||
| gtegsc-lm | 1452 | udp | GTE Government Systems License Man | [Mike_Gregory] | [Mike_Gregory] | ||||||
| snifferclient | 2452 | tcp | SnifferClient | [Amy_Weaver_2] | [Amy_Weaver_2] | ||||||
| snifferclient | 2452 | udp | SnifferClient | [Amy_Weaver_2] | [Amy_Weaver_2] | ||||||
| sabp-signal | 3452 | tcp | SABP-Signalling Protocol | [Brendan_McWilliams] | [Brendan_McWilliams] | 2002-04 | |||||
| sabp-signal | 3452 | udp | SABP-Signalling Protocol | [Brendan_McWilliams] | [Brendan_McWilliams] | 2002-04 | |||||
| ctiprogramload | 4452 | tcp | CTI Program Load | [Control_Technology_Inc] | [Clint_Eskew] | 2011-10-28 | |||||
| ctiprogramload | 4452 | udp | CTI Program Load | [Control_Technology_Inc] | [Clint_Eskew] | 2011-10-28 | |||||
| 5451-5452 | Unassigned |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Amy_Weaver_2] | Amy Weaver | mailto:amy_weaver&nai.com | ||
| [Brendan_McWilliams] | Brendan McWilliams | mailto:brendan.mcwilliams&vf.vodafone.co.uk | 2002-04 | |
| [Clint_Eskew] | Clint Eskew | Control Technology Inc. | mailto:ceskew&controltechnology.com | 2011-10-28 |
| [Control_Technology_Inc] | Control Technology Inc. | mailto:ceskew&controltechnology.com | 2011-10-28 | |
| [Mike_Gregory] | Mike Gregory | mailto:Gregory_Mike&msmail.iipo.gtegsc.com | ||
| [Walter_Poxon] | Walter Poxon | mailto:wdp&ironwood.cray.com |