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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| esro-gen | 259 | tcp | Efficient Short Remote Operations | [Mohsen_Banan] | [Mohsen_Banan] | ||||||
| esro-gen | 259 | udp | Efficient Short Remote Operations | [Mohsen_Banan] | [Mohsen_Banan] | ||||||
| opennl-voice | 1259 | tcp | Open Network Library Voice | [Phil_Frisbie] | [Phil_Frisbie] | ||||||
| opennl-voice | 1259 | udp | Open Network Library Voice | [Phil_Frisbie] | [Phil_Frisbie] | ||||||
| bid-serv | 2259 | tcp | BIF identifiers resolution service | [Li_Zhiping] | [Zhang_Bo] | 2023-03-06 | |||||
| bid-serv | 2259 | udp | BIF identifiers resolution service | [Li_Zhiping] | [Zhang_Bo] | 2023-03-06 | |||||
| idotdist | 2590 | tcp | idotdist | [Jason_Hunter] | [Jason_Hunter] | ||||||
| idotdist | 2590 | udp | idotdist | [Jason_Hunter] | [Jason_Hunter] | ||||||
| maytagshuffle | 2591 | tcp | Maytag Shuffle | [Ken_Ksiazek] | [Ken_Ksiazek] | ||||||
| maytagshuffle | 2591 | udp | Maytag Shuffle | [Ken_Ksiazek] | [Ken_Ksiazek] | ||||||
| netrek | 2592 | tcp | netrek | [Al_Guetzlaff] | [Al_Guetzlaff] | ||||||
| netrek | 2592 | udp | netrek | [Al_Guetzlaff] | [Al_Guetzlaff] | ||||||
| mns-mail | 2593 | tcp | MNS Mail Notice Service | [Rumiko_Kikuta] | [Rumiko_Kikuta] | ||||||
| mns-mail | 2593 | udp | MNS Mail Notice Service | [Rumiko_Kikuta] | [Rumiko_Kikuta] | ||||||
| dts | 2594 | tcp | Data Base Server | [Andreas_Roene] | [Andreas_Roene] | ||||||
| dts | 2594 | udp | Data Base Server | [Andreas_Roene] | [Andreas_Roene] | ||||||
| worldfusion1 | 2595 | tcp | World Fusion 1 | ||||||||
| worldfusion1 | 2595 | udp | World Fusion 1 | ||||||||
| worldfusion2 | 2596 | tcp | World Fusion 2 | [World_Fusion] | [World_Fusion] | ||||||
| worldfusion2 | 2596 | udp | World Fusion 2 | [World_Fusion] | [World_Fusion] | ||||||
| homesteadglory | 2597 | tcp | Homestead Glory | [John_Tokash] | [John_Tokash] | ||||||
| homesteadglory | 2597 | udp | Homestead Glory | [John_Tokash] | [John_Tokash] | ||||||
| citriximaclient | 2598 | tcp | Citrix MA Client | [Myk_Willis] | [Myk_Willis] | ||||||
| citriximaclient | 2598 | udp | Citrix MA Client | [Myk_Willis] | [Myk_Willis] | ||||||
| snapd | 2599 | tcp | Snap Discovery | [Kevin_Osborn] | [Kevin_Osborn] | ||||||
| snapd | 2599 | udp | Snap Discovery | [Kevin_Osborn] | [Kevin_Osborn] | ||||||
| epncdp2 | 3259 | tcp | Epson Network Common Devi | [Oishi_Toshiaki] | [Oishi_Toshiaki] | 2002-02 | |||||
| epncdp2 | 3259 | udp | Epson Network Common Devi | [Oishi_Toshiaki] | [Oishi_Toshiaki] | 2002-02 | |||||
| 10254-10259 | Unassigned | ||||||||||
| 18259 | Unassigned | Known Unauthorized Use on port 18259 | |||||||||
| tasp-net | 25900 | tcp | TASP Network Comm | [Martin_Ellis] | [Martin_Ellis] | 2004-11 | |||||
| tasp-net | 25900 | udp | TASP Network Comm | [Martin_Ellis] | [Martin_Ellis] | 2004-11 | |||||
| niobserver | 25901 | tcp | NIObserver | [Roman_Oliynyk] | [Roman_Oliynyk] | ||||||
| niobserver | 25901 | udp | NIObserver | [Roman_Oliynyk] | [Roman_Oliynyk] | ||||||
| nilinkanalyst | 25902 | tcp | NILinkAnalyst | [Roman_Oliynyk_2] | [Roman_Oliynyk_2] | 2007-08-30 | |||||
| nilinkanalyst | 25902 | udp | NILinkAnalyst | [Roman_Oliynyk_2] | [Roman_Oliynyk_2] | 2007-08-30 | |||||
| niprobe | 25903 | tcp | NIProbe | [Roman_Oliynyk] | [Roman_Oliynyk] | ||||||
| niprobe | 25903 | udp | NIProbe | [Roman_Oliynyk] | [Roman_Oliynyk] | ||||||
| 25904-25953 | Unassigned | ||||||||||
| bf-game | 25954 | udp | Bitfighter game server | [Christopher_Eykamp] | [Christopher_Eykamp] | 2012-08-16 | |||||
| 25954 | tcp | Reserved | |||||||||
| bf-master | 25955 | udp | Bitfighter master server | [Christopher_Eykamp] | [Christopher_Eykamp] | 2012-08-16 | |||||
| 25955 | tcp | Reserved | |||||||||
| 25956-25999 | Unassigned | ||||||||||
| 26258-26259 | Unassigned | ||||||||||
| 30101-30259 | Unassigned |