Service Name and Transport Protocol Port Number Registry

Last Updated

  • 2026-10-27

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

  • RFC 6335: Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry

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 basis, as described in RFC 6335.

Port numbers are divided into three ranges, with their uses and assignment procedures specified in Section 8.1.2 of RFC 6335:

The registration procedures for service names and port numbers are specified in RFC 6335, while the registration policies referenced above are defined in RFC 8126.

Assigned ports both System and User ports SHOULD NOT be used without or prior to IANA registration.

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.

Registration Forms

Available Formats

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
45055-45184 Unassigned
witsnet 45185 tcp Wire and Wireless transfer on synchroniz Shenzhen Inovance Technology Co., Ltd Yan Yi 2025-03-11
witsnet 45185 udp Wire and Wireless transfer on synchroniz Shenzhen Inovance Technology Co., Ltd Yan Yi 2025-03-11
45186-45513 Unassigned

Contact Information

Name Organization Contact URI Last Updated
Clint Eskew Control Technology Inc. ceskew&controltechnology.com 2011-10-28
Control Technology Inc. ceskew&controltechnology.com 2011-10-28
Julian Mehnle julian&mehnle.net
Karen Burns
Mike Gossett mike&omnibond.com 2002-04
Shenzhen Inovance Technology Co., Ltd yanyi&inovance.com 2025-03-11
Yan Yi yanyi&inovance.com 2025-03-11