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
oob-ws-https 664 tcp DMTF out-of-band secure web services management protocol [Jim_Davis] [Jim_Davis] 2007-06
asf-secure-rmcp 664 udp ASF Secure Remote Management and Control Protocol [Carl_First] [Carl_First]
netview-aix-4 1664 tcp netview-aix-4
netview-aix-4 1664 udp netview-aix-4
patrol-mq-gm 2664 tcp Patrol for MQ GM
patrol-mq-gm 2664 udp Patrol for MQ GM
ups-engine 3664 tcp UPS Engine Port
ups-engine 3664 udp UPS Engine Port
ems 4664 tcp Rimage Messaging Server [David_V_Raskin] [David_V_Raskin] 2006-02
ems 4664 udp Rimage Messaging Server [David_V_Raskin] [David_V_Raskin] 2006-02
ovsdb 6640 tcp Open vSwitch Database protocol [Bruce_Davie_2] [Bruce_Davie_2] 2013-07-31 [RFC7047]
6640 udp Reserved
6641-6652 Unassigned
6658-6664 Unassigned Unauthorized Use Known on Port 6659
7664-7667 Unassigned
8616-8664 Unassigned Unauthorized Use Known on ports 8616 and 8617
16620-16664 Unassigned
nfs-domainroot tcp NFS service for the domain root, the root of an organization's published file namespace. [IESG] [IETF_Chair] 2012-04-24 [RFC6641] Defined TXT keys: None

Contact Information

ID Name Organization Contact URI Last Updated
[Bruce_Davie_2] Bruce Davie mailto:bdavie&vmware.com 2013-07-31
[Carl_First] Carl First mailto:Carl.L.First&intel.com
[David_V_Raskin] David V. Raskin mailto:draskin&rimage.com 2006-02
[IESG] IESG mailto:iesg&ietf.org
[IETF_Chair] IETF Chair IETF mailto:chair&ietf.org
[Jim_Davis] Jim Davis mailto:jim.davis&wbemsolutions.com 2007-06