Service Name and Transport Protocol Port Number Registry

Last Updated

  • 2026-11-10

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
vacdsm-app 671 tcp VACDSM-APP
vacdsm-app 671 udp VACDSM-APP
netview-aix-11 1671 tcp netview-aix-11
netview-aix-11 1671 udp netview-aix-11
newlixreg 2671 tcp newlixreg Jean-Serge Gagnon Jean-Serge Gagnon
newlixreg 2671 udp newlixreg Jean-Serge Gagnon Jean-Serge Gagnon
efcp 3671 tcp e Field Control (EIBnet) Marc Goossens Marc Goossens 2003-01
efcp 3671 udp e Field Control (EIBnet) Marc Goossens Marc Goossens 2003-01
acter 4671 tcp Bull RSF action server Christian Caudrelier Christian Caudrelier 2006-02
acter 4671 udp Bull RSF action server Christian Caudrelier Christian Caudrelier 2006-02
amqps 5671 tcp amqp protocol over TLS/SSL Ted Ross Ted Ross 2008-03-26
amqps 5671 udp amqp protocol over TLS/SSL Ted Ross Ted Ross 2008-03-26
p4p-portal 6671 tcp P4P Portal Service Chris Griffiths Chris Griffiths 2008-07-28
p4p-portal 6671 udp P4P Portal Service Chris Griffiths Chris Griffiths 2008-07-28
6707-6713 Unassigned
ibprotocol 6714 tcp Internet Backplane Protocol Alessandro Bassi Alessandro Bassi
ibprotocol 6714 udp Internet Backplane Protocol Alessandro Bassi Alessandro Bassi
fibotrader-com 6715 tcp Fibotrader Communications Robert Wetzold Robert Wetzold 2006-01
fibotrader-com 6715 udp Fibotrader Communications Robert Wetzold Robert Wetzold 2006-01
princity-agent 6716 tcp Princity Agent ENSTEAM Sp. z o.o. Tomasz Krakowiak 2014-07-07 2015-07-08
6716 udp Reserved
6717-6766 Unassigned
7669-7671 Unassigned
kca-service 9878 udp The KX509 Kerberized Certificate Issuance Protocol in Use in 2012 IESG IETF Chair 2012-07-12 RFC 6717 Historically, this service has been referred to as "kca_service", but this service name does not meet the registry requirements.
20671-20809 Unassigned

Contact Information

Name Organization Contact URI Last Updated
Alessandro Bassi abassi&cs.utk.edu
Chris Griffiths chris_griffiths&cable.comcast.com 2008-07-28
Christian Caudrelier Christian.Caudrelier&bull.net 2006-02
ENSTEAM Sp. z o.o. support&ensteam.com 2015-07-08
IESG iesg&ietf.org
IETF Chair IETF chair&ietf.org
Jean-Serge Gagnon jsg&newlix.com
Marc Goossens mgoossens&eiba.com 2003-01
Robert Wetzold robert.wetzold&fibotrader.com 2006-01
Ted Ross tross&redhat.com 2008-03-26
Tomasz Krakowiak ENSTEAM Sp. z o.o. tomasz.krakowiak&ensteam.com 2015-07-08