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
philips-vc 583 tcp Philips Video-Conferencing [Janna_Chang] [Janna_Chang]
philips-vc 583 udp Philips Video-Conferencing [Janna_Chang] [Janna_Chang]
simbaexpress 1583 tcp simbaexpress [Betsy_Alexander] [Betsy_Alexander]
simbaexpress 1583 udp simbaexpress [Betsy_Alexander] [Betsy_Alexander]
mon 2583 tcp MON [Jim_Trocki] [Jim_Trocki]
mon 2583 udp MON [Jim_Trocki] [Jim_Trocki]
canex-watch 3583 tcp CANEX Watch System [Peter_Kollath] [Peter_Kollath] 2002-08
canex-watch 3583 udp CANEX Watch System [Peter_Kollath] [Peter_Kollath] 2002-08
tmo-icon-sync 5583 tcp T-Mobile SMS Protocol Message 2 [Donghwan_Lim] [Donghwan_Lim] 2008-01-22
tmo-icon-sync 5583 udp T-Mobile SMS Protocol Message 2 [Donghwan_Lim] [Donghwan_Lim] 2008-01-22
joaJewelSuite 6583 tcp JOA Jewel Suite [Bob_Rundle] [Bob_Rundle] 2005-11
joaJewelSuite 6583 udp JOA Jewel Suite [Bob_Rundle] [Bob_Rundle] 2005-11

Contact Information

ID Name Contact URI Last Updated
[Betsy_Alexander] Betsy Alexander tel:+1-604-681-4549
[Bob_Rundle] Bob Rundle mailto:rundle&rundle.com 2005-11
[Donghwan_Lim] Donghwan Lim mailto:donghwan.lim&t-mobile.com 2008-01-22
[Janna_Chang] Janna Chang mailto:janna&pmc.philips.com
[Jim_Trocki] Jim Trocki mailto:trockij&transmeta.com
[Peter_Kollath] Peter Kollath mailto:peter.kollath&canex.sk 2002-08