Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2024-11-27
- 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 |
---|---|---|---|---|---|---|---|---|---|---|---|
ftp-data | 20 | tcp | File Transfer [Default Data] | [Jon_Postel] | [Jon_Postel] | ||||||
ftp-data | 20 | udp | File Transfer [Default Data] | [Jon_Postel] | [Jon_Postel] | ||||||
ftp-data | 20 | sctp | FTP | [Randall_Stewart] | [Randall_Stewart] | 2022-02-07 | [RFC9260] | ||||
ftp | 21 | tcp | File Transfer Protocol [Control] | [Jon_Postel] | [Jon_Postel] | [RFC959] | Defined TXT keys: u=<username> p=<password> path=<path> | ||||
ftp | 21 | udp | File Transfer Protocol [Control] | [Jon_Postel] | [Jon_Postel] | [RFC959] | Defined TXT keys: u=<username> p=<password> path=<path> | ||||
ftp | 21 | sctp | FTP | [Randall_Stewart] | [Randall_Stewart] | 2022-02-07 | [RFC9260] | Defined TXT keys: u=<username> p=<password> path=<path> | |||
tftp | 69 | tcp | Trivial File Transfer | [David_Clark] | [David_Clark] | ||||||
tftp | 69 | udp | Trivial File Transfer | [David_Clark] | [David_Clark] | ||||||
sftp | 115 | tcp | Simple File Transfer Protocol | [Mark_Lottor] | [Mark_Lottor] | ||||||
sftp | 115 | udp | Simple File Transfer Protocol | [Mark_Lottor] | [Mark_Lottor] | ||||||
bftp | 152 | tcp | Background File Transfer Program | [Annette_DeSchon] | [Annette_DeSchon] | ||||||
bftp | 152 | udp | Background File Transfer Program | [Annette_DeSchon] | [Annette_DeSchon] | ||||||
softpc | 215 | tcp | Insignia Solutions | [Martyn_Thomas] | [Martyn_Thomas] | ||||||
softpc | 215 | udp | Insignia Solutions | [Martyn_Thomas] | [Martyn_Thomas] | ||||||
subntbcst-tftp | 247 | tcp | SUBNTBCST_TFTP IANA assigned this well-formed service name as a replacement for "subntbcst_tftp". |
[John_Fake] | [John_Fake] | ||||||
subntbcst_tftp | 247 | tcp | SUBNTBCST_TFTP | [John_Fake] | [John_Fake] | This entry is an alias to "subntbcst-tftp". This entry is now historic, not usable for use with many common service discovery mechanisms. | |||||
subntbcst-tftp | 247 | udp | SUBNTBCST_TFTP IANA assigned this well-formed service name as a replacement for "subntbcst_tftp". |
[John_Fake] | [John_Fake] | ||||||
subntbcst_tftp | 247 | udp | SUBNTBCST_TFTP | [John_Fake] | [John_Fake] | This entry is an alias to "subntbcst-tftp". This entry is now historic, not usable for use with many common service discovery mechanisms. | |||||
mftp | 349 | tcp | mftp | [Dave_Feinleib] | [Dave_Feinleib] | ||||||
mftp | 349 | udp | mftp | [Dave_Feinleib] | [Dave_Feinleib] | ||||||
ftp-agent | 574 | tcp | FTP Software Agent System | [Michael_S_Greenberg] | [Michael_S_Greenberg] | ||||||
ftp-agent | 574 | udp | FTP Software Agent System | [Michael_S_Greenberg] | [Michael_S_Greenberg] | ||||||
pftp | 662 | tcp | PFTP | [Ben_Schluricke] | [Ben_Schluricke] | ||||||
pftp | 662 | udp | PFTP | [Ben_Schluricke] | [Ben_Schluricke] | ||||||
ftps-data | 989 | tcp | ftp protocol, data, over TLS/SSL | ||||||||
ftps-data | 989 | udp | ftp protocol, data, over TLS/SSL | ||||||||
ftps | 990 | tcp | ftp protocol, control, over TLS/SSL | [Christopher_Allen] | [Christopher_Allen] | ||||||
ftps | 990 | udp | ftp protocol, control, over TLS/SSL | [Christopher_Allen] | [Christopher_Allen] | ||||||
tftp-mcast | 1758 | tcp | tftp-mcast | [Tom_Emberson] | [Tom_Emberson] | ||||||
tftp-mcast | 1758 | udp | tftp-mcast | [Tom_Emberson] | [Tom_Emberson] | ||||||
etftp | 1818 | tcp | Enhanced Trivial File Transfer Protocol | [William_Polites] | [William_Polites] | ||||||
etftp | 1818 | udp | Enhanced Trivial File Transfer Protocol | [William_Polites] | [William_Polites] | ||||||
utsftp | 2529 | tcp | UTS FTP | [David_Moore] | [David_Moore] | ||||||
utsftp | 2529 | udp | UTS FTP | [David_Moore] | [David_Moore] | ||||||
gsiftp | 2811 | tcp | GSI FTP | [Von_Welch] | [Von_Welch] | ||||||
gsiftp | 2811 | udp | GSI FTP | [Von_Welch] | [Von_Welch] | ||||||
odette-ftp | 3305 | tcp | ODETTE-FTP | [David_Nash] | [David_Nash] | [RFC5024] | |||||
odette-ftp | 3305 | udp | ODETTE-FTP | [David_Nash] | [David_Nash] | [RFC5024] | |||||
tftps | 3713 | tcp | TFTP over TLS | [Mark_mayernick] | [Mark_mayernick] | 2003-03 | |||||
tftps | 3713 | udp | TFTP over TLS | [Mark_mayernick] | [Mark_mayernick] | 2003-03 | |||||
exasoftport1 | 3920 | tcp | Exasoft IP Port | [Alan_Malik] | [Alan_Malik] | 2003-11 | |||||
exasoftport1 | 3920 | udp | Exasoft IP Port | [Alan_Malik] | [Alan_Malik] | 2003-11 | |||||
nst | 4687 | tcp | Network Scanner Tool FTP | [Mala_Bhat] | [Mala_Bhat] | 2005-08 | |||||
nst | 4687 | udp | Network Scanner Tool FTP | [Mala_Bhat] | [Mala_Bhat] | 2005-08 | |||||
mftp | 5402 | tcp | OmniCast MFTP | [Steve_Bannister] | [Steve_Bannister] | ||||||
mftp | 5402 | udp | OmniCast MFTP | [Steve_Bannister] | [Steve_Bannister] | ||||||
odette-ftps | 6619 | tcp | ODETTE-FTP over TLS/SSL | [Ieuan_Friend] | [Ieuan_Friend] | 2006-03 | [RFC5024] | ||||
odette-ftps | 6619 | udp | ODETTE-FTP over TLS/SSL | [Ieuan_Friend] | [Ieuan_Friend] | 2006-03 | [RFC5024] | ||||
kftp-data | 6620 | tcp | Kerberos V5 FTP Data | [Robert_J_Scott] | [Robert_J_Scott] | 2005-08 | |||||
kftp-data | 6620 | udp | Kerberos V5 FTP Data | [Robert_J_Scott] | [Robert_J_Scott] | 2005-08 | |||||
kftp | 6621 | tcp | Kerberos V5 FTP Control | [Robert_J_Scott] | [Robert_J_Scott] | 2005-08 | |||||
kftp | 6621 | udp | Kerberos V5 FTP Control | [Robert_J_Scott] | [Robert_J_Scott] | 2005-08 | |||||
mcftp | 6622 | tcp | Multicast FTP | [Bruce_Lueckenhoff_2] | [Bruce_Lueckenhoff_2] | 2006-02 | |||||
mcftp | 6622 | udp | Multicast FTP | [Bruce_Lueckenhoff_2] | [Bruce_Lueckenhoff_2] | 2006-02 | |||||
eftp | 37601 | tcp | Epipole File Transfer Protocol | [Epipole_Limited] | [Colin_Buchanan] | 2014-11-13 | |||||
spremotetablet | 46998 | tcp | Connection between a desktop computer or server and a signature tablet to capture handwritten signatures | [SOFTPRO_GmbH] | [Christoph_Hipp] | 2012-07-19 | 2013-08-02 | ||||
cftp | CFTP | ||||||||||
via-ftp | VIA Systems-File Transfer Protocol | ||||||||||
ftpcroco | Crocodile FTP Server | [Xnet_Communications] | [Xnet_Communications] | Defined TXT keys: None | |||||||
ni-ftp | tcp | NI FTP | [Steve_Kille] | [Steve_Kille] | 2017-05-18 | Defined TXT keys: None | |||||
ni-ftp | udp | NI FTP | [Steve_Kille] | [Steve_Kille] | 2017-05-18 | Defined TXT keys: None | |||||
scoop-sftp | tcp | The service name is used by the SFTP protocol to upload log files from vehicles to road side units in a securely way in a cooperative intelligent transportation system. | [SCOOP_at_F_Project] | [Houda_Labiod] | 2016-02-04 | Defined TXT keys: None | |||||
scoop-sftp | udp | The service name is used by the SFTP protocol to upload log files from vehicles to road side units in a securely way in a cooperative intelligent transportation system. | [SCOOP_at_F_Project] | [Houda_Labiod] | 2016-02-04 | Defined TXT keys: None | |||||
sftp-ssh | Secure File Transfer Protocol over SSH | [Bryan_Cole] | [Bryan_Cole] | Defined TXT keys: u=<username> p=<password> path=<path> | |||||||
simusoftpong | simusoftpong iPhone game protocol | [Anders_Svensson] | [Anders_Svensson] | Defined TXT keys: Proprietary |