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
uuidgen 697 tcp UUIDGEN [James_Falkner] [James_Falkner]
uuidgen 697 udp UUIDGEN [James_Falkner] [James_Falkner]
rrisat 1697 tcp rrisat [Allen_Briggs] [Allen_Briggs]
rrisat 1697 udp rrisat [Allen_Briggs] [Allen_Briggs]
oce-snmp-trap 2697 tcp Oce SNMP Trap Port [Peter_Teeuwen] [Peter_Teeuwen]
oce-snmp-trap 2697 udp Oce SNMP Trap Port [Peter_Teeuwen] [Peter_Teeuwen]
nw-license 3697 tcp NavisWorks License System [Tim_Wiegand] [Tim_Wiegand] 2003-02
nw-license 3697 udp NavisWorks License System [Tim_Wiegand] [Tim_Wiegand] 2003-02
5697-5699 Unassigned
ircs-u 6697 tcp Internet Relay Chat via TLS/SSL 2014-02-11 [RFC7194]
6697 udp Reserved 2014-02-11
conductor 6970 tcp Conductor test coordination protocol [George_Neville-Neil] [George_Neville-Neil] 2014-09-18
6970 udp Reserved
conductor-mpx 6970 sctp conductor for multiplex [George_Neville-Neil] [George_Neville-Neil] 2014-07-29
6971-6979 Unassigned
klio 7697 tcp KLIO communications [Helmut_Giritzer_2] [Helmut_Giritzer_2] 2005-08
klio 7697 udp KLIO communications [Helmut_Giritzer_2] [Helmut_Giritzer_2] 2005-08

Contact Information

ID Name Contact URI Last Updated
[Allen_Briggs] Allen Briggs mailto:briggs&access.rrinc.com
[George_Neville-Neil] George Neville-Neil mailto:gnn&neville-neil.com 2014-07-29
[Helmut_Giritzer_2] Helmut Giritzer mailto:helmut.giritzer&o.roteskreuz.at 2005-08
[James_Falkner] James Falkner mailto:james.falkner&sun.com
[Peter_Teeuwen] Peter Teeuwen mailto:ptee&oce.nl
[Tim_Wiegand] Tim Wiegand mailto:tim.wiegand&navisworks.com 2003-02