Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2026-09-02
- 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| hyperwave-isp | 692 | tcp | Hyperwave-ISP | [Gerald_Mesaric] | [Gerald_Mesaric] | ||||||
| hyperwave-isp | 692 | udp | Hyperwave-ISP | [Gerald_Mesaric] | [Gerald_Mesaric] | ||||||
| rift-lies | 914 | udp | Routing in Fat Trees Link Information Element | [IESG] | [IETF_Chair] | 2023-02-17 | 2024-06-07 | [RFC9692] | |||
| rift-ties | 915 | udp | Routing in Fat Trees Topology Information Element | [IESG] | [IETF_Chair] | 2023-02-17 | 2024-06-07 | [RFC9692] | |||
| exp1 | 1021 | tcp | RFC3692-style Experiment 1 | [IESG] | [IETF_Chair] | [1][RFC4727][RFC6335] | |||||
| exp1 | 1021 | udp | RFC3692-style Experiment 1 | [IESG] | [IETF_Chair] | [1][RFC4727][RFC6335] | |||||
| exp1 | 1021 | sctp | RFC3692-style Experiment 1 | [IESG] | [IETF_Chair] | [1][RFC4727][RFC6335] | |||||
| exp1 | 1021 | dccp | RFC3692-style Experiment 1 | [IESG] | [IETF_Chair] | [1][RFC4727][RFC6335] | |||||
| exp2 | 1022 | tcp | RFC3692-style Experiment 2 | [IESG] | [IETF_Chair] | [1][RFC4727][RFC6335] | |||||
| exp2 | 1022 | udp | RFC3692-style Experiment 2 | [IESG] | [IETF_Chair] | [1][RFC4727][RFC6335] | |||||
| exp2 | 1022 | sctp | RFC3692-style Experiment 2 | [IESG] | [IETF_Chair] | [1][RFC4727][RFC6335] | |||||
| exp2 | 1022 | dccp | RFC3692-style Experiment 2 | [IESG] | [IETF_Chair] | [1][RFC4727][RFC6335] | |||||
| sstsys-lm | 1692 | tcp | sstsys-lm | [Yih_Wu_Wang] | [Yih_Wu_Wang] | ||||||
| sstsys-lm | 1692 | udp | sstsys-lm | [Yih_Wu_Wang] | [Yih_Wu_Wang] | ||||||
| admins-lms | 2692 | tcp | Admins LMS | [Dagfinn_Saether] | [Dagfinn_Saether] | ||||||
| admins-lms | 2692 | udp | Admins LMS | [Dagfinn_Saether] | [Dagfinn_Saether] | ||||||
| intelsync | 3692 | tcp | Brimstone IntelSync | [Davey_Taylor] | [Davey_Taylor] | 2003-02 | |||||
| intelsync | 3692 | udp | Brimstone IntelSync | [Davey_Taylor] | [Davey_Taylor] | 2003-02 | |||||
| conspiracy | 4692 | tcp | Conspiracy messaging | [Jens_Edlund] | [Jens_Edlund] | 2005-08 | |||||
| conspiracy | 4692 | udp | Conspiracy messaging | [Jens_Edlund] | [Jens_Edlund] | 2005-08 | |||||
| 5690-5692 | Unassigned | ||||||||||
| 6902-6923 | Unassigned | ||||||||||
| split-ping | 6924 | tcp | Ping with RX/TX latency/loss split | [Ben_Cartwright_Cox] | [Ben_Cartwright_Cox] | 2020-02-12 | |||||
| split-ping | 6924 | udp | Ping with RX/TX latency/loss split | [Ben_Cartwright_Cox] | [Ben_Cartwright_Cox] | 2020-02-12 | |||||
| 6925-6934 | Unassigned |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Ben_Cartwright_Cox] | Ben Cartwright-Cox | mailto:ben&benjojo.co.uk | 2020-02-12 | |
| [Dagfinn_Saether] | Dagfinn Saether | mailto:Dagfinn&admins.com | ||
| [Davey_Taylor] | Davey Taylor | mailto:davey.taylor&brimstone.net | 2003-02 | |
| [Gerald_Mesaric] | Gerald Mesaric | mailto:gmesaric&hyperwave.com | ||
| [IESG] | IESG | mailto:iesg&ietf.org | ||
| [IETF_Chair] | IETF Chair | IETF | mailto:chair&ietf.org | |
| [Jens_Edlund] | Jens Edlund | mailto:edlund&speech.kth.se | 2005-08 | |
| [Yih_Wu_Wang] | Yih-Wu Wang | mailto:sstsys&ix.netcom.com |