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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| sift-uft | 608 | tcp | Sender-Initiated/Unsolicited File Transfer | [Rick_Troth] | [Rick_Troth] | ||||||
| sift-uft | 608 | udp | Sender-Initiated/Unsolicited File Transfer | [Rick_Troth] | [Rick_Troth] | ||||||
| smart-lm | 1608 | tcp | Smart Corp. License Manager | [Connie_Qiu] | [Connie_Qiu] | ||||||
| smart-lm | 1608 | udp | Smart Corp. License Manager | [Connie_Qiu] | [Connie_Qiu] | ||||||
| iec-104 | 2404 | tcp | IEC 60870-5-104 process control over IP | [Walter_K_Eichelburg] | [Walter_K_Eichelburg] | ||||||
| iec-104 | 2404 | udp | IEC 60870-5-104 process control over IP | [Walter_K_Eichelburg] | [Walter_K_Eichelburg] | ||||||
| wag-service | 2608 | tcp | Wag Service | [Gilles_Bourquard] | [Gilles_Bourquard] | ||||||
| wag-service | 2608 | udp | Wag Service | [Gilles_Bourquard] | [Gilles_Bourquard] | ||||||
| trendchip-dcp | 3608 | tcp | Trendchip control protocol | [Ming_Jen_Chen] | [Ming_Jen_Chen] | 2002-09 | |||||
| trendchip-dcp | 3608 | udp | Trendchip control protocol | [Ming_Jen_Chen] | [Ming_Jen_Chen] | 2002-09 | |||||
| gue | 6080 | udp | Generic UDP Encapsulation | [Tom_Herbert] | [Tom_Herbert] | 2015-03-05 | [draft-herbert-gue-02] | ||||
| 6080 | tcp | Reserved | |||||||||
| geneve | 6081 | udp | Generic Network Virtualization Encapsulation (Geneve) | [IESG] | [IETF_Chair] | 2014-03-27 | 2020-05-04 | [RFC8926] | |||
| 6081 | tcp | Reserved | |||||||||
| 6082 | tcp | Reserved | |||||||||
| p25cai | 6082 | udp | APCO Project 25 Common Air Interface - UDP encapsulation | [APCO_Project] | [APCO_Project] | 2011-05-13 | |||||
| 6083 | tcp | Reserved | |||||||||
| miami-bcast | 6083 | udp | telecomsoftware miami broadcast | [Peter_Steiner] | [Peter_Steiner] | 2011-02-22 | |||||
| reload-config | 6084 | tcp | Peer to Peer Infrastructure Configuration | [IESG] | [IETF_Chair] | 2009-01-29 | 2013-03-26 | [RFC6940] | |||
| 6084 | udp | Reserved | |||||||||
| konspire2b | 6085 | tcp | konspire2b p2p network | [Jason_Rohrer] | [Jason_Rohrer] | 2002-10 | |||||
| konspire2b | 6085 | udp | konspire2b p2p network | [Jason_Rohrer] | [Jason_Rohrer] | 2002-10 | |||||
| pdtp | 6086 | tcp | PDTP P2P | [Tony_Arcieri] | [Tony_Arcieri] | 2006-03 | |||||
| pdtp | 6086 | udp | PDTP P2P | [Tony_Arcieri] | [Tony_Arcieri] | 2006-03 | |||||
| ldss | 6087 | tcp | Local Download Sharing Service | [Clifford_Heath] | [Clifford_Heath] | 2006-05 | |||||
| ldss | 6087 | udp | Local Download Sharing Service | [Clifford_Heath] | [Clifford_Heath] | 2006-05 | |||||
| doglms | 6088 | tcp | SuperDog License Manager | [SafeNet] | [Rob_Tao] | 2012-07-26 | |||||
| doglms-notify | 6088 | udp | SuperDog License Manager Notifier | [SafeNet] | [Rob_Tao] | 2012-07-26 | |||||
| 6089-6098 | Unassigned | ||||||||||
| 8601-8608 | Unassigned | ||||||||||
| iec-104-sec | 19998 | tcp | IEC 60870-5-104 process control - secure | [Grant_Gilchrist] | [Grant_Gilchrist] | 2010-10-18 |