Service Name and Transport Protocol Port Number Registry

Last Updated
2026-09-11
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
collaborator 622 tcp Collaborator [Johnson_Davis] [Johnson_Davis]
collaborator 622 udp Collaborator [Johnson_Davis] [Johnson_Davis]
ontime 1622 tcp ontime [Keith_Rhodes] [Keith_Rhodes]
ontime 1622 udp ontime [Keith_Rhodes] [Keith_Rhodes]
metricadbc 2622 tcp MetricaDBC [Russ_Olivant] [Russ_Olivant]
metricadbc 2622 udp MetricaDBC [Russ_Olivant] [Russ_Olivant]
ff-lr-port 3622 tcp FF LAN Redundancy Port [Fieldbus_Foundation] [Fieldbus_Foundation] 2002-10
ff-lr-port 3622 udp FF LAN Redundancy Port [Fieldbus_Foundation] [Fieldbus_Foundation] 2002-10
4622-4645 Unassigned
6210-6221 Unassigned
radmind 6222 tcp Radmind Access Protocol [Patrick_M_McNeal] [Patrick_M_McNeal] 2006-03
radmind 6222 udp Radmind Access Protocol [Patrick_M_McNeal] [Patrick_M_McNeal] 2006-03
6223-6240 Unassigned
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
11601-11622 Unassigned

Contact Information

ID Name Contact URI Last Updated
[Bruce_Lueckenhoff_2] Bruce Lueckenhoff mailto:bruce&scalabledesign.com 2006-02
[Fieldbus_Foundation] Fieldbus Foundation mailto:dave.glanzer&fieldbus.org 2002-10
[Johnson_Davis] Johnson Davis mailto:johnsond&opteamasoft.com
[Keith_Rhodes] Keith Rhodes tel:+1-810-559-5955
[Patrick_M_McNeal] Patrick M McNeal mailto:mcneal&umich.edu 2006-03
[Russ_Olivant] Russ Olivant mailto:russ.olivant&metrica.co.uk