Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2024-08-29
- 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 |
---|---|---|---|---|---|---|---|---|---|---|---|
hp-3000-telnet | 2564 | tcp | HP 3000 NS/VT block mode telnet | ||||||||
hp-3000-telnet | 2564 | udp | HP 3000 NS/VT block mode telnet | ||||||||
hbci | 3000 | tcp | HBCI | [Kurt_Haubner] | [Kurt_Haubner] | ||||||
hbci | 3000 | udp | HBCI | [Kurt_Haubner] | [Kurt_Haubner] | ||||||
remoteware-cl | 3000 | tcp | RemoteWare Client | [Tim_Farley] | [Tim_Farley] | This entry records an unassigned but widespread use | |||||
remoteware-cl | 3000 | udp | RemoteWare Client | [Tim_Farley] | [Tim_Farley] | This entry records an unassigned but widespread use | |||||
inovaport1 | 23000 | tcp | Inova LightLink Server Type 1 | [Chris_Koeritz_3] | [Chris_Koeritz_3] | 2006-10 | |||||
inovaport1 | 23000 | udp | Inova LightLink Server Type 1 | [Chris_Koeritz_3] | [Chris_Koeritz_3] | 2006-10 | |||||
ndmps | 30000 | tcp | Secure Network Data Management Protocol | [Alioune_Thiam] | [Alioune_Thiam] | 2013-02-05 | |||||
30000 | udp | Reserved | |||||||||
pago-services1 | 30001 | tcp | Pago Services 1 | [Balduin_Mueller_Plat] | [Balduin_Mueller_Plat] | 2002-03 | |||||
pago-services1 | 30001 | udp | Pago Services 1 | [Balduin_Mueller_Plat] | [Balduin_Mueller_Plat] | 2002-03 | |||||
pago-services2 | 30002 | tcp | Pago Services 2 | [Balduin_Mueller_Plat] | [Balduin_Mueller_Plat] | 2002-03 | |||||
pago-services2 | 30002 | udp | Pago Services 2 | [Balduin_Mueller_Plat] | [Balduin_Mueller_Plat] | 2002-03 | |||||
amicon-fpsu-ra | 30003 | tcp | Amicon FPSU-IP Remote Administration | [Amicon_OOO] | [Alexey_Novotorzhin] | 2013-04-25 | |||||
amicon-fpsu-ra | 30003 | udp | Amicon FPSU-IP Remote Administration | [Amicon_OOO] | [Alexey_Novotorzhin] | 2013-04-25 | |||||
amicon-fpsu-s | 30004 | udp | Amicon FPSU-IP VPN | [Amicon_OOO] | [Alexey_Novotorzhin] | 2013-04-25 | |||||
30004 | tcp | Reserved | |||||||||
30005-30099 | Unassigned | ||||||||||
wg-endpt-comms | 33000 | tcp | WatchGuard Endpoint Communications | [WatchGuard_Technologies_Inc] | [Anunoy_Ghosh] | 2020-01-16 | |||||
33000 | udp | Reserved | |||||||||
recvr-rc | 43000 | tcp | Receiver Remote Control | [Research_Electronics_International] | [Ross_Binkley] | 2012-12-20 | |||||
recvr-rc-disc | 43000 | udp | Receiver Remote Control Discovery | [Research_Electronics_International] | [Ross_Binkley] | 2012-12-20 |
Contact Information
ID | Name | Organization | Contact URI | Last Updated |
---|---|---|---|---|
[Alexey_Novotorzhin] | Alexey Novotorzhin | Amicon OOO | mailto:nav&amicon.ru | 2013-04-25 |
[Alioune_Thiam] | Alioune Thiam | mailto:alioune_thiam&symantec.com | 2013-02-05 | |
[Amicon_OOO] | Amicon OOO | mailto:info&amicon.ru | 2013-04-25 | |
[Anunoy_Ghosh] | Anunoy Ghosh | mailto:anunoy.ghosh&watchguard.com | 2020-01-16 | |
[Balduin_Mueller_Plat] | Balduin Mueller-Platz | mailto:balduin.mueller-platz&pago.de | 2002-03 | |
[Chris_Koeritz_3] | Chris Koeritz | mailto:portmanager&inovasolutions.com | 2006-10 | |
[Kurt_Haubner] | Kurt Haubner | mailto:haubner&ibm.net | ||
[Research_Electronics_International] | Research Electronics International | mailto:software&reiusa.net | 2012-12-20 | |
[Ross_Binkley] | Ross Binkley | Research Electronics International | mailto:software&reiusa.net | 2012-12-20 |
[Tim_Farley] | Tim Farley | mailto:Tim.Farley&xcellenet.com | ||
[WatchGuard_Technologies_Inc] | WatchGuard Technologies, Inc. | mailto:vendoraccount&watchguard.com | 2020-01-16 |