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
smsp 413 tcp Storage Management Services Protocol [Murthy_Srinivas] [Murthy_Srinivas]
smsp 413 udp Storage Management Services Protocol [Murthy_Srinivas] [Murthy_Srinivas]
innosys-acl 1413 tcp Innosys-ACL [Eric_Welch] [Eric_Welch]
innosys-acl 1413 udp Innosys-ACL [Eric_Welch] [Eric_Welch]
orion-rmi-reg 2413 tcp orion-rmi-reg [J_S_Greenfield_2] [J_S_Greenfield_2]
orion-rmi-reg 2413 udp orion-rmi-reg [J_S_Greenfield_2] [J_S_Greenfield_2]
svnet 3413 tcp SpecView Networking [Richard_Dickins] [Richard_Dickins] 2002-02
svnet 3413 udp SpecView Networking [Richard_Dickins] [Richard_Dickins] 2002-02
fronet 4130 tcp FRONET message protocol [Christer_Nygren] [Christer_Nygren] 2007-08-07
fronet 4130 udp FRONET message protocol [Christer_Nygren] [Christer_Nygren] 2007-08-07
stars 4131 tcp Global Maintech Stars [Harry_Goldschmitt_2] [Harry_Goldschmitt_2] 2007-06
stars 4131 udp Global Maintech Stars [Harry_Goldschmitt_2] [Harry_Goldschmitt_2] 2007-06
nuts-dem 4132 tcp NUTS Daemon

IANA assigned this well-formed service name as a replacement for "nuts_dem".
nuts_dem 4132 tcp NUTS Daemon This entry is an alias to "nuts-dem". This entry is now historic, not usable for use with many common service discovery mechanisms.
nuts-dem 4132 udp NUTS Daemon

IANA assigned this well-formed service name as a replacement for "nuts_dem".
nuts_dem 4132 udp NUTS Daemon This entry is an alias to "nuts-dem". This entry is now historic, not usable for use with many common service discovery mechanisms.
nuts-bootp 4133 tcp NUTS Bootp Server

IANA assigned this well-formed service name as a replacement for "nuts_bootp".
[Martin_Freiss_2] [Martin_Freiss_2]
nuts_bootp 4133 tcp NUTS Bootp Server [Martin_Freiss_2] [Martin_Freiss_2] This entry is an alias to "nuts-bootp". This entry is now historic, not usable for use with many common service discovery mechanisms.
nuts-bootp 4133 udp NUTS Bootp Server

IANA assigned this well-formed service name as a replacement for "nuts_bootp".
[Martin_Freiss_2] [Martin_Freiss_2]
nuts_bootp 4133 udp NUTS Bootp Server [Martin_Freiss_2] [Martin_Freiss_2] This entry is an alias to "nuts-bootp". This entry is now historic, not usable for use with many common service discovery mechanisms.
nifty-hmi 4134 tcp NIFTY-Serve HMI protocol [Ryuichi_Suzuki] [Ryuichi_Suzuki]
nifty-hmi 4134 udp NIFTY-Serve HMI protocol [Ryuichi_Suzuki] [Ryuichi_Suzuki]
cl-db-attach 4135 tcp Classic Line Database Server Attach
cl-db-attach 4135 udp Classic Line Database Server Attach
cl-db-request 4136 tcp Classic Line Database Server Request
cl-db-request 4136 udp Classic Line Database Server Request
cl-db-remote 4137 tcp Classic Line Database Server Remote [Arno_Kirmeir] [Arno_Kirmeir] 2007-01
cl-db-remote 4137 udp Classic Line Database Server Remote [Arno_Kirmeir] [Arno_Kirmeir] 2007-01
nettest 4138 tcp nettest [David_Borman] [David_Borman] 2003-03
nettest 4138 udp nettest [David_Borman] [David_Borman] 2003-03
thrtx 4139 tcp Imperfect Networks Server [Dinkar_Chivaluri_2] [Dinkar_Chivaluri_2] 2006-02
thrtx 4139 udp Imperfect Networks Server [Dinkar_Chivaluri_2] [Dinkar_Chivaluri_2] 2006-02
vision-mon 4413 tcp FORTÉ Vision Monitoring platform [FORTÉ] [Rob_Duram] 2015-09-18 2025-11-14
vision-mon-disc 4413 udp FORTÉ Vision Monitoring platform [FORTÉ] [Rob_Duram] 2015-09-18 2025-11-14
wwiotalk 5413 tcp WWIOTALK [Roger_Knobbe] [Roger_Knobbe]
wwiotalk 5413 udp WWIOTALK [Roger_Knobbe] [Roger_Knobbe]
14251-14413 Unassigned
19413-19538 Unassigned
36413-36421 Unassigned
38413-38421 Unassigned

Contact Information

ID Name Organization Contact URI Last Updated
[Arno_Kirmeir] Arno Kirmeir mailto:Arno.kirmeir&sage.de 2007-01
[Christer_Nygren] Christer Nygren mailto:christer.nygren&fro.se 2007-08-07
[David_Borman] David Borman mailto:david.borman&quantum.com 2015-02-05
[Dinkar_Chivaluri_2] Dinkar Chivaluri mailto:dchivaluri&imperfectnetworks.com 2006-02
[Eric_Welch] Eric Welch
[FORTÉ] FORTÉ mailto:rob.duram&ourforte.com 2025-10-30
[Harry_Goldschmitt_2] Harry Goldschmitt mailto:harry&hgac.com 2007-06
[J_S_Greenfield_2] J.S. Greenfield mailto:greeny&us.ibm.com
[Martin_Freiss_2] Martin Freiss mailto:freiss.pad@sni.
[Murthy_Srinivas] Murthy Srinivas mailto:murthy&novell.com
[Richard_Dickins] Richard Dickins mailto:rad&specview.com 2002-02
[Rob_Duram] Rob Duram mailto:rob.duram&ourforte.com 2025-10-30
[Roger_Knobbe] Roger Knobbe mailto:RogerK&wonderware.com
[Ryuichi_Suzuki] Ryuichi Suzuki mailto:SCI00376&niftyserve.or.jp