Service Name and Transport Protocol Port Number Registry

Last Updated

  • 2026-11-19

Expert(s)

  • TCP/UDP: Joe Touch; Eliot Lear, Kumiko Ono, Wes Eddy, Brian Trammell, and Michael Scharf
  • SCTP: Michael Tuexen
  • DCCP: Eddie Kohler and Yoshifumi Nishida

Reference

  • RFC 6335: Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry

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 basis, as described in RFC 6335.

Port numbers are divided into three ranges, with their uses and assignment procedures specified in Section 8.1.2 of RFC 6335:

The registration procedures for service names and port numbers are specified in RFC 6335, while the registration policies referenced above are defined in RFC 8126.

Assigned ports both System and User ports SHOULD NOT be used without or prior to IANA registration.

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.

Registration Forms

Available Formats

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 RFC 3977
nntp 119 udp Network News Transfer Protocol IESG IETF Chair 2018-07-06 RFC 3977
ntp 123 tcp Network Time Protocol Dave Mills Dave Mills RFC 5905
ntp 123 udp Network Time Protocol Dave Mills Dave Mills RFC 5905
nnsp 433 tcp NNTP for transit servers (NNSP) IESG IETF Chair 2018-07-06 RFC 3977
nnsp 433 udp NNTP for transit servers (NNSP) IESG IETF Chair 2018-07-06 RFC 3977
nntps 563 tcp nntp protocol over TLS/SSL (was snntp) IESG IETF Chair 2018-07-06 RFC 4642
nntps 563 udp nntp protocol over TLS/SSL (was snntp) IESG IETF Chair 2018-07-06 RFC 4642
sntp-heartbeat 580 tcp SNTP HEARTBEAT Louis Mamakos Louis Mamakos
sntp-heartbeat 580 udp SNTP HEARTBEAT Louis Mamakos Louis Mamakos
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 The Growl Project Chris Forsythe 2012-02-07

Contact Information

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