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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| skronk | 460 | tcp | skronk | [Henry_Strickland] | [Henry_Strickland] | ||||||
| skronk | 460 | udp | skronk | [Henry_Strickland] | [Henry_Strickland] | ||||||
| dhcpv6-server | 547 | tcp | DHCPv6 Server | [IESG] | [IETF_Chair] | 2018-05-21 | [RFC5460] | ||||
| proshare2 | 1460 | tcp | Proshare Notebook Application | [Robin_Kar] | [Robin_Kar] | ||||||
| proshare2 | 1460 | udp | Proshare Notebook Application | [Robin_Kar] | [Robin_Kar] | ||||||
| ms-theater | 2460 | tcp | ms-theater | [Anton_Kucer] | [Anton_Kucer] | ||||||
| ms-theater | 2460 | udp | ms-theater | [Anton_Kucer] | [Anton_Kucer] | ||||||
| edm-manager | 3460 | tcp | EDM Manger | ||||||||
| edm-manager | 3460 | udp | EDM Manger | ||||||||
| ntske | 4460 | tcp | Network Time Security Key Establishment | [IESG] | [IETF_Chair] | 2020-04-07 | [RFC8915] | ||||
| 4460 | udp | Reserved | |||||||||
| piranha1 | 4600 | tcp | Piranha1 | ||||||||
| piranha1 | 4600 | udp | Piranha1 | ||||||||
| piranha2 | 4601 | tcp | Piranha2 | [Primark_Corporation] | [Primark_Corporation] | ||||||
| piranha2 | 4601 | udp | Piranha2 | [Primark_Corporation] | [Primark_Corporation] | ||||||
| mtsserver | 4602 | tcp | EAX MTS Server | [Pedro_A_Rodriguez] | [Pedro_A_Rodriguez] | 2008-08-06 | |||||
| 4602 | udp | Reserved | |||||||||
| menandmice-upg | 4603 | tcp | Men & Mice Upgrade Agent | [Eggert_Thorlacius_2] | [Eggert_Thorlacius_2] | 2010-01-27 | |||||
| 4603 | udp | Reserved | |||||||||
| irp | 4604 | tcp | Identity Registration Protocol | [Sixscape_Communications_Pte_Ltd] | [Lawrence_E._Hughes] | 2014-03-17 | 2014-08-26 | ||||
| 4604 | udp | Reserved | |||||||||
| sixchat | 4605 | tcp | Direct End to End Secure Chat Protocol | [Sixscape_Communications_Pte_Ltd] | [Lawrence_E._Hughes] | 2014-09-11 | |||||
| 4605 | udp | Reserved | |||||||||
| sixid | 4606 | tcp | Secure ID to IP registration and lookup | [Sixscape_Communications_Pte_Ltd] | [Lawrence_E._Hughes] | 2020-04-28 | |||||
| 4606 | udp | Reserved | |||||||||
| 4607-4620 | Unassigned | ||||||||||
| 5457-5460 | Unassigned | ||||||||||
| 24578-24600 | Unassigned | ||||||||||
| udpstp | 24601 | udp | UDP-based IP-Layer Capacity and Performance Measurement protocol | [IESG] | [IETF_Chair] | 2025-09-26 | [RFC9946] | ||||
| 24601 | tcp | Reserved | |||||||||
| 24602-24665 | Unassigned | ||||||||||
| 44600 | tcp | Reserved | |||||||||
| asihpi | 44600 | udp | AudioScience HPI | [Eliot_Blennerhassett] | [Eliot_Blennerhassett] | 2011-07-07 | |||||
| 44601-44817 | Unassigned |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Anton_Kucer] | Anton Kucer | mailto:akucerµsoft.com | ||
| [Eggert_Thorlacius_2] | Eggert Thorlacius | mailto:eggi&menandmice.com | 2010-01-27 | |
| [Eliot_Blennerhassett] | Eliot Blennerhassett | mailto:eblennerhassett&audioscience.com | 2011-07-07 | |
| [Henry_Strickland] | Henry Strickland | mailto:strick&yak.net | ||
| [IESG] | IESG | mailto:iesg&ietf.org | ||
| [IETF_Chair] | IETF Chair | IETF | mailto:chair&ietf.org | |
| [Lawrence_E._Hughes] | Lawrence E. Hughes | Sixscape Communications, Ltd. | mailto:lhughes&sixscape.com | 2014-03-17 |
| [Pedro_A_Rodriguez] | Pedro A Rodriguez | mailto:pedro.rdz&eaxtechnologies.com.mx | 2008-08-06 | |
| [Primark_Corporation] | Primark Corporation | mailto:joe.boone&primark.com | ||
| [Robin_Kar] | Robin Kar | mailto:Robin_Kar&ccm.hf.intel.com | ||
| [Sixscape_Communications_Pte_Ltd] | Sixscape Communications, Pte. Ltd. | mailto:lhughes&sixscape.com | 2014-08-26 |