Service Name and Transport Protocol Port Number Registry

Last Updated
2018-11-06
Expert(s)
TCP/UDP: Joe Touch; Eliot Lear, Allison Mankin, Markku Kojo, Kumiko Ono, Martin Stiemerling, 
Lars Eggert, Alexey Melnikov, Wes Eddy, Alexander Zimmermann, Brian Trammell, and Jana Iyengar
SCTP: Allison Mankin and 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 difference uses of these ranges is 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.                                                   *
************************************************************************
Available Formats

CSV

XML

HTML

Plain text
Service Name Port Number Transport Protocol Description Assignee Contact Registration Date Modification Date Reference Service Code Known Unauthorized Uses Assignment Notes
mdqs 666 tcp
mdqs 666 udp
doom 666 tcp doom Id Software [ddt] [ddt]
doom 666 udp doom Id Software [ddt] [ddt]
netview-aix-6 1666 tcp netview-aix-6
netview-aix-6 1666 udp netview-aix-6
extensis 2666 tcp extensis [Milton_Sagen] [Milton_Sagen]
extensis 2666 udp extensis [Milton_Sagen] [Milton_Sagen]
m3ua 2905 tcp M3UA [Lyndon_Ong] [Lyndon_Ong] [RFC4666]
m3ua 2905 sctp M3UA [Lyndon_Ong] [Lyndon_Ong] [RFC4666]
eserver-pap 3666 tcp IBM eServer PAP [Dave_Gimpl] [Dave_Gimpl] 2003-01
eserver-pap 3666 udp IBM EServer PAP [Dave_Gimpl] [Dave_Gimpl] 2003-01
eportcomm 4666 tcp E-Port Message Service
eportcomm 4666 udp E-Port Message Service
nrpe 5666 tcp Nagios Remote Plugin Executor [Nagios_Enterprises_LLC] [Bryan_Heden] 2017-09-06
5666 udp Reserved
6658-6664 Unassigned Unauthorized Use Known on Port 6659
ircu 6665-6669 tcp IRCU [Brian_Tackett] [Brian_Tackett]
6665-6669 udp Reserved
monetra-admin 8666 tcp Monetra Administrative Access [Main_Street_Softworks] [Brad_House] 2013-04-02
8666 udp Reserved
zoomcp 9666 tcp Zoom Control Panel Game Server Management [Zoom_Control_Panel] [Joshua_Pedroza] 2014-02-26
9666 udp Reserved
16620-16664 Unassigned
axon-tunnel 16665 tcp Reliable multipath data transport for high latencies [Bridgeworks] [Paul_Burgess] 2014-09-26
16665 udp Reserved
16666 tcp Reserved
vtp 16666 udp Vidder Tunnel Protocol [Vidder_Inc] [Ted_Schroeder_2] 2011-10-24
16667-16788 Unassigned
sdtvwcam 24666 tcp Service used by SmarDTV to communicate between a CAM and a second screen application [SmarDTV] [Vincent_Demortier] 2015-03-04
24666 udp Reserved

People

ID Name Organization Contact URI Last Updated
[Brad_House] Brad House Main Street Softworks Inc mailto:brad&mainstreetsoftworks.com 2013-04-02
[Brian_Tackett] Brian Tackett mailto:cym&acrux.net
[Bridgeworks] Bridgeworks mailto:paul.burgess&4bridgeworks.com 2014-09-26
[Bryan_Heden] Bryan Heden mailto:bheden&nagios.com 2017-09-06
[Dave_Gimpl] Dave Gimpl mailto:gimpl&us.ibm.com 2003-01
[Joshua_Pedroza] Joshua Pedroza Zoom Control Panel mailto:info&zoomcp.com 2014-02-26
[Lyndon_Ong] Lyndon Ong mailto:LyOng&ciena.com
[Main_Street_Softworks] Main Street Softworks Inc mailto:info&mainstreetsoftworks.com 2013-04-02
[Milton_Sagen] Milton Sagen mailto:msagen&extensis.com
[Nagios_Enterprises_LLC] Nagios Enterprises, LLC mailto:techteam&nagios.com 2017-09-06
[Paul_Burgess] Paul Burgess Bridgeworks mailto:paul.burgess&4bridgeworks.com 2014-09-26
[SmarDTV] SmarDTV mailto:vincent.demortier&smardtv.com 2015-03-04
[Ted_Schroeder_2] Ted Schroeder Vidder, Inc. mailto:ted&vidder.com 2011-10-24
[Vidder_Inc] Vidder, Inc. mailto:ted&vidder.com 2011-10-24
[Vincent_Demortier] Vincent Demortier SmarDTV mailto:vincent.demortier&smardtv.com 2015-03-04
[Zoom_Control_Panel] Zoom Control Panel mailto:ianaport&zoomcp.com 2014-02-26
[ddt] mailto:ddt&idcube.idsoftware.com