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
vatp 690 tcp Velneo Application Transfer Protocol [Velneo] [David_Gutierrez] 2015-02-03
vatp 690 udp Velneo Application Transfer Protocol [Velneo] [David_Gutierrez] 2015-02-03
ng-umds 1690 tcp ng-umds [Louis_E_Simard] [Louis_E_Simard]
ng-umds 1690 udp ng-umds [Louis_E_Simard] [Louis_E_Simard]
hp-nnm-data 2690 tcp HP NNM Embedded Database [Chris_Das] [Chris_Das]
hp-nnm-data 2690 udp HP NNM Embedded Database [Chris_Das] [Chris_Das]
svn 3690 tcp Subversion [Greg_Hudson_2] [Greg_Hudson_2] 2003-01
svn 3690 udp Subversion [Greg_Hudson_2] [Greg_Hudson_2] 2003-01
prelude 4690 tcp Prelude IDS message proto [Yoann_Vandoorselaere] [Yoann_Vandoorselaere] 2005-08
prelude 4690 udp Prelude IDS message proto [Yoann_Vandoorselaere] [Yoann_Vandoorselaere] 2005-08
5690-5692 Unassigned
cleverdetect 6690 tcp CLEVERDetect Message Service [Applied_Expert_Systems_Inc] [David_Cheng] 2014-12-03
6690 udp Reserved
rtimeviewer 6900 tcp R*TIME Viewer Data Interface [Curtiss-Wright_Corporation] [Robert_Ammon] 2016-12-14
6900 udp Reserved
jetstream 6901 tcp Novell Jetstream messaging protocol [Anil_Tyagi] [Anil_Tyagi] 2010-06-11
6901 udp Reserved
6902-6923 Unassigned
sovd 7690 tcp Service-Oriented Vehicle Diagnostics [ASAM_e_V] [Bernd_Wenzel] 2022-07-01
7690 udp Reserved
newbay-snc-mc 16900 tcp Newbay Mobile Client Update Service [Srinivasa_Nayudu] [Srinivasa_Nayudu] 2009-07-06
newbay-snc-mc 16900 udp Newbay Mobile Client Update Service [Srinivasa_Nayudu] [Srinivasa_Nayudu] 2009-07-06
16901-16949 Unassigned

Contact Information

ID Name Organization Contact URI Last Updated
[Anil_Tyagi] Anil Tyagi mailto:tanil&novell.com 2010-06-11
[Applied_Expert_Systems_Inc] Applied Expert Systems, Inc. mailto:davec&aesclever.com 2014-12-03
[ASAM_e_V] ASAM e.V. mailto:marius.dupuis&asam.net 2022-07-01
[Bernd_Wenzel] Bernd Wenzel ASAM e.V. mailto:bernd.wenzel&asam.net 2022-07-01
[Chris_Das] Chris Das mailto:cdas&cnd.hp.com
[Curtiss-Wright_Corporation] Curtiss-Wright Corporation mailto:rammon&curtisswright.com 2016-12-14
[David_Cheng] David Cheng mailto:davec&aesclever.com 2010-02-01
[David_Gutierrez] David GutiƩrrez Velneo mailto:velneo&velneo.com 2015-02-03
[Greg_Hudson_2] Greg Hudson mailto:ghudson&mit.edu 2023-11-17
[Louis_E_Simard] Louis E. Simard mailto:76400.3371&compuserve.com
[Robert_Ammon] Robert Ammon mailto:rammon&curtisswright.com 2016-12-14
[Srinivasa_Nayudu] Srinivasa Nayudu mailto:sn156n&att.com 2009-07-06
[Velneo] Velneo mailto:velneo&velneo.com
[Yoann_Vandoorselaere] Yoann Vandoorselaere mailto:yoann&prelude-ids.org 2005-08