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
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 RFC 4540
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

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