Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2024-08-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 |
---|---|---|---|---|---|---|---|---|---|---|---|
ctf | 84 | tcp | Common Trace Facility | [Hugh_Thomas] | [Hugh_Thomas] | ||||||
ctf | 84 | udp | Common Trace Facility | [Hugh_Thomas] | [Hugh_Thomas] | ||||||
di-traceware | 3041 | tcp | di-traceware | [Carlos_Hung] | [Carlos_Hung] | ||||||
di-traceware | 3041 | udp | di-traceware | [Carlos_Hung] | [Carlos_Hung] | ||||||
rtraceroute | 3765 | tcp | Remote Traceroute | [A_Blake_Cooper] | [A_Blake_Cooper] | 2003-06 | |||||
rtraceroute | 3765 | udp | Remote Traceroute | [A_Blake_Cooper] | [A_Blake_Cooper] | 2003-06 | |||||
clever-ctrace | 6687 | tcp | CleverView for cTrace Message Service | [David_Cheng] | [David_Cheng] | 2010-02-01 | |||||
speedtrace | 33334 | tcp | SpeedTrace TraceAgent | [Holger_Heinrich] | [Holger_Heinrich] | 2012-02-01 | |||||
speedtrace-disc | 33334 | udp | SpeedTrace TraceAgent Discovery | [Holger_Heinrich] | [Holger_Heinrich] | 2012-02-01 | |||||
traceroute | 33434 | tcp | traceroute use | [IANA] | [IANA] | ||||||
traceroute | 33434 | udp | traceroute use | [IANA] | [IANA] | ||||||
mtrace | 33435 | udp | IP Multicast Traceroute | [IESG] | [IETF_Chair] | 2017-12-13 | 2019-08-09 | [RFC8487] | Known Unauthorized Use on port 33435 | ||
dccp-ping | dccp | ping/traceroute using DCCP | [Samuel_Jero] | [Samuel_Jero] | 2012-11-14 | 1885957735 | Defined TXT keys: None |
Contact Information
ID | Name | Organization | Contact URI | Last Updated |
---|---|---|---|---|
[A_Blake_Cooper] | A. Blake Cooper | mailto:blake&cluebie.net | 2003-06 | |
[Carlos_Hung] | Carlos Hung | mailto:chung&digisle.net | ||
[David_Cheng] | David Cheng | mailto:davec&aesclever.com | 2010-02-01 | |
[Holger_Heinrich] | Holger Heinrich | mailto:holger2222&googlemail.com | 2012-02-01 | |
[Hugh_Thomas] | Hugh Thomas | mailto:thomas&oils.enet.dec.com | ||
[IANA] | IANA | mailto:iana&iana.org | ||
[IESG] | IESG | mailto:iesg&ietf.org | ||
[IETF_Chair] | IETF Chair | IETF | mailto:chair&ietf.org | |
[Samuel_Jero] | Samuel Jero | mailto:sj323707&ohio.edu | 2012-11-14 |