Service Name and Transport Protocol Port Number Registry

Last Updated
2026-08-17
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
[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 different uses of these ranges are 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.                                                   *
************************************************************************

Request an Assignment
  [https://www.iana.org/protocols/apply]

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
iris-xpcs 714 tcp IRIS over XPCS [RFC4992]
iris-xpcs 714 udp IRIS over XPCS [RFC4992]
telnets 992 tcp telnet protocol over TLS/SSL
telnets 992 udp telnet protocol over TLS/SSL
stun-p3 1992 tcp cisco STUN Priority 3 port
stun-p3 1992 udp cisco STUN Priority 3 port
ipsendmsg 1992 tcp IPsendmsg [Bob_Kummerfeld] [Bob_Kummerfeld] This entry records an unassigned but widespread use
ipsendmsg 1992 udp IPsendmsg [Bob_Kummerfeld] [Bob_Kummerfeld] This entry records an unassigned but widespread use
avenyo 2992 tcp Avenyo Server [Bodo_Rueskamp] [Bodo_Rueskamp]
avenyo 2992 udp Avenyo Server [Bodo_Rueskamp] [Bodo_Rueskamp]
bv-ds 3992 tcp BindView-DirectoryServer
bv-ds 3992 udp BindView-DirectoryServer
4992-4998 Unassigned
consul-insight 5992 tcp Consul InSight Security [Arthur_Hillenaar] [Arthur_Hillenaar] 2006-01
consul-insight 5992 udp Consul InSight Security [Arthur_Hillenaar] [Arthur_Hillenaar] 2006-01
8992-8996 Unassigned
9912-9924 Unassigned
xybrid-cloud 9925 tcp XYBRID Cloud [Rx_Networks_Inc_2] [Drew_Davies_2] 2013-04-25
9925 udp Reserved
9926-9949 Unassigned
palace-1 9992 tcp OnLive-1 [Douglas_Crockford] [Douglas_Crockford]
palace-1 9992 udp OnLive-1 [Douglas_Crockford] [Douglas_Crockford]
amt-soap-http 16992 tcp Intel(R) AMT SOAP/HTTP [David_T_Hines] [David_T_Hines] 2005-02
amt-soap-http 16992 udp Intel(R) AMT SOAP/HTTP [David_T_Hines] [David_T_Hines] 2005-02

Contact Information

ID Name Organization Contact URI Last Updated
[Arthur_Hillenaar] Arthur Hillenaar mailto:arthur.hillenaar&consul.com 2006-01
[Bob_Kummerfeld] Bob Kummerfeld mailto:bob&sarad.cs.su.oz.au
[Bodo_Rueskamp] Bodo Rueskamp mailto:iana+spam&pinda.de 2020-06-04
[David_T_Hines] David T. Hines mailto:david.hines&intel.com 2005-02
[Douglas_Crockford] Douglas Crockford mailto:douglas&crockford.com
[Drew_Davies_2] Drew Davies Rx Networks Inc. mailto:ddavies&rxnetworks.com 2013-04-25
[Rx_Networks_Inc_2] Rx Networks Inc. mailto:ddavies&rxnetworks.com 2013-04-25