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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| terabase | 4000 | tcp | Terabase | [Thor_Olson] | [Thor_Olson] | Potential Conflict of ports PORT 4000 also used by ICQ <www.icq.com> | |||||
| terabase | 4000 | udp | Terabase | [Thor_Olson] | [Thor_Olson] | Potential Conflict of ports PORT 4000 also used by ICQ <www.icq.com> | |||||
| scotty-ft | 14000 | tcp | SCOTTY High-Speed Filetransfer | [Patrick_Verbeek] | [Patrick_Verbeek] | 2007-05 | |||||
| scotty-ft | 14000 | udp | SCOTTY High-Speed Filetransfer | [Patrick_Verbeek] | [Patrick_Verbeek] | 2007-05 | |||||
| med-ltp | 24000 | tcp | med-ltp | [Juergen_Fischbach] | [Juergen_Fischbach] | ||||||
| med-ltp | 24000 | udp | med-ltp | [Juergen_Fischbach] | [Juergen_Fischbach] | ||||||
| safetynetp | 40000 | tcp | SafetyNET p | [Pilz_GmbH_and_Co._KG] | [Matthias_Holzaepfel] | 2006-11 | 2022-12-15 | ||||
| safetynetp | 40000 | udp | SafetyNET p | [Pilz_GmbH_and_Co._KG] | [Matthias_Holzaepfel] | 2006-11 | 2022-12-15 | ||||
| 40001-40022 | Unassigned |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Juergen_Fischbach] | Juergen Fischbach | mailto:juergen.fischbach&philips.com | ||
| [Matthias_Holzaepfel] | Matthias Holzaepfel | Pilz GmbH & Co. KG | mailto:m.holzaepfel&pilz.de | 2022-12-15 |
| [Patrick_Verbeek] | Patrick Verbeek | mailto:p.verbeek&scottygroup.com | 2007-05 | |
| [Pilz_GmbH_and_Co._KG] | Pilz GmbH & Co. KG | mailto:m.holzaepfel&pilz.de | 2022-12-15 | |
| [Thor_Olson] | Thor Olson | mailto:Thor&terabase.com |