Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2025-06-18
- 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 |
---|---|---|---|---|---|---|---|---|---|---|---|
strobe-sync | tcp | Strobe Synchronization | [Jasper_Morgal] | [Richard_Morgal] | 2019-06-13 | Defined TXT keys: Application will rely upon Bonjour version 3.1.0.1 | |||||
syncqdea | Synchronize! X Plus 2.0 | [Qdea] | [Qdea] | Defined TXT keys: None | |||||||
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]). | ||||
tinavigator | TI Navigator Hub 1.0 Discovery Service | [Stephen_Reid] | [Stephen_Reid] | Defined TXT keys: None | |||||||
x510 | tcp | Security service to protocols | [ITU-T_Study_Group_17] | [Erik_Andersen] | 2019-08-13 | Defined TXT keys: None |
Contact Information
ID | Name | Organization | Contact URI | Last Updated |
---|---|---|---|---|
[Erik_Andersen] | Erik Andersen | mailto:era&x500.eu | 2019-08-13 | |
[IESG] | IESG | mailto:iesg&ietf.org | ||
[IETF_Chair] | IETF Chair | IETF | mailto:chair&ietf.org | |
[ITU-T_Study_Group_17] | ITU-T Study Group 17 | mailto:era&x500.eu | 2019-08-13 | |
[Jasper_Morgal] | Jasper Morgal | mailto:jpmorgal8&gmail.com | 2019-06-13 | |
[Qdea] | Qdea | mailto:support&qdea.com | ||
[Richard_Morgal] | Richard Morgal | mailto:rmorgal&wildblue.net | 2019-06-13 | |
[Stephen_Reid] | Stephen Reid | mailto:sreid&ti.com |