Internet Assigned Numbers Authority

Service Name and Transport Protocol Port Number Registry

Last Updated
2022-05-24
Expert(s)
TCP/UDP: Joe Touch; Eliot Lear, Markku Kojo, Kumiko Ono, Martin Stiemerling, 
Wes Eddy, Brian Trammell, Jana Iyengar, 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.                                                   *
************************************************************************
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
sfs-smp-net 451 tcp Cray Network Semaphore server
sfs-smp-net 451 udp Cray Network Semaphore server
infoman 1451 tcp IBM Information Management [Karen_Burns] [Karen_Burns]
infoman 1451 udp IBM Information Management [Karen_Burns] [Karen_Burns]
netchat 2451 tcp netchat [Julian_Mehnle] [Julian_Mehnle]
netchat 2451 udp netchat [Julian_Mehnle] [Julian_Mehnle]
asam 3451 tcp ASAM Services [Mike_Gossett] [Mike_Gossett] 2002-04
asam 3451 udp ASAM Services [Mike_Gossett] [Mike_Gossett] 2002-04
ctisystemmsg 4451 tcp CTI System Msg [Control_Technology_Inc] [Clint_Eskew] 2011-10-28
ctisystemmsg 4451 udp CTI System Msg [Control_Technology_Inc] [Clint_Eskew] 2011-10-28
5451-5452 Unassigned
8451-8456 Unassigned
9451-9499 Unassigned
44446-44543 Unassigned Known UNAUTHORIZED USE: Ports 44515 & 44516

Contact Information

ID Name Organization Contact URI Last Updated
[Clint_Eskew] Clint Eskew Control Technology Inc. mailto:ceskew&controltechnology.com 2011-10-28
[Control_Technology_Inc] Control Technology Inc. mailto:ceskew&controltechnology.com 2011-10-28
[Julian_Mehnle] Julian Mehnle mailto:julian&mehnle.net
[Karen_Burns] Karen Burns
[Mike_Gossett] Mike Gossett mailto:mike&omnibond.com 2002-04