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
uarps 219 tcp Unisys ARPs [Ashok_Marwaha] [Ashok_Marwaha]
uarps 219 udp Unisys ARPs [Ashok_Marwaha] [Ashok_Marwaha]
aeroflight-ret 1219 tcp AeroFlight-Ret [Eric_Johnson] [Eric_Johnson]
aeroflight-ret 1219 udp AeroFlight-Ret [Eric_Johnson] [Eric_Johnson]
tivoconnect 2190 tcp TiVoConnect Beacon [Jeffrey_J_Peters] [Jeffrey_J_Peters] 2002-08
tivoconnect 2190 udp TiVoConnect Beacon [Jeffrey_J_Peters] [Jeffrey_J_Peters] 2002-08
tvbus 2191 tcp TvBus Messaging [Brian_W_Beach] [Brian_W_Beach] 2003-01
tvbus 2191 udp TvBus Messaging [Brian_W_Beach] [Brian_W_Beach] 2003-01
asdis 2192 tcp ASDIS software management [ASDIS_Support] [ASDIS_Support] 2005-08
asdis 2192 udp ASDIS software management [ASDIS_Support] [ASDIS_Support] 2005-08
drwcs 2193 tcp Dr.Web Enterprise Management Service [Eugeny_Gladkih] [Eugeny_Gladkih] 2008-01-31
drwcs 2193 udp Dr.Web Enterprise Management Service [Eugeny_Gladkih] [Eugeny_Gladkih] 2008-01-31
2194-2196 Unassigned Unauthorized Use Known on ports 2194-2196
mnp-exchange 2197 tcp MNP data exchange [Peter_Pramberger] [Peter_Pramberger] 2004-11
mnp-exchange 2197 udp MNP data exchange [Peter_Pramberger] [Peter_Pramberger] 2004-11
onehome-remote 2198 tcp OneHome Remote Access
onehome-remote 2198 udp OneHome Remote Access
onehome-help 2199 tcp OneHome Service Port [Jim_Herman] [Jim_Herman] 2005-08
onehome-help 2199 udp OneHome Service Port [Jim_Herman] [Jim_Herman] 2005-08
netiq-ncap 2219 tcp NetIQ NCAP Protocol [Roger_Huebner] [Roger_Huebner] 2010-08-25
netiq-ncap 2219 udp NetIQ NCAP Protocol [Roger_Huebner] [Roger_Huebner] 2010-08-25
wms-messenger 3219 tcp WMS Messenger [WM_Software_Inc.] [WM_Software_Inc.] 2022-07-18
wms-messenger 3219 udp WMS Messenger [WM_Software_Inc.] [WM_Software_Inc.] 2022-07-18
13219-13222 Unassigned
chipper 17219 tcp Chipper [Ronald_Jimmink] [Ronald_Jimmink]
chipper 17219 udp Chipper [Ronald_Jimmink] [Ronald_Jimmink]
19195-19219 Unassigned
21850-21999 Unassigned

Contact Information

ID Name Organization Contact URI Last Updated
[ASDIS_Support] ASDIS Support mailto:support&asdis.de 2005-08
[Ashok_Marwaha] Ashok Marwaha
[Brian_W_Beach] Brian W. Beach mailto:brian&tivo.com 2003-01
[Eric_Johnson] Eric Johnson mailto:eric&gruver.net
[Eugeny_Gladkih] Eugeny Gladkih mailto:john&drweb.com 2008-01-31
[Jeffrey_J_Peters] Jeffrey J. Peters mailto:jpeters&tivo.com 2002-08
[Jim_Herman] Jim Herman mailto:jherman&homelogic.com 2005-08
[Peter_Pramberger] Peter Pramberger mailto:peter.pramberger&telering.co.at 2004-11
[Roger_Huebner] Roger Huebner mailto:iana-ports&netiq.com 2010-08-25
[Ronald_Jimmink] Ronald Jimmink mailto:Ronald.Jimmink&chipper.nl
[WM_Software_Inc.] WM Software Inc. mailto:support&wmsoftware.com 2022-07-18