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
dhcpv6-client 546 udp DHCPv6 Client [IESG] [IETF_Chair] 2018-05-21 [RFC9915]
dhcpv6-server 547 udp DHCPv6 Server [IESG] [IETF_Chair] 2018-05-21 [RFC9915]
915 tcp Reserved
rift-ties 915 udp Routing in Fat Trees Topology Information Element [IESG] [IETF_Chair] 2023-02-17 2024-06-07 [RFC9692]
facelink 1915 tcp FACELINK [J_H_Hermans] [J_H_Hermans]
facelink 1915 udp FACELINK [J_H_Hermans] [J_H_Hermans]
tksocket 2915 tcp TK Socket [Dino_Ciano] [Dino_Ciano] 2011-03-02
tksocket 2915 udp TK Socket [Dino_Ciano] [Dino_Ciano] 2011-03-02
agcat 3915 tcp Auto-Graphics Cataloging [Paul_Cope] [Paul_Cope] 2003-11
agcat 3915 udp Auto-Graphics Cataloging [Paul_Cope] [Paul_Cope] 2003-11
ntske 4460 tcp Network Time Security Key Establishment [IESG] [IETF_Chair] 2020-04-07 [RFC8915]
frcs 4915 tcp Fibics Remote Control Service [Ken_Lagarec] [Ken_Lagarec] 2009-04-17
4915 udp Reserved
5915-5962 Unassigned
9132-9159 Unassigned
inspider 49150 tcp InSpider System [AnRobot] [Zhang_Xinnan] 2017-11-06
49150 udp Reserved
49151 Reserved 2024-12-20 [RFC6335]

Contact Information

ID Name Organization Contact URI Last Updated
[AnRobot] AnRobot mailto:webmaster&anrobot.org 2017-11-06
[Dino_Ciano] Dino Ciano mailto:DCiano&tickets.com 2011-03-02
[IESG] IESG mailto:iesg&ietf.org
[IETF_Chair] IETF Chair IETF mailto:chair&ietf.org
[J_H_Hermans] J.H. Hermans mailto:j.h.hermans&hiscom.nl
[Ken_Lagarec] Ken Lagarec mailto:klagarec&fibics.com 2009-04-17
[Paul_Cope] Paul Cope mailto:prc&auto-graphics.com 2003-11
[Zhang_Xinnan] Zhang Xinnan mailto:70331471&qq.com 2017-11-06