Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2026-09-11
- 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| telnet | 23 | tcp | Telnet | [Jon_Postel] | [Jon_Postel] | [RFC854] | Defined TXT keys: u=<username> p=<password> | ||||
| telnet | 23 | udp | Telnet | [Jon_Postel] | [Jon_Postel] | [RFC854] | Defined TXT keys: u=<username> p=<password> | ||||
| dlep | 854 | tcp | Dynamic Link Exchange Protocol (DLEP) | [IESG] | [IETF_Chair] | 2017-04-03 | [RFC8175] | ||||
| dlep | 854 | udp | Dynamic Link Exchange Protocol (DLEP) | [IESG] | [IETF_Chair] | 2017-04-03 | [RFC8175] | ||||
| owamp-test | 861 | udp | OWAMP-Test | [IESG] | [IETF_Chair] | 2018-12-21 | [RFC8545] | ||||
| twamp-test | 862 | udp | TWAMP-Test Receiver Port | [IESG] | [IETF_Chair] | 2018-12-21 | [RFC8545] | ||||
| buddy-draw | 1854 | tcp | Buddy Draw | [Marvin_Shin] | [Marvin_Shin] | ||||||
| buddy-draw | 1854 | udp | Buddy Draw | [Marvin_Shin] | [Marvin_Shin] | ||||||
| infomover | 2854 | tcp | InfoMover | [Carla_Caputo] | [Carla_Caputo] | ||||||
| infomover | 2854 | udp | InfoMover | [Carla_Caputo] | [Carla_Caputo] | ||||||
| stryker-com | 3854 | tcp | Stryker Comm Port | [Andrew_Schultz] | [Andrew_Schultz] | 2003-08 | |||||
| stryker-com | 3854 | udp | Stryker Comm Port | [Andrew_Schultz] | [Andrew_Schultz] | 2003-08 | |||||
| 40854-41110 | Unassigned |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Andrew_Schultz] | Andrew Schultz | mailto:aschultz&strykercom.com | 2003-08 | |
| [Carla_Caputo] | Carla Caputo | mailto:caputo&emc.com | ||
| [IESG] | IESG | mailto:iesg&ietf.org | ||
| [IETF_Chair] | IETF Chair | IETF | mailto:chair&ietf.org | |
| [Jon_Postel] | Jon Postel | mailto:postel&isi.edu | ||
| [Marvin_Shin] | Marvin Shin | mailto:president&medialingo.com |