Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2026-08-17
- 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
1 2
| Service Name | Port Number | Transport Protocol | Description | Assignee | Contact | Registration Date | Modification Date | Reference | Service Code | Unauthorized Use Reported | Assignment Notes |
|---|---|---|---|---|---|---|---|---|---|---|---|
| axio-disc | 35100 | udp | Axiomatic discovery protocol | [Axiomatic_Technologies_Corporation] | [Oleksandr_Bogush] | 2016-12-09 | |||||
| altova-lm-disc | 35355 | udp | Altova License Management Discovery | [Alexander_Falk_2] | [Alexander_Falk_2] | 2011-07-07 | |||||
| crescoctrl-disc | 38002 | udp | Cresco Controller Discovery | [UofK] | [Cody_Bumgardner] | 2014-11-21 | |||||
| ortec-disc | 40853 | udp | ORTEC Service Discovery | [Jesse_Ursery] | [Jesse_Ursery] | 2010-11-22 | |||||
| recvr-rc-disc | 43000 | udp | Receiver Remote Control Discovery | [Research_Electronics_International] | [Ross_Binkley] | 2012-12-20 | |||||
| shaperai-disc | 43210 | udp | Shaper Automation Server Management Discovery | [Shaper_Automation] | [Yohann_Sulaiman] | 2012-06-22 | |||||
| ew-disc-cmd | 43440 | udp | Cisco EnergyWise Discovery and Command Flooding | [John_Parello] | [John_Parello] | 2009-05-19 | |||||
| m3da-disc | 44900 | udp | M3DA Discovery is used for efficient machine-to-machine communications | [Eclipse_Foundation] | [Didier_Lahay] | 2013-02-22 | |||||
| nusdp-disc | 49001 | udp | Nuance Unity Service Discovery Protocol | [Nuance_Communications_Inc3] | [Andrew_Andrews] | 2017-04-20 | |||||
| ai-adp | tcp | AI Agent Discovery Protocol (ADP) | [Harry_Lian] | [Harry_Lian] | 2026-06-12 | [draft-pro-adp-agent-discovery-00] | Defined TXT keys: None | ||||
| egistix | Egistix Auto-Discovery | [Dave_Lindquist_2] | [Dave_Lindquist_2] | Defined TXT keys: None | |||||||
| rapta | tcp | Industrial IOT self-discovery network | [Rapta_Inc] | [Matt_Daue] | 2022-09-22 | Defined TXT keys: version | |||||
| rr-disc | Robot Raconteur discovery | [Wason_Technology_LLC] | [John_Wason] | 2014-01-27 | Defined TXT keys: None | ||||||
| s2connect | tcp | S2 Connect energy management protocol | [TNO] | [Wilco_Wijbrandi] | 2026-03-27 | Defined TXT Keys: [https://docs.s2standard.org/docs/communication-layer/discovery-pairing-authentication/#dns-sd-based-discovery] | |||||
| ss-sign-disc | udp | Samsung Smart Interaction for Group Network Discovery | [Samsung] | [Lee_HoJun] | 2013-01-03 | Defined TXT keys: None | |||||
| twiline-disc | tcp | Discovery for Twiline systems | [W._Wahli_AG] | [Michael_Voser] | 2023-12-04 | Defined TXT keys: txtvers, protovers, caddr, xbusid |
1 2