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
dn6-smm-red 196 tcp DNSIX Session Mgt Module Audit Redir [Lawrence_Lebahn] [Lawrence_Lebahn]
dn6-smm-red 196 udp DNSIX Session Mgt Module Audit Redir [Lawrence_Lebahn] [Lawrence_Lebahn]
netmagic 1196 tcp Network Magic [Nick_Holt] [Nick_Holt] 2005-08
netmagic 1196 udp Network Magic [Nick_Holt] [Nick_Holt] 2005-08
nasmanager 1960 tcp Merit DAC NASmanager [Richard_S_Conto] [Richard_S_Conto]
nasmanager 1960 udp Merit DAC NASmanager [Richard_S_Conto] [Richard_S_Conto]
bts-appserver 1961 tcp BTS APPSERVER [Carl_Obsorn] [Carl_Obsorn]
bts-appserver 1961 udp BTS APPSERVER [Carl_Obsorn] [Carl_Obsorn]
biap-mp 1962 tcp BIAP-MP [Louis_Slothouber] [Louis_Slothouber]
biap-mp 1962 udp BIAP-MP [Louis_Slothouber] [Louis_Slothouber]
webmachine 1963 tcp WebMachine [Tim_Jowers] [Tim_Jowers]
webmachine 1963 udp WebMachine [Tim_Jowers] [Tim_Jowers]
solid-e-engine 1964 tcp SOLID E ENGINE [Ari_Valtanen] [Ari_Valtanen]
solid-e-engine 1964 udp SOLID E ENGINE [Ari_Valtanen] [Ari_Valtanen]
tivoli-npm 1965 tcp Tivoli NPM [Ivana_Cuozzo] [Ivana_Cuozzo]
tivoli-npm 1965 udp Tivoli NPM [Ivana_Cuozzo] [Ivana_Cuozzo]
slush 1966 tcp Slush [Damien_Miller] [Damien_Miller]
slush 1966 udp Slush [Damien_Miller] [Damien_Miller]
sns-quote 1967 tcp SNS Quote [Robert_Ellman] [Robert_Ellman]
sns-quote 1967 udp SNS Quote [Robert_Ellman] [Robert_Ellman]
lipsinc 1968 tcp LIPSinc
lipsinc 1968 udp LIPSinc
lipsinc1 1969 tcp LIPSinc 1 [Robert_Armington] [Robert_Armington]
lipsinc1 1969 udp LIPSinc 1 [Robert_Armington] [Robert_Armington]
2194-2196 Unassigned Unauthorized Use Known on ports 2194-2196
ncu-2 3196 tcp Network Control Unit [Charlie_Hundre] [Charlie_Hundre]
ncu-2 3196 udp Network Control Unit [Charlie_Hundre] [Charlie_Hundre]
4196 Unassigned
ampl-tableproxy 5196 tcp The protocol is used by two programs that exchange "table" data used in the AMPL modeling language [AMPL_Optimization] [David_M_Gay] 2012-05-25
5196 udp Reserved
8196-8198 Unassigned
11878-11966 Unassigned
sysinfo-sp 11967 tcp SysInfo Service Protocol [Mike_Cooper] [Mike_Cooper] 2003-03
sysinfo-sp 11967 udp SysInfo Service Protocol [Mike_Cooper] [Mike_Cooper] 2003-03
11968-11970 Unassigned

Contact Information

ID Name Organization Contact URI Last Updated
[AMPL_Optimization] AMPL Optimization, Inc. mailto:dmg&ampl.com 2012-05-25
[Ari_Valtanen] Ari Valtanen mailto:ari.valtanen&solidtech.com
[Carl_Obsorn] Carl Obsorn mailto:carl_osborn&sabre.com
[Charlie_Hundre] Charlie Hundre mailto:charlie&rdsrv.reco.com.tw
[Damien_Miller] Damien Miller mailto:damien&ibs.com.au
[David_M_Gay] David M. Gay AMPL Optimization, Inc. mailto:dmg&ampl.com 2012-05-25
[Ivana_Cuozzo] Ivana Cuozzo mailto:Ivana.Cuozzo&tivoli.com
[Lawrence_Lebahn] Lawrence Lebahn mailto:DIA3&paxrv-nes.navy.mil
[Louis_Slothouber] Louis Slothouber mailto:lpslot&biap.com 2005-08
[Mike_Cooper] Mike Cooper mailto:mcooper&magnicomp.com 2003-03
[Nick_Holt] Nick Holt mailto:nickh&purenetworks.com 2005-08
[Richard_S_Conto] Richard S. Conto mailto:rsc&merit.edu
[Robert_Armington] Robert Armington mailto:rarmington&lipsinc.com
[Robert_Ellman] Robert Ellman mailto:rellman&calicotech.com
[Tim_Jowers] Tim Jowers mailto:Tim.Jowers&columbiasc.ncr.com