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
rrh 753 tcp
rrh 753 udp
predatar-comms 1753 tcp Predatar Comms Service [Silverstring_Ltd] [Ronnie_De_Giorgio] 2011-09-15
1753 udp Reserved
de-spot 2753 tcp de-spot [Sanjay_Parekh] [Sanjay_Parekh]
de-spot 2753 udp de-spot [Sanjay_Parekh] [Sanjay_Parekh]
nattyserver 3753 tcp NattyServer Port [Akira_Saito] [Akira_Saito] 2003-04
nattyserver 3753 udp NattyServer Port [Akira_Saito] [Akira_Saito] 2003-04
simon 4753 tcp Simple Invocation of Methods Over Network (SIMON) [Alexander_Christian] [Alexander_Christian] 2012-04-19
simon-disc 4753 udp Simple Invocation of Methods Over Network (SIMON) Discovery [Alexander_Christian] [Alexander_Christian] 2012-04-19
rasadv 9753 tcp rasadv [Dave_Thaler_2] [Dave_Thaler_2]
rasadv 9753 udp rasadv [Dave_Thaler_2] [Dave_Thaler_2]
tsaf 12753 tcp tsaf port [Andreas_Fehr] [Andreas_Fehr]
tsaf 12753 udp tsaf port [Andreas_Fehr] [Andreas_Fehr]
17730-17753 Unassigned
24728-24753 Unassigned

Contact Information

ID Name Organization Contact URI Last Updated
[Akira_Saito] Akira Saito mailto:admin&kobu.com 2003-04
[Alexander_Christian] Alexander Christian mailto:alexander.christian&root1.de 2012-04-19
[Andreas_Fehr] Andreas Fehr mailto:andreas&mrs.ch
[Dave_Thaler_2] Dave Thaler mailto:dthaler&microsoft.com
[Ronnie_De_Giorgio] Ronnie De Giorgio Silverstring Ltd. mailto:rdegiorgio&silverstring.com 2011-09-15
[Sanjay_Parekh] Sanjay Parekh mailto:spot&digitalenvoy.net
[Silverstring_Ltd] Silverstring Ltd. mailto:rdegiorgio&silverstring.com 2011-09-15