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
smartsdp 426 tcp smartsdp [Marie_Pierre_Belange] [Marie_Pierre_Belange]
smartsdp 426 udp smartsdp [Marie_Pierre_Belange] [Marie_Pierre_Belange]
syslog 514 udp 2020-06-01 [RFC5426]
sais 1426 tcp Satellite-data Acquisition System 1 [Bill_Taylor] [Bill_Taylor]
sais 1426 udp Satellite-data Acquisition System 1 [Bill_Taylor] [Bill_Taylor]
vcmp 2426 tcp VeloCloud MultiPath Protocol [VeloCloud_Networks] [Tim_Van_Herck] 2014-11-13 This port was previously removed on 2002-04-29.
vcmp 2426 udp VeloCloud MultiPath Protocol [VeloCloud_Networks] [Tim_Van_Herck] 2014-11-13 This port was previously removed on 2002-04-29.
arkivio 3426 tcp Arkivio Storage Protocol [Bruce_Greenblatt] [Bruce_Greenblatt] 2002-02
arkivio 3426 udp Arkivio Storage Protocol [Bruce_Greenblatt] [Bruce_Greenblatt] 2002-02
beacon-port-2 4426 tcp SMARTS Beacon Port [Eyal_Yardeni] [Eyal_Yardeni] 2003-11
beacon-port-2 4426 udp SMARTS Beacon Port [Eyal_Yardeni] [Eyal_Yardeni] 2003-11
devbasic 5426 tcp DEVBASIC [Curtis_Smith] [Curtis_Smith]
devbasic 5426 udp DEVBASIC [Curtis_Smith] [Curtis_Smith]
pmdmgr 7426 tcp OpenView DM Postmaster Manager [Dave_Lamb] [Dave_Lamb]
pmdmgr 7426 udp OpenView DM Postmaster Manager [Dave_Lamb] [Dave_Lamb]

Contact Information

ID Name Organization Contact URI Last Updated
[Bill_Taylor] Bill Taylor mailto:sais&ssec.wisc.edu
[Bruce_Greenblatt] Bruce Greenblatt mailto:bruce&arkivio.com 2002-02
[Curtis_Smith] Curtis Smith mailto:curtis.smith&vsin.com
[Dave_Lamb] Dave Lamb mailto:rdl&rdl.cnd.hp.com
[Eyal_Yardeni] Eyal Yardeni mailto:eyal.yardeni&smarts.com 2003-11
[Marie_Pierre_Belange] Marie-Pierre Belanger mailto:belanger_marie&emc.com
[Tim_Van_Herck] Tim Van Herck VeloCloud Networks mailto:herckt&velocloud.net 2014-11-13
[VeloCloud_Networks] VeloCloud Networks mailto:ops&velocloud.net 2014-11-13