Service Name and Transport Protocol Port Number Registry

Last Updated
2021-06-16
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
nntp 119 tcp Network News Transfer Protocol [IESG] [IETF_Chair] 2018-07-06 [RFC3977]
nntp 119 udp Network News Transfer Protocol [IESG] [IETF_Chair] 2018-07-06 [RFC3977]
ntp 123 tcp Network Time Protocol [Dave_Mills] [Dave_Mills] [RFC5905]
ntp 123 udp Network Time Protocol [Dave_Mills] [Dave_Mills] [RFC5905]
nnsp 433 tcp NNTP for transit servers (NNSP) [IESG] [IETF_Chair] 2018-07-06 [RFC3977]
nnsp 433 udp NNTP for transit servers (NNSP) [IESG] [IETF_Chair] 2018-07-06 [RFC3977]
nntps 563 tcp nntp protocol over TLS/SSL (was snntp) [IESG] [IETF_Chair] 2018-07-06 [RFC4642]
nntps 563 udp nntp protocol over TLS/SSL (was snntp) [IESG] [IETF_Chair] 2018-07-06 [RFC4642]
sntp-heartbeat 580 tcp SNTP HEARTBEAT [Louis_Mamakos_2] [Louis_Mamakos_2]
sntp-heartbeat 580 udp SNTP HEARTBEAT [Louis_Mamakos_2] [Louis_Mamakos_2]
entp 1865 tcp ENTP [Seiko_Epson] [Seiko_Epson]
entp 1865 udp ENTP [Seiko_Epson] [Seiko_Epson]
facsys-ntp 2514 tcp Facsys NTP
facsys-ntp 2514 udp Facsys NTP
lv-frontpanel 3079 tcp LV Front Panel [Darshan_Shah] [Darshan_Shah]
lv-frontpanel 3079 udp LV Front Panel [Darshan_Shah] [Darshan_Shah]
radclientport 3178 tcp Radiance UltraEdge Port [Sri_Subramaniam] [Sri_Subramaniam]
radclientport 3178 udp Radiance UltraEdge Port [Sri_Subramaniam] [Sri_Subramaniam]
trnsprntproxy 3346 tcp Trnsprnt Proxy [Grant_Kirby] [Grant_Kirby]
trnsprntproxy 3346 udp Trnsprnt Proxy [Grant_Kirby] [Grant_Kirby]
mcntp 5418 tcp MCNTP [Heiko_Rupp] [Heiko_Rupp]
mcntp 5418 udp MCNTP [Heiko_Rupp] [Heiko_Rupp]
usicontentpush 7998 udp USI Content Push Service [Prakash_Iyer] [Prakash_Iyer] 2009-08-10
marathontp 8384 udp Marathon Transport Protocol [Inertia_Systemes] [Jasmin_Blouin] 2015-06-11
gntp 23053 tcp Generic Notification Transport Protocol [Growl_Project] [Chris_Forsythe] 2012-02-07

Contact Information

ID Name Organization Contact URI Last Updated
[Chris_Forsythe] Chris Forsythe The Growl Project mailto:chris&growl.info 2012-02-07
[Darshan_Shah] Darshan Shah mailto:darshan.shah&ni.com
[Dave_Mills] Dave Mills mailto:mills&udel.edu
[Grant_Kirby] Grant Kirby mailto:grant_kirby&ccm.al.intel.com
[Growl_Project] The Growl Project mailto:support&growl.info 2012-02-07
[Heiko_Rupp] Heiko Rupp mailto:hwr&pilhuhn.de
[IESG] IESG mailto:iesg&ietf.org
[IETF_Chair] IETF Chair IETF mailto:chair&ietf.org
[Inertia_Systemes] Inertia Systemes mailto:jasmin.blouin&inertiasystemes.com 2015-06-11
[Jasmin_Blouin] Jasmin Blouin Inertia Systemes mailto:jasmin.blouin&inertiasystemes.com 2015-06-11
[Louis_Mamakos_2] Louis Mamakos mailto:louie&uu.net
[Prakash_Iyer] Prakash Iyer mailto:prakash.iyer&intel.com 2009-08-10
[Seiko_Epson] Seiko Epson mailto:Ishida.Hitoshi&exc.epson.co.jp
[Sri_Subramaniam] Sri Subramaniam mailto:sri&radiance.com