Service Name and Transport Protocol Port Number Registry

Last Updated
2026-09-02
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
ipx 213 tcp IPX [Don_Provan] [Don_Provan]
ipx 213 udp IPX [Don_Provan] [Don_Provan]
mpc-lifenet 1213 tcp Medtronic/Physio-Control LIFENET [Physio-Control_Inc] [Kevin_Drew] 2014-02-14
mpc-lifenet 1213 udp Medtronic/Physio-Control LIFENET [Physio-Control_Inc] [Kevin_Drew] 2014-02-14
xds 2130 tcp XDS [Peter_Zurich] [Peter_Zurich]
xds 2130 udp XDS [Peter_Zurich] [Peter_Zurich]
avantageb2b 2131 tcp Avantageb2b [Avi_Software] [Avi_Software]
avantageb2b 2131 udp Avantageb2b [Avi_Software] [Avi_Software]
solera-epmap 2132 tcp SoleraTec End Point Map [Mark_Armstrong] [Mark_Armstrong]
solera-epmap 2132 udp SoleraTec End Point Map [Mark_Armstrong] [Mark_Armstrong]
zymed-zpp 2133 tcp ZYMED-ZPP [Gregg_Welker] [Gregg_Welker]
zymed-zpp 2133 udp ZYMED-ZPP [Gregg_Welker] [Gregg_Welker]
avenue 2134 tcp AVENUE [Jason_Cater] [Jason_Cater]
avenue 2134 udp AVENUE [Jason_Cater] [Jason_Cater]
gris 2135 tcp Grid Resource Information Server [Steve_Tuecke] [Steve_Tuecke]
gris 2135 udp Grid Resource Information Server [Steve_Tuecke] [Steve_Tuecke]
appworxsrv 2136 tcp APPWORXSRV [Fred_McLain] [Fred_McLain]
appworxsrv 2136 udp APPWORXSRV [Fred_McLain] [Fred_McLain]
connect 2137 tcp CONNECT [Reid_Ligon] [Reid_Ligon]
connect 2137 udp CONNECT [Reid_Ligon] [Reid_Ligon]
unbind-cluster 2138 tcp UNBIND-CLUSTER [Francois_Harvey] [Francois_Harvey]
unbind-cluster 2138 udp UNBIND-CLUSTER [Francois_Harvey] [Francois_Harvey]
ias-auth 2139 tcp IAS-AUTH
ias-auth 2139 udp IAS-AUTH
kali 2213 tcp Kali [Jay_Cotton] [Jay_Cotton]
kali 2213 udp Kali [Jay_Cotton] [Jay_Cotton]
neon24x7 3213 tcp NEON 24X7 Mission Control [Tony_Lubrano] [Tony_Lubrano]
neon24x7 3213 udp NEON 24X7 Mission Control [Tony_Lubrano] [Tony_Lubrano]
serverstart 9213 tcp ServerStart RemoteControl [Detlef_Rothe] [Detlef_Rothe] 2009-05-15
serverstart 9213 udp ServerStart RemoteControl [Detlef_Rothe] [Detlef_Rothe] 2009-05-15
cohesity-agent 21213 tcp Cohesity backup agents [Cohesity_Inc] [Sashi_Madduri] 2019-08-01
21213 udp Reserved
21222-21336 Unassigned
xahaud 21337 tcp Xahau P2P network protocol [INFTF_MTU] [Bharath_Chari] 2025-10-16 [https://xahau.network]
21337 udp Reserved
21338-21552 Unassigned

Contact Information

ID Name Organization Contact URI Last Updated
[Avi_Software] Avi Software mailto:srobert&logava.com
[Bharath_Chari] Bharath Chari mailto:bharath&inftf.org 2025-10-16
[Cohesity_Inc] Cohesity Inc mailto:support&cohesity.com 2019-08-01
[Detlef_Rothe] Detlef Rothe mailto:detlef.rothe&ts.fujitsu.com 2009-05-15
[Don_Provan] Don Provan mailto:donp&xlnvax.novell.com
[Francois_Harvey] Francois Harvey mailto:securiweb&pandore.qc.ca
[Fred_McLain] Fred McLain mailto:fmclain&appworx.com
[Gregg_Welker] Gregg Welker mailto:greggw&zmi.com
[INFTF_MTU] INFTF MTU mailto:bharath&inftf.org 2025-10-16
[Jason_Cater] Jason Cater mailto:jason&ncsmags.com
[Jay_Cotton] Jay Cotton mailto:JAY&calc.vet.uga.edu
[Kevin_Drew] Kevin Drew Physio-Control, Inc. mailto:kevin.c.drew&physio-control.com 2014-02-14
[Mark_Armstrong] Mark Armstrong mailto:Mark.Armstrong&soleratec.com 2005-12
[Peter_Zurich] Peter Zurich mailto:pbz&lowpft.com
[Physio-Control_Inc] Physio-Control, Inc. mailto:kevin.c.drew&physio-control.com 2014-02-14
[Reid_Ligon] Reid Ligon mailto:reid&connectrf.com
[Sashi_Madduri] Sashi Madduri mailto:sashi&cohesity.com 2019-08-01
[Steve_Tuecke] Steve Tuecke mailto:tuecke&mcs.anl.gov
[Tony_Lubrano] Tony Lubrano mailto:tlubrano&neonsys.com