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
pkix-3-ca-ra 829 tcp PKIX-3 CA/RA [Carlisle_Adams] [Carlisle_Adams]
pkix-3-ca-ra 829 udp PKIX-3 CA/RA [Carlisle_Adams] [Carlisle_Adams]
optika-emedia 1829 tcp Optika eMedia [Daryle_DeBalski] [Daryle_DeBalski]
optika-emedia 1829 udp Optika eMedia [Daryle_DeBalski] [Daryle_DeBalski]
silkp1 2829 tcp silkp1
silkp1 2829 udp silkp1
neteh-ext 3829 tcp Netadmin Systems Event Handler External [Jonas_Krogell] [Jonas_Krogell] 2007-07-10
neteh-ext 3829 udp Netadmin Systems Event Handler External [Jonas_Krogell] [Jonas_Krogell] 2007-07-10
8283-8291 Unassigned
blp3 8292 tcp Bloomberg professional [Albert_Hou] [Albert_Hou] 2006-05
blp3 8292 udp Bloomberg professional [Albert_Hou] [Albert_Hou] 2006-05
hiperscan-id 8293 tcp Hiperscan Identification Service [Thomas_Klose] [Thomas_Klose] 2009-12-15
8293 udp Reserved
blp4 8294 tcp Bloomberg intelligent client [Albert_Hou] [Albert_Hou] 2006-05
blp4 8294 udp Bloomberg intelligent client [Albert_Hou] [Albert_Hou] 2006-05
8295-8299 Unassigned

Contact Information

ID Name Contact URI Last Updated
[Albert_Hou] Albert Hou mailto:ahou1&bloomberg.com 2006-05
[Carlisle_Adams] Carlisle Adams mailto:Cadams&entrust.com
[Daryle_DeBalski] Daryle DeBalski mailto:ddebalski&optika.com
[Jonas_Krogell] Jonas Krogell mailto:jonas.krogell&netadmin.se 2007-07-10
[Thomas_Klose] Thomas Klose mailto:thomas.klose&hiperscan.com 2009-12-15