Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2024-09-23
- Expert(s)
-
TCP/UDP: Joe Touch; Eliot Lear, Kumiko Ono, Wes Eddy, Brian Trammell, Jana Iyengar, 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 |
---|---|---|---|---|---|---|---|---|---|---|---|
accessbuilder | 888 | tcp | AccessBuilder | [Steve_Sweeney] | [Steve_Sweeney] | ||||||
accessbuilder | 888 | udp | AccessBuilder | [Steve_Sweeney] | [Steve_Sweeney] | ||||||
cddbp | 888 | tcp | CD Database Protocol | [Steve_Scherf] | [Steve_Scherf] | This entry records an unassigned but widespread use | |||||
ncconfig | 1888 | tcp | NC Config Port | [Simon_Parker] | [Simon_Parker] | ||||||
ncconfig | 1888 | udp | NC Config Port | [Simon_Parker] | [Simon_Parker] | ||||||
spcsdlobby | 2888 | tcp | SPCSDLOBBY | [Matthew_Williams] | [Matthew_Williams] | ||||||
spcsdlobby | 2888 | udp | SPCSDLOBBY | [Matthew_Williams] | [Matthew_Williams] | ||||||
ciphire-serv | 3888 | tcp | Ciphire Services | [Lars_Eilebrecht] | [Lars_Eilebrecht] | 2003-10 | |||||
ciphire-serv | 3888 | udp | Ciphire Services | [Lars_Eilebrecht] | [Lars_Eilebrecht] | 2003-10 | |||||
xcap-portal | 4888 | tcp | xcap code analysis portal public user access | [_88solutions_Corporation] | [Manfred_Koethe] | 2018-06-06 | |||||
4888 | udp | Reserved | |||||||||
muse | 6888 | tcp | MUSE | [Muse_Communications] | [Muse_Communications] | ||||||
muse | 6888 | udp | MUSE | [Muse_Communications] | [Muse_Communications] | ||||||
7888-7899 | Unassigned | ||||||||||
cddbp-alt | 8880 | tcp | CDDBP | [Steve_Scherf] | [Steve_Scherf] | ||||||
cddbp-alt | 8880 | udp | CDDBP | [Steve_Scherf] | [Steve_Scherf] | ||||||
galaxy4d | 8881 | tcp | Galaxy4D Online Game Engine | [Galaxy4D] | [Olivier_St-Laurent] | 2012-06-18 | |||||
8881 | udp | Reserved | |||||||||
8882 | Unassigned | Unauthorized Use Known on port 8882 | |||||||||
secure-mqtt | 8883 | tcp | Secure MQTT | [OASIS] | [Robin_Cover] | 2008-02-27 | 2015-03-06 | ||||
secure-mqtt | 8883 | udp | Secure MQTT | [OASIS] | [Robin_Cover] | 2008-02-27 | 2015-03-06 | ||||
8884-8887 | Unassigned | ||||||||||
ddi-tcp-1 | 8888 | tcp | NewsEDGE server TCP (TCP 1) | [Fred_Yao] | [Fred_Yao] | Known Unauthorized Use on port 8888 | |||||
ddi-udp-1 | 8888 | udp | NewsEDGE server UDP (UDP 1) | [Fred_Yao] | [Fred_Yao] | Known Unauthorized Use on port 8888 | |||||
ddi-tcp-2 | 8889 | tcp | Desktop Data TCP 1 | [Fred_Yao] | [Fred_Yao] | Known Unauthorized Use on port 8889 | |||||
ddi-udp-2 | 8889 | udp | NewsEDGE server broadcast | [Fred_Yao] | [Fred_Yao] | Known Unauthorized Use on port 8889 | |||||
cyborg-systems | 9888 | tcp | CYBORG Systems | [Malcolm_Graham] | [Malcolm_Graham] | ||||||
cyborg-systems | 9888 | udp | CYBORG Systems | [Malcolm_Graham] | [Malcolm_Graham] | ||||||
18770-18880 | Unassigned | ||||||||||
infotos | 18881 | tcp | Infotos | [Marcel_Dube] | [Marcel_Dube] | 2004-11 | |||||
infotos | 18881 | udp | Infotos | [Marcel_Dube] | [Marcel_Dube] | 2004-11 | |||||
18882-18887 | Unassigned | ||||||||||
apc-necmp | 18888 | tcp | APCNECMP | [Michael_Yip] | [Michael_Yip] | ||||||
apc-necmp | 18888 | udp | APCNECMP | [Michael_Yip] | [Michael_Yip] | ||||||
18889-18999 | Unassigned |