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
pftp 662 tcp PFTP [Ben_Schluricke] [Ben_Schluricke]
pftp 662 udp PFTP [Ben_Schluricke] [Ben_Schluricke]
netview-aix-2 1662 tcp netview-aix-2
netview-aix-2 1662 udp netview-aix-2
bintec-capi 2662 tcp BinTec-CAPI Unauthorized Use Known on port 2662
bintec-capi 2662 udp BinTec-CAPI Unauthorized Use Known on port 2662
pserver 3662 tcp pserver [Patrick_Furlong] [Patrick_Furlong] 2003-01
pserver 3662 udp pserver [Patrick_Furlong] [Patrick_Furlong] 2003-01
oms 4662 tcp OrbitNet Message Service [Roy_Davies] [Roy_Davies] 2005-08
oms 4662 udp OrbitNet Message Service [Roy_Davies] [Roy_Davies] 2005-08
kftp-data 6620 tcp Kerberos V5 FTP Data [Robert_J_Scott] [Robert_J_Scott] 2005-08
kftp-data 6620 udp Kerberos V5 FTP Data [Robert_J_Scott] [Robert_J_Scott] 2005-08
kftp 6621 tcp Kerberos V5 FTP Control [Robert_J_Scott] [Robert_J_Scott] 2005-08
kftp 6621 udp Kerberos V5 FTP Control [Robert_J_Scott] [Robert_J_Scott] 2005-08
mcftp 6622 tcp Multicast FTP [Bruce_Lueckenhoff_2] [Bruce_Lueckenhoff_2] 2006-02
mcftp 6622 udp Multicast FTP [Bruce_Lueckenhoff_2] [Bruce_Lueckenhoff_2] 2006-02
ktelnet 6623 tcp Kerberos V5 Telnet [Robert_J_Scott] [Robert_J_Scott] 2005-08
ktelnet 6623 udp Kerberos V5 Telnet [Robert_J_Scott] [Robert_J_Scott] 2005-08
datascaler-db 6624 tcp DataScaler database [Vasu_Murthy] [Vasu_Murthy] 2010-02-08
6624 udp Reserved
datascaler-ctl 6625 tcp DataScaler control [Vasu_Murthy] [Vasu_Murthy] 2010-02-08
6625 udp Reserved
wago-service 6626 tcp WAGO Service and Update [Wolfgang_Adler] [Wolfgang_Adler] 2006-04
wago-service 6626 udp WAGO Service and Update [Wolfgang_Adler] [Wolfgang_Adler] 2006-04
nexgen 6627 tcp Allied Electronics NeXGen [Lou_Seitchik] [Lou_Seitchik] 2005-08
nexgen 6627 udp Allied Electronics NeXGen [Lou_Seitchik] [Lou_Seitchik] 2005-08
afesc-mc 6628 tcp AFE Stock Channel M/C [K_K_Ho] [K_K_Ho] 2004-04
afesc-mc 6628 udp AFE Stock Channel M/C [K_K_Ho] [K_K_Ho] 2004-04
nexgen-aux 6629 tcp Secondary, (non ANDI) multi-protocol multi-function interface to the Allied ANDI-based family of forecourt controllers [Allied_Electronics] [Robert_E_Tomenchok_Jr] 2016-11-29
nexgen-aux 6629 udp Secondary, (non ANDI) multi-protocol multi-function interface to the Allied ANDI-based family of forecourt controllers [Allied_Electronics] [Robert_E_Tomenchok_Jr] 2016-11-29
7649-7662 Unassigned
16620-16664 Unassigned

Contact Information

ID Name Organization Contact URI Last Updated
[Allied_Electronics] Allied Electronics mailto:Rob&AlliedElectronics.com 2016-11-29
[Ben_Schluricke] Ben Schluricke mailto:support&pftp.de
[Bruce_Lueckenhoff_2] Bruce Lueckenhoff mailto:bruce&scalabledesign.com 2006-02
[K_K_Ho] K. K Ho mailto:kk.ho&afe-solutions.com 2004-04
[Lou_Seitchik] Lou Seitchik mailto:lou&alliedelectronics.com 2005-08
[Patrick_Furlong] Patrick Furlong mailto:pfurlong&darkknight.ca 2003-01
[Robert_E_Tomenchok_Jr] Robert E. Tomenchok Jr. mailto:Rob&AlliedElectronics.com 2016-11-29
[Robert_J_Scott] Robert J. Scott mailto:rob&hpcmo.hpc.mil 2005-08
[Roy_Davies] Roy Davies mailto:rdavies&daq.net 2005-08
[Vasu_Murthy] Vasu Murthy mailto:vmurthy&datascaler.com 2010-02-08
[Wolfgang_Adler] Wolfgang Adler mailto:electronicc_rd&wago.com 2006-04