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
netviewdm1 729 tcp IBM NetView DM/6000 Server/Client
netviewdm1 729 udp IBM NetView DM/6000 Server/Client
citynl 1729 tcp CityNL License Management [CityDisc] [CityDisc]
citynl 1729 udp CityNL License Management [CityDisc] [CityDisc]
tcim-control 2729 tcp TCIM Control [Dean_Skelton] [Dean_Skelton]
tcim-control 2729 udp TCIM Control [Dean_Skelton] [Dean_Skelton]
fksp-audit 3729 tcp Fireking Audit Port [Richard_Thurman] [Richard_Thurman] 2003-04
fksp-audit 3729 udp Fireking Audit Port [Richard_Thurman] [Richard_Thurman] 2003-04
ipsec-nat-t 4500 udp IPsec NAT-Traversal 2017-07-07 [RFC3948][RFC7296]
4729 tcp Reserved
gsmtap 4729 udp GSM Interface Tap [Harald_Welte] [Harald_Welte] 2009-01-16
openmail 5729 tcp Openmail User Agent Layer [OpenMail_Encyclopedi][Don_Loughry] [OpenMail_Encyclopedi][Don_Loughry]
openmail 5729 udp Openmail User Agent Layer [OpenMail_Encyclopedi][Don_Loughry] [OpenMail_Encyclopedi][Don_Loughry]
7284-7299 Unassigned
7729-7733 Unassigned
ea 17729 tcp Eclipse Aviation [William_Schmidt] [William_Schmidt] 2006-03
ea 17729 udp Eclipse Aviation [William_Schmidt] [William_Schmidt] 2006-03

Contact Information

ID Name Organization Contact URI Last Updated
[CityDisc] CityDisc mailto:citydisc&euronet.nl
[Dean_Skelton] Dean Skelton mailto:mdskel&ftw.rsc.raytheon.com
[Don_Loughry] Don Loughry mailto:DON_LOUGHRY&hp-cupertino-om4.om.hp.com
[Harald_Welte] Harald Welte mailto:laforge&gnumonks.org 2009-01-16
[OpenMail_Encyclopedi] OpenMail Encyclopedia mailto:opencyc&hpopd.pwd.hp.com
[Richard_Thurman] Richard Thurman mailto:richt&fireking.com 2003-04
[William_Schmidt] William Schmidt mailto:info&eclipseaviation.com 2006-03