Service Name and Transport Protocol Port Number Registry

Last Updated
2021-09-21
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
shell 514 tcp cmd like exec, but automatic authentication is performed as for login server
syslog 514 udp 2020-06-01 [RFC5426]
fujitsu-dtcns 1514 tcp Fujitsu Systems Business of America, Inc [Charles_A_Higgins] [Charles_A_Higgins]
fujitsu-dtcns 1514 udp Fujitsu Systems Business of America, Inc [Charles_A_Higgins] [Charles_A_Higgins]
facsys-ntp 2514 tcp Facsys NTP
facsys-ntp 2514 udp Facsys NTP
must-p2p 3514 tcp MUST Peer to Peer
must-p2p 3514 udp MUST Peer to Peer
5138-5144 Unassigned
rmonitor-secure 5145 tcp RMONITOR SECURE

IANA assigned this well-formed service name as a replacement for "rmonitor_secure".
[Kory_Hamzeh] [Kory_Hamzeh]
rmonitor_secure 5145 tcp RMONITOR SECURE [Kory_Hamzeh] [Kory_Hamzeh] This entry is an alias to "rmonitor-secure". This entry is now historic, not usable for use with many common service discovery mechanisms.
rmonitor-secure 5145 udp RMONITOR SECURE

IANA assigned this well-formed service name as a replacement for "rmonitor_secure".
[Kory_Hamzeh] [Kory_Hamzeh]
rmonitor_secure 5145 udp RMONITOR SECURE [Kory_Hamzeh] [Kory_Hamzeh] This entry is an alias to "rmonitor-secure". This entry is now historic, not usable for use with many common service discovery mechanisms.
social-alarm 5146 tcp Social Alarm Service [Shaun_Byrne] [Shaun_Byrne] 2009-08-18
5146 udp Reserved
5147-5149 Unassigned
syslog-tls 6514 tcp Syslog over TLS [RFC5425]
syslog-tls 6514 udp syslog over DTLS [RFC6012]
syslog-tls 6514 dccp syslog over DTLS [RFC6012]
cloudcheck 45514 tcp ASSIA CloudCheck WiFi Management System [ASSIA_Inc] [Leonardo_Dagum] 2016-08-29
cloudcheck-ping 45514 udp ASSIA CloudCheck WiFi Management keepalive [ASSIA_Inc] [Leonardo_Dagum] 2016-08-29

Contact Information

ID Name Organization Contact URI Last Updated
[ASSIA_Inc] ASSIA Inc. mailto:info&assia-inc.com 2016-08-29
[Charles_A_Higgins] Charles A. Higgins mailto:75730.2257&compuserve.com
[Kory_Hamzeh] Kory Hamzeh mailto:kory&ascend.com
[Leonardo_Dagum] Leonardo Dagum mailto:ldagum&assia-inc.com 2016-08-29
[Shaun_Byrne] Shaun Byrne mailto:s_byrne&tunstall.co.uk 2009-08-18