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
tbrpf 712 tcp TBRPF RFC 3684
tbrpf 712 udp TBRPF RFC 3684
ltp-deepspace 1113 udp Licklider Transmission Protocol 2014-02-21 RFC 5326; RFC 7122
ltp-deepspace 1113 dccp Licklider Transmission Protocol 2013-11-12 2014-02-21 RFC 7122 7107696
registrar 1712 tcp resource monitoring service Ron Lawson Ron Lawson
registrar 1712 udp resource monitoring service Ron Lawson Ron Lawson
aocp 2712 tcp Axapta Object Communication Protocol Jakob Steen Hansen Jakob Steen Hansen
aocp 2712 udp Axapta Object Communication Protocol Jakob Steen Hansen Jakob Steen Hansen
sentinel-ent 3712 tcp Sentinel Enterprise Ian Gordon Ian Gordon 2003-03
sentinel-ent 3712 udp Sentinel Enterprise Ian Gordon Ian Gordon 2003-03
dtn-bundle 4556 udp DTN Bundle UDP CL Protocol 2006-11 2014-02-21 RFC 7122
dtn-bundle 4556 dccp DTN Bundle DCCP CL Protocol 2013-11-12 2014-02-21 RFC 7122 1685351985
4712-4724 Unassigned
5706-5712 Unassigned
7118-7120 Unassigned
virprot-lm 7121 tcp Virtual Prototypes License Manager Victor Galis Victor Galis
virprot-lm 7121 udp Virtual Prototypes License Manager Victor Galis Victor Galis
7122 Unassigned
snif 7123 tcp SNIF End-to-End TLS Relay Control Connection VESvault Corp Jim Zubov 2021-12-24 2026-07-22 draft-zubov-snif-05, Section 4.3
snif 7123 udp SNIF End-to-End TLS Relay over QUIC VESvault Corp Jim Zubov 2026-07-22 2026-07-22 draft-zubov-snif-05, Section 4.4
7124-7127 Unassigned
scenidm 7128 tcp intelligent data manager Paul Ignatius Paul Ignatius 2006-03
scenidm 7128 udp intelligent data manager Paul Ignatius Paul Ignatius 2006-03
scenccs 7129 tcp Catalog Content Search Anil Sharma Anil Sharma 2006-04
scenccs 7129 udp Catalog Content Search Anil Sharma Anil Sharma 2006-04
raqmon-pdu 7744 tcp RAQMON PDU RFC 4712
raqmon-pdu 7744 udp RAQMON PDU RFC 4712
8712-8731 Unassigned

Contact Information

Name Organization Contact URI Last Updated
Anil Sharma anil.sharma&scentric.com 2006-04
Ian Gordon ian&n-genltd.co.uk 2003-03
Jakob Steen Hansen jsh&dk.damgaard.com
Jim Zubov VESvault Corp jz&vesvault.com 2021-12-29
Paul Ignatius paul.ignatius&scentric.com 2006-03
Ron Lawson ronaldl&hpindacx.cup.hp.com
VESvault Corp info&vesvault.com 2021-12-29
Victor Galis galis&satchmo.virtualprototypes.ca