Service Name and Transport Protocol Port Number Registry

Last Updated
2026-09-11
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
asia 626 tcp ASIA [Michael_Dasenbrock] [Michael_Dasenbrock]
asia 626 udp ASIA [Michael_Dasenbrock] [Michael_Dasenbrock]
shockwave 1626 tcp Shockwave [Sarah_Allen] [Sarah_Allen]
shockwave 1626 udp Shockwave [Sarah_Allen] [Sarah_Allen]
gbjd816 2626 tcp gbjd816 [George_Balesta] [George_Balesta]
gbjd816 2626 udp gbjd816 [George_Balesta] [George_Balesta]
bvcdaemon-port 3626 tcp bvControl Daemon [Ravi_Gokhale] [Ravi_Gokhale] 2002-10
bvcdaemon-port 3626 udp bvControl Daemon [Ravi_Gokhale] [Ravi_Gokhale] 2002-10
5619-5626 Unassigned
6254-6266 Unassigned
gld 6267 tcp GridLAB-D User Interface [David_Chassin] [David_Chassin] 2010-12-10
6267 udp Reserved
grid 6268 tcp Grid Authentication [Jason_Hamilton] [Jason_Hamilton] 2006-06
grid 6268 udp Grid Authentication [Jason_Hamilton] [Jason_Hamilton] 2006-06
grid-alt 6269 tcp Grid Authentication Alt [Jason_Hamilton] [Jason_Hamilton] 2006-06
grid-alt 6269 udp Grid Authentication Alt [Jason_Hamilton] [Jason_Hamilton] 2006-06
wago-service 6626 tcp WAGO Service and Update [Wolfgang_Adler] [Wolfgang_Adler] 2006-04
wago-service 6626 udp WAGO Service and Update [Wolfgang_Adler] [Wolfgang_Adler] 2006-04
simco 7626 tcp SImple Middlebox COnfiguration (SIMCO) Server [RFC4540]
7626 udp De-registered 2006-01-30
simco 7626 sctp SImple Middlebox COnfiguration (SIMCO) [Sebastian_Kiesel] [Sebastian_Kiesel] 2006-01
ezproxy 26260 tcp eZproxy [Albert_C_Yang] [Albert_C_Yang]
ezproxy 26260 udp eZproxy [Albert_C_Yang] [Albert_C_Yang]
ezmeeting 26261 tcp eZmeeting [Albert_C_Yang] [Albert_C_Yang]
ezmeeting 26261 udp eZmeeting [Albert_C_Yang] [Albert_C_Yang]
k3software-svr 26262 tcp K3 Software-Server [Jim_Baldridge] [Jim_Baldridge]
k3software-svr 26262 udp K3 Software-Server [Jim_Baldridge] [Jim_Baldridge]
k3software-cli 26263 tcp K3 Software-Client [Jim_Baldridge] [Jim_Baldridge]
k3software-cli 26263 udp K3 Software-Client [Jim_Baldridge] [Jim_Baldridge]
26264 De-registered 2006-04-06
26265-26485 Unassigned

Contact Information

ID Name Contact URI Last Updated
[Albert_C_Yang] Albert C. Yang mailto:albert.yang&ezmeeting.com 2002-03
[David_Chassin] David Chassin mailto:david.chassin&pnl.gov 2010-12-10
[George_Balesta] George Balesta mailto:George.Baletsa&tfn.com
[Jason_Hamilton] Jason Hamilton mailto:JHamilton&griddatasecurity.com 2006-06
[Jim_Baldridge] Jim Baldridge mailto:jimb&rpower.com
[Michael_Dasenbrock] Michael Dasenbrock mailto:dasenbro&apple.com
[Ravi_Gokhale] Ravi Gokhale mailto:rgokhale&bindview.com 2002-10
[Sarah_Allen] Sarah Allen mailto:sallen&macromedia.com
[Sebastian_Kiesel] Sebastian Kiesel mailto:kiesel&ikr.uni-stuttgart.de 2006-01
[Wolfgang_Adler] Wolfgang Adler mailto:electronicc_rd&wago.com 2006-04