Service Name and Transport Protocol Port Number Registry

Last Updated
2019-08-26
Expert(s)
TCP/UDP: Joe Touch; Eliot Lear, Allison Mankin, Markku Kojo, Kumiko Ono, Martin Stiemerling, 
Lars Eggert, Alexey Melnikov, Wes Eddy, Alexander Zimmermann, Brian Trammell, and Jana Iyengar
SCTP: Allison Mankin and 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 difference uses of these ranges is 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.                                                   *
************************************************************************
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
ssh 22 tcp The Secure Shell (SSH) Protocol [RFC4251] Defined TXT keys: u=<username> p=<password>
ssh 22 udp The Secure Shell (SSH) Protocol [RFC4251] Defined TXT keys: u=<username> p=<password>
ssh 22 sctp SSH [Randall_Stewart] [Randall_Stewart] [RFC4960] Defined TXT keys: u=<username> p=<password>
sshell 614 tcp SSLshell [Simon_J_Gerraty] [Simon_J_Gerraty]
sshell 614 udp SSLshell [Simon_J_Gerraty] [Simon_J_Gerraty]
netconf-ssh 830 tcp NETCONF over SSH [RFC6242]
netconf-ssh 830 udp NETCONF over SSH [RFC6242]
enpp 2968 tcp ENPP [Kazuhito_Gassho] [Kazuhito_Gassho]
enpp 2968 udp ENPP [Kazuhito_Gassho] [Kazuhito_Gassho]
sdo-ssh 3897 tcp Simple Distributed Objects over SSH [Alexander_Philippou] [Alexander_Philippou] 2003-10
sdo-ssh 3897 udp Simple Distributed Objects over SSH [Alexander_Philippou] [Alexander_Philippou] 2003-10
netconf-ch-ssh 4334 tcp NETCONF Call Home (SSH) [IESG] [IETF_Chair] 2016-01-12 [RFC8071]
snmpssh 5161 tcp SNMP over SSH Transport Model [RFC5592]
snmpssh-trap 5162 tcp SNMP Notification over SSH Transport Model [RFC5592] Known Unauthorized Use on port 5162
tl1-ssh 6252 tcp TL1 over SSH [Jim_Humphreys] [Jim_Humphreys] 2008-01-25
tl1-ssh 6252 udp TL1 over SSH [Jim_Humphreys] [Jim_Humphreys] 2008-01-25
ssh-mgmt 17235 tcp SSH Tectia Manager [Ville_Laurikari] [Ville_Laurikari] 2005-08
ssh-mgmt 17235 udp SSH Tectia Manager [Ville_Laurikari] [Ville_Laurikari] 2005-08
sftp-ssh Secure File Transfer Protocol over SSH [Bryan_Cole] [Bryan_Cole] Defined TXT keys: u=<username> p=<password> path=<path>
shifter Window Shifter server protocol [Antoine_Martin] [Antoine_Martin] Defined TXT keys: username The login username to use (optional) ssh_tunnel Whether an SSH tunnel must be used (required) iface The network interface the server is on (required - may be empty) version Software version (required) ID Server Identifier (requried)
ssh tcp SSH Remote Login Protocol [Tatu_Ylonen] [Tatu_Ylonen] Defined TXT keys: u=<username> p=<password>

People

ID Name Organization Contact URI Last Updated
[Alexander_Philippou] Alexander Philippou mailto:alex&noemax.com 2003-10
[Antoine_Martin] Antoine Martin mailto:antoine&nagafix.co.uk 2016-10-05
[Bryan_Cole] Bryan Cole mailto:bryan.cole&teraview.com
[IESG] IESG mailto:iesg&ietf.org
[IETF_Chair] IETF Chair IETF mailto:chair&ietf.org
[Jim_Humphreys] Jim Humphreys mailto:jhumphre&ciena.com 2008-01-29
[Kazuhito_Gassho] Kazuhito Gassho mailto:Gassho.Kasuhito&exc.epson.co.jp
[Randall_Stewart] Randall Stewart IETF TSVWG mailto:rrs&lakerest.net
[Simon_J_Gerraty] Simon J. Gerraty mailto:sjg&quick.com.au
[Tatu_Ylonen] Tatu Ylonen mailto:ylo&cs.hut.fi
[Ville_Laurikari] Ville Laurikari mailto:vlaurika&ssh.com 2005-08