Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2025-04-07
- 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 |
---|---|---|---|---|---|---|---|---|---|---|---|
irc | 194 | tcp | Internet Relay Chat Protocol | [Jarkko_Oikarinen] | [Jarkko_Oikarinen] | ||||||
irc | 194 | udp | Internet Relay Chat Protocol | [Jarkko_Oikarinen] | [Jarkko_Oikarinen] | ||||||
irc-serv | 529 | tcp | IRC-SERV | [Brian_Tackett] | [Brian_Tackett] | ||||||
irc-serv | 529 | udp | IRC-SERV | [Brian_Tackett] | [Brian_Tackett] | ||||||
bounzza | 2218 | tcp | Bounzza IRC Proxy | [Danko_Alexeyev] | [Danko_Alexeyev] | 2006-02 | |||||
bounzza | 2218 | udp | Bounzza IRC Proxy | [Danko_Alexeyev] | [Danko_Alexeyev] | 2006-02 | |||||
circle-x | 2931 | tcp | Circle-X | [Norm_Freedman_2] | [Norm_Freedman_2] | ||||||
circle-x | 2931 | udp | Circle-X | [Norm_Freedman_2] | [Norm_Freedman_2] | ||||||
wimd | 2980 | tcp | Instant Messaging Service | [Kevin_Birch] | [Kevin_Birch] | ||||||
wimd | 2980 | udp | Instant Messaging Service | [Kevin_Birch] | [Kevin_Birch] | ||||||
samd | 3275 | tcp | SAMD | [Edgar_Circenis] | [Edgar_Circenis] | ||||||
samd | 3275 | udp | SAMD | [Edgar_Circenis] | [Edgar_Circenis] | ||||||
ircu | 6665-6669 | tcp | IRCU | [Brian_Tackett] | [Brian_Tackett] | ||||||
ircs-u | 6697 | tcp | Internet Relay Chat via TLS/SSL | 2014-02-11 | [RFC7194] | ||||||
iwg1 | 7071 | tcp | IWGADTS Aircraft Housekeeping Message | [Don_Sullivan] | [Don_Sullivan] | 2010-02-16 | |||||
iwg1 | 7071 | udp | IWGADTS Aircraft Housekeeping Message | [Don_Sullivan] | [Don_Sullivan] | 2010-02-16 | |||||
d-star | 9011 | udp | D-Star Routing digital voice+data for amateur radio | [QuadNet2_USA_IRC_Network] | [Thomas_A_Early] | 2018-03-16 | |||||
emcrmirccd | 10004 | tcp | EMC Replication Manager Client | [Robert_Boudrie] | [Robert_Boudrie] | 2008-06-09 | |||||
hydap | 15000 | tcp | Hypack Data Aquisition | [HYPACK_Inc] | [Mircea_Neacsu] | 2011-10-27 | |||||
hydap | 15000 | udp | Hypack Data Aquisition | [HYPACK_Inc] | [Mircea_Neacsu] | 2011-10-27 | |||||
faircom-db | 19790 | tcp | FairCom Database | [FairCom_Corporation] | [Michael_Bowers] | 2020-12-04 | |||||
cctv | IP and Closed-Circuit Television for Securitiy applications | [Frank_Rottmann] | [Frank_Rottmann] | Defined TXT keys: u=<username>, p=<password>, path=<path to XML file> | |||||||
cpnotebook2 | NoteBook 2 | [Circus_Ponies_Suppor] | [Circus_Ponies_Suppor] | Defined TXT keys: None | |||||||
flir-ircam | tcp | FLIR Infrared Camera | [FLIR_Systems_AB] | [Bjorn_Roth][Klas_Malmborg] | 2011-10-20 | Defined TXT keys: Proprietary | |||||
irc-iot | tcp | The universal protocol for building IoT | [Alexey_Y_Woronov] | [Alexey_Y_Woronov] | 2019-12-20 | Defined TXT keys: _irc-iot | |||||
mxim-ice | Maxim Integrated Products In-circuit Emulator | [Zach_Metzinger] | [Zach_Metzinger] | Defined TXT keys: Proprietary | |||||||
robustirc | tcp | Like ircu (RFC1459), but failure tolerant due to strong consistency among n>=3 servers | [Michael_Stapelberg] | [Michael_Stapelberg] | 2015-01-07 | Defined TXT keys: None |