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
cadkey-tablet 1400 tcp Cadkey Tablet Daemon [Joe_McCollough] [Joe_McCollough]
cadkey-tablet 1400 udp Cadkey Tablet Daemon [Joe_McCollough] [Joe_McCollough]
scotty-ft 14000 tcp SCOTTY High-Speed Filetransfer [Patrick_Verbeek] [Patrick_Verbeek] 2007-05
scotty-ft 14000 udp SCOTTY High-Speed Filetransfer [Patrick_Verbeek] [Patrick_Verbeek] 2007-05
sua 14001 tcp SUA [Miguel_Angel_Garcia] [Miguel_Angel_Garcia]
sua 14001 udp De-Registered [Miguel_Angel_Garcia] [Miguel_Angel_Garcia] 2001-06-06
sua 14001 sctp SUA [Miguel_Angel_Garcia] [Miguel_Angel_Garcia]
scotty-disc 14002 udp Discovery of a SCOTTY hardware codec board [SCOTTY_Group_SE] [Patrick_Verbeek_2] 2013-01-14
14002 tcp Reserved
14003-14032 Unassigned
pace-licensed 31400 tcp PACE license server [PACE_Anti-Piracy] [Allen_Cronce] 2014-04-28
31400 udp Reserved

Contact Information

ID Name Organization Contact URI Last Updated
[Allen_Cronce] Allen Cronce PACE Anti-Piracy mailto:allen&paceap.com 2014-04-28
[Joe_McCollough] Joe McCollough mailto:joe&cadkey.com
[Miguel_Angel_Garcia] Miguel Angel Garcia mailto:Miguel.A.Garcia&ericsson.com
[PACE_Anti-Piracy] PACE Anti-Piracy mailto:allen&paceap.com 2014-04-28
[Patrick_Verbeek] Patrick Verbeek mailto:p.verbeek&scottygroup.com 2007-05
[Patrick_Verbeek_2] Patrick Verbeek SCOTTY Group SE mailto:p.verbeek&scottygroup.com 2013-01-14
[SCOTTY_Group_SE] SCOTTY Group SE mailto:p.verbeek&scottygroup.com 2013-01-14