Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2025-09-29
- Expert(s)
-
TCP/UDP: Joe Touch; Eliot Lear, Kumiko Ono, 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. * ************************************************************************
- 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 |
---|---|---|---|---|---|---|---|---|---|---|---|
domain-s | 853 | tcp | DNS query-response protocol run over TLS | [IESG] | [IETF_Chair] | 2015-10-08 | 2022-04-11 | [RFC7858] | |||
domain-s | 853 | udp | DNS query-response protocol run over DTLS or QUIC | [IESG] | [IETF_Chair] | 2015-10-08 | 2022-04-01 | [RFC7858][RFC8094][RFC9250] | |||
vids-avtp | 1853 | tcp | VIDS-AVTP | [Sascha_Kuemmel] | [Sascha_Kuemmel] | ||||||
vids-avtp | 1853 | udp | VIDS-AVTP | [Sascha_Kuemmel] | [Sascha_Kuemmel] | ||||||
ispipes | 2853 | tcp | ISPipes | [Rajesh_Nandyalam] | [Rajesh_Nandyalam] | ||||||
ispipes | 2853 | udp | ISPipes | [Rajesh_Nandyalam] | [Rajesh_Nandyalam] | ||||||
sscan | 3853 | tcp | SONY scanning protocol | [Takashi_Aihara] | [Takashi_Aihara] | 2003-08 | |||||
sscan | 3853 | udp | SONY scanning protocol | [Takashi_Aihara] | [Takashi_Aihara] | 2003-08 | |||||
dtn-bundle | 4556 | dccp | DTN Bundle DCCP CL Protocol | 2013-11-12 | 2014-02-21 | [RFC7122] | 1685351985 | ||||
40853 | tcp | Reserved | |||||||||
ortec-disc | 40853 | udp | ORTEC Service Discovery | [Jesse_Ursery] | [Jesse_Ursery] | 2010-11-22 |
Contact Information
ID | Name | Organization | Contact URI | Last Updated |
---|---|---|---|---|
[IESG] | IESG | mailto:iesg&ietf.org | ||
[IETF_Chair] | IETF Chair | IETF | mailto:chair&ietf.org | |
[Jesse_Ursery] | Jesse Ursery | mailto:jesse.ursery&ametek.com | 2010-11-22 | |
[Rajesh_Nandyalam] | Rajesh Nandyalam | mailto:rnandyal&emc.com | ||
[Sascha_Kuemmel] | Sascha Kuemmel | mailto:kuemmel&vidsoft.de | ||
[Takashi_Aihara] | Takashi Aihara | mailto:aiharat&sm.sony.co.jp | 2003-08 |