Service Name and Transport Protocol Port Number Registry

Last Updated
2026-09-11
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
DMExpress 32636 udp DMExpress [Arnie_Farrelly] [Arnie_Farrelly]
32637-32766 Unassigned
profinet-rtm 34963 tcp PROFInet RT Multicast [PNO_PROFIBUS_Nutzerorganisation_e.V.] [Dietmar_Bohn] 2004-11 2026-03-16
profinet-rtm 34963 udp PROFInet RT Multicast [PNO_PROFIBUS_Nutzerorganisation_e.V.] [Dietmar_Bohn] 2004-11 2026-03-16
36463-36523 Unassigned
38463-38471 Unassigned
38473-38637 Unassigned
psqlmws 38638 tcp Premier SQL Middleware Server [Brain_Patchwork_DX_LLC] [Ozz_Nixon] 2022-02-15
38638 udp Reserved
38639-38799 Unassigned
vroa 39063 tcp Children's hearing test/Telemedicine [Hearing_Australia] [Dan_Zhou] 2021-12-23
39063 udp Reserved
45967-46335 Unassigned
inedo 46336 tcp Listen port used for Inedo agent communication [Inedo] [Steve_Dennis] 2016-01-12
46336 udp Reserved
46337-46997 Unassigned
49151 Reserved 2024-12-20 [RFC6335]
carddav tcp vCard Extensions to WebDAV (CardDAV) - non-TLS [IESG] [IETF_Chair] 2012-02-17 [RFC6352] This is an extension of the http service. Defined TXT keys: path=<context path>
carddavs tcp vCard Extensions to WebDAV (CardDAV) - over TLS [IESG] [IETF_Chair] 2012-02-17 [RFC6352] This is an extension of the https service. Defined TXT keys: path=<context path>
timezone tcp Time Zone Data Distribution Service - non-TLS [IESG] [IETF_Chair] 2015-08-03 [RFC7808] This is an extension of the http service. Defined TXT keys: path=<context path> (as per Section 6 of [RFC6763]).
timezones tcp Time Zone Data Distribution Service - over TLS [IESG] [IETF_Chair] 2015-08-03 [RFC7808] This is an extension of the https service. Defined TXT keys: path=<context path> (as per Section 6 of [RFC6763]).

Contact Information

ID Name Organization Contact URI Last Updated
[Arnie_Farrelly] Arnie Farrelly mailto:afarrelly&syncsort.com
[Brain_Patchwork_DX_LLC] Brain Patchwork DX, LLC. mailto:specifications&brainpatchworkdx.com 2022-02-15
[Dan_Zhou] Dan Zhou Hearing Australia mailto:dan.zhou&hearing.com.au 2021-12-23
[Dietmar_Bohn] Dietmar Bohn mailto:standards.central-office&profibus.com 2026-03-10
[Hearing_Australia] Hearing Australia mailto:dan.zhou&hearing.com.au 2021-12-23
[IESG] IESG mailto:iesg&ietf.org
[IETF_Chair] IETF Chair IETF mailto:chair&ietf.org
[Inedo] Inedo mailto:support&inedo.com 2016-01-12
[Ozz_Nixon] Ozz Nixon Brain Patchwork DX, LLC. mailto:specifications&bpdx.com 2022-02-15
[PNO_PROFIBUS_Nutzerorganisation_e.V.] PNO – PROFIBUS Nutzerorganisation e.V. mailto:standards.central-office&profibus.com 2026-03-10
[Steve_Dennis] Steve Dennis mailto:sdennis&inedo.com 2016-01-12