Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2024-04-19
- 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 |
---|---|---|---|---|---|---|---|---|---|---|---|
webex | tcp | Cisco WebEx serials products will release Bonjour based service | [Mobile_Team] | [Aulion_Huang] | 2018-02-09 | Defined TXT keys: None | |||||
wifile | tcp | System for transferring files between mobile device and computer in a local network | [Artyom_Nikolaev] | [Artyom_Nikolaev] | 2016-12-23 | Defined TXT keys: None | |||||
wot | tcp | W3C WoT Thing Description or Directory | [W3C_Web_of_Things_Working_Group] | [Kazuyuki_Ashimura] | 2022-11-22 | 2022-12-15 |
Defined TXT keys: td: Absolute pathname of the Thing Description of the Thing or Thing Description of the Thing Description Directory. type: Type of the Thing Description, i.e. "Thing" or "Directory". If omitted, the type is assumed to be Thing. scheme: Scheme part of URL. One of the following values can be specified, with the standard registered URI interpretations [RFC7595]: http (HTTP over TCP),https (HTTP over TLS/TCP), coap+tcp (CoAP over TCP), or coaps+tcp (CoAP over TLS/TCP). If omitted, the scheme is assumed to be http. |
||||
wpl-ers-http | tcp | World Programming repository server | [World_Programming_Limited] | [Thomas_Quarendon] | 2017-03-17 | Defined TXT keys: None | |||||
wpl-ers-zmq | tcp | World Programming repository server | [World_Programming_Limited] | [Thomas_Quarendon] | 2017-03-17 | Defined TXT keys: None | |||||
x510 | tcp | Security service to protocols | [ITU-T_Study_Group_17] | [Erik_Andersen] | 2019-08-13 | Defined TXT keys: None | |||||
xential | tcp | xential document creation services | [Xential] | [Michiel_Terpstra] | 2013-11-13 | Defined TXT keys: None | |||||
xmiserver | tcp | XMI Systems home terminal local connection | [XMI_Systems_SA] | [CLAUDE_MALLY] | 2013-01-18 | Defined TXT keys: coucou | |||||
xul-http | XUL (XML User Interface Language) transported over HTTP | [Eran_Gampel] | [Eran_Gampel] | Defined TXT keys: u=<username> p=<password> path=<path to document> (Same as for _http._tcp) | |||||||
z-wave | tcp | Z-Wave Service Discovery | [Sigma_Designs_Inc] | [Anders_Brandt_2] | 2011-10-03 | Defined TXT keys: NIF, EP, LM | |||||
zeromq | tcp | High performance brokerless messaging | [Daniel_Holth] | [Daniel_Holth] | 2012-04-24 | Defined TXT keys: type, app, label, note | |||||
zigbee-bridge | tcp | ZigBee Bridge device | [ZigBee_Alliances_Network_Device_working_group] | [Leslie_Mulder] | 2013-05-28 | Defined TXT keys: see: http://www.zigbee.org/Standards/ZigBeeNetworkDevices | |||||
zigbee-gateway | tcp | ZigBee IP Gateway | [ZigBee_Alliances_Network_Device_working_group] | [Leslie_Mulder] | 2013-05-28 | Defined TXT keys: see: http://www.zigbee.org/Standards/ZigBeeNetworkDevices |