Internet Assigned Numbers Authority

Service Name and Transport Protocol Port Number Registry

Last Updated
2025-06-12
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 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>
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]
saft 487 tcp saft Simple Asynchronous File Transfer [Ulli_Horlacher] [Ulli_Horlacher]
saft 487 udp saft Simple Asynchronous File Transfer [Ulli_Horlacher] [Ulli_Horlacher]
sift-uft 608 tcp Sender-Initiated/Unsolicited File Transfer [Rick_Troth] [Rick_Troth]
sift-uft 608 udp Sender-Initiated/Unsolicited File Transfer [Rick_Troth] [Rick_Troth]
bnetfile 1120 tcp Battle.net File Transfer Protocol [Domain_Tech] [Domain_Tech] 2005-04
bnetfile 1120 udp Battle.net File Transfer Protocol [Domain_Tech] [Domain_Tech] 2005-04
etftp 1818 tcp Enhanced Trivial File Transfer Protocol [William_Polites] [William_Polites]
etftp 1818 udp Enhanced Trivial File Transfer Protocol [William_Polites] [William_Polites]
simple-tx-rx 2257 tcp simple text/file transfer [Daniel_Kilsdonk] [Daniel_Kilsdonk] 2006-08
simple-tx-rx 2257 udp simple text/file transfer [Daniel_Kilsdonk] [Daniel_Kilsdonk] 2006-08
rothaga 7117 tcp Encrypted chat and file transfer service [Arcadian_Computers] [Jonathan_Pollock] 2016-05-10
isdd 8148 tcp i-SDD file transfer [Frank_Waarsenburg] [Frank_Waarsenburg] 2004-11
isdd 8148 udp i-SDD file transfer [Frank_Waarsenburg] [Frank_Waarsenburg] 2004-11
scotty-ft 14000 tcp SCOTTY High-Speed Filetransfer [Patrick_Verbeek] [Patrick_Verbeek] 2007-05
scotty-ft 14000 udp SCOTTY High-Speed Filetransfer [Patrick_Verbeek] [Patrick_Verbeek] 2007-05
caldsoft-backup 22537 tcp CaldSoft Backup server file transfer [CaldSoft] [Mark_Caldwell] 2011-08-12
eftp 37601 tcp Epipole File Transfer Protocol [Epipole_Limited] [Colin_Buchanan] 2014-11-13
via-ftp VIA Systems-File Transfer Protocol
commfort tcp A client-server chat for LAN or Internet with video chat support [CommFort_software_Ltd.] [Maxim_Mirgorodsky] 2016-03-03 Defined TXT keys: commfort, chat, communications, client-server, local chat, LAN, network, voice chat, video chat, video communication, video conference, file transfer
payload-app tcp Local and remote file transfers [Didrik_Nordström] [Didrik_Nordström] 2022-12-02 Defined TXT keys: _payload._tcp.local, _payload._udp.local
payload-app udp Local and remote file transfers [Didrik_Nordström] [Didrik_Nordström] 2022-12-02 Defined TXT keys: _payload._tcp.local, _payload._udp.local
sftp-ssh Secure File Transfer Protocol over SSH [Bryan_Cole] [Bryan_Cole] Defined TXT keys: u=<username> p=<password> path=<path>
swyp Framework for transferring any file from any app, to any app on any device: simply with a swÿp. [ExoMachina] [Alexander_List] 2011-12-06 Defined TXT keys: NONE
wifile tcp System for transferring files between mobile device and computer in a local network [Artyom_Nikolaev] [Artyom_Nikolaev] 2016-12-23 Defined TXT keys: None

Contact Information

ID Name Organization Contact URI Last Updated
[Alexander_List] Alexander List mailto:alist&exomachina.com 2011-12-06
[Annette_DeSchon] Annette DeSchon mailto:DESCHON&isi.edu
[Arcadian_Computers] Arcadian Computers mailto:support&arcadiancomputers.com 2016-05-10
[Artyom_Nikolaev] Artyom Nikolaev mailto:support&wifile.info 2016-12-23
[Bryan_Cole] Bryan Cole mailto:bryan.cole&teraview.com
[CaldSoft] CaldSoft mailto:development&caldsoft.co.uk 2011-08-12
[Colin_Buchanan] Colin Buchanan Epipole Limited mailto:colin&epipole.com 2014-11-13
[CommFort_software_Ltd.] CommFort software Ltd. mailto:support&commfort.com 2016-03-03
[Daniel_Kilsdonk] Daniel Kilsdonk mailto:dan&prospeed.net 2006-08
[David_Clark] David Clark mailto:ddc&lcs.mit.edu
[Didrik_Nordström] Didrik Nordström mailto:didrik.nordstrom&gmail.com 2022-12-02
[Domain_Tech] Domain Tech mailto:Domainnametech&blizzard.com 2005-04
[Epipole_Limited] Epipole Limited mailto:info&epipole.com 2014-11-13
[ExoMachina] ExoMachina mailto:hello&exomachina.com 2011-12-06
[Frank_Waarsenburg] Frank Waarsenburg mailto:frank&eye-display.nl 2004-11
[Jon_Postel] Jon Postel mailto:postel&isi.edu
[Jonathan_Pollock] Jonathan Pollock mailto:jon&arcadiancomputers.com 2016-05-10
[Mark_Caldwell] Mark Caldwell mailto:development&caldsoft.co.uk 2011-08-12
[Mark_Lottor] Mark Lottor mailto:MKL&nisc.sri.com
[Maxim_Mirgorodsky] Maxim Mirgorodsky CommFort software Ltd. mailto:support&commfort.com 2016-03-03
[Patrick_Verbeek] Patrick Verbeek mailto:p.verbeek&scottygroup.com 2007-05
[Rick_Troth] Rick Troth mailto:troth&rice.edu
[Ulli_Horlacher] Ulli Horlacher mailto:framstag&rus.uni-stuttgart.de
[William_Polites] William Polites mailto:wpolites&mitre.org