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
| Service Name | Port Number | Transport Protocol | Description | Assignee | Contact | Registration Date | Modification Date | Reference | Service Code | Unauthorized Use Reported | Assignment Notes |
|---|---|---|---|---|---|---|---|---|---|---|---|
| board-roar | 9700 | udp | Board M.I.T. Service | [Francesco_Rosi] | [Francesco_Rosi] | 2006-01 | |||||
| 9701-9746 | Unassigned | ||||||||||
| l5nas-parchan | 9747 | tcp | L5NAS Parallel Channel | [Lawrence_J_Dickson] | [Lawrence_J_Dickson] | 2002-03 | |||||
| l5nas-parchan | 9747 | udp | L5NAS Parallel Channel | [Lawrence_J_Dickson] | [Lawrence_J_Dickson] | 2002-03 | |||||
| 9748-9749 | Unassigned | ||||||||||
| board-voip | 9750 | tcp | Board M.I.T. Synchronous Collaboration | [Francesco_Rosi] | [Francesco_Rosi] | 2006-01 | |||||
| board-voip | 9750 | udp | Board M.I.T. Synchronous Collaboration | [Francesco_Rosi] | [Francesco_Rosi] | 2006-01 | |||||
| 9751-9752 | Unassigned | ||||||||||
| rasadv | 9753 | tcp | rasadv | [Dave_Thaler_2] | [Dave_Thaler_2] | ||||||
| rasadv | 9753 | udp | rasadv | [Dave_Thaler_2] | [Dave_Thaler_2] | ||||||
| 9754-9761 | Unassigned | ||||||||||
| tungsten-http | 9762 | tcp | WSO2 Tungsten HTTP | [Afkham_Azeez] | [Afkham_Azeez] | 2006-06 | |||||
| tungsten-http | 9762 | udp | WSO2 Tungsten HTTP | [Afkham_Azeez] | [Afkham_Azeez] | 2006-06 | |||||
| 9763-9799 | Unassigned | ||||||||||
| sapv1 | 9875 | tcp | Session Announcement v1 | [RFC2974] | |||||||
| sapv1 | 9875 | udp | Session Announcement v1 | [RFC2974] | |||||||
| 9890-9897 | Unassigned | ||||||||||
| 9967-9977 | Unassigned | ||||||||||
| xybrid-rt | 9978 | tcp | XYBRID RT Server | [Rx_Networks_Inc] | [Drew_Davies] | 2013-01-24 | |||||
| 9978 | udp | Reserved | |||||||||
| visweather | 9979 | tcp | Valley Information Systems Weather station data | [Valley_Information_Systems_Inc] | [Michael_Walsh_2] | 2017-05-12 | |||||
| 9979 | udp | Reserved | |||||||||
| palace-6 | 9997 | tcp | Palace-6 | [Douglas_Crockford] | [Douglas_Crockford] | ||||||
| palace-6 | 9997 | udp | Palace-6 | [Douglas_Crockford] | [Douglas_Crockford] | ||||||
| 11797-11875 | Unassigned | ||||||||||
| 11968-11970 | Unassigned | ||||||||||
| tibsd | 11971 | tcp | TiBS Service | [Teradactyl_LLC] | [Kristen_Webb] | 2019-05-17 | |||||
| 11971 | udp | Reserved | |||||||||
| 11972-11996 | Unassigned | ||||||||||
| wmereceiving | 11997 | sctp | WorldMailExpress | [Greg_Foutz] | [Greg_Foutz] | 2006-03 | |||||
| 15741-15997 | Unassigned | ||||||||||
| 19316-19397 | Unassigned | ||||||||||
| 19542-19787 | Unassigned | ||||||||||
| mle | 19788 | udp | Mesh Link Establishment | [IESG] | [IETF_Chair] | 2012-12-18 | |||||
| 19788 | tcp | Reserved | |||||||||
| 19789 | Unassigned | ||||||||||
| faircom-db | 19790 | tcp | FairCom Database | [FairCom_Corporation] | [Michael_Bowers] | 2020-12-04 | |||||
| 19790 | udp | Reserved | |||||||||
| 19791-19997 | Unassigned | ||||||||||
| 32897-32999 | Unassigned | ||||||||||
| 34967-34979 | Unassigned | ||||||||||
| crestron-ctps | 41797 | tcp | Crestron Secure Terminal Port | [Crestron_Electronics] | [John_Pavlik] | 2012-06-27 | 2019-10-17 | ||||
| 41797 | udp | Reserved | |||||||||
| 46337-46997 | Unassigned | ||||||||||
| brski-reg-cmp | tcp | Bootstrapping Remote Secure Key Infrastructure registrar with CMP capabilities according to the Lightweight CMP Profile (LCMPP) [RFC9483] | [IESG] | [IETF_Chair] | 2024-09-23 | [RFC9733] | Defined TXT keys: None | ||||
| dots-call-home | tcp | DOTS Signal Channel Call Home Protocol. The service name is used to construct the SRV service names "_dots-call-home._udp" and "_dots-call-home._tcp" for discovering Call Home DOTS clients used to establish DOTS signal channel call home. | [IESG] | [IETF_Chair] | 2020-11-19 | [RFC8973] | Defined TXT keys: None | ||||
| dots-call-home | udp | DOTS Signal Channel Call Home Protocol. The service name is used to construct the SRV service names "_dots-call-home._udp" and "_dots-call-home._tcp" for discovering Call Home DOTS clients used to establish DOTS signal channel call home. | [IESG] | [IETF_Chair] | 2020-11-19 | [RFC8973] | Defined TXT keys: None | ||||
| dots-data | tcp | DOTS Data Channel Protocol. The service name is used to construct the SRV service name "_dots-data._tcp" for discovering DOTS servers used to establish DOTS data channel. | [IESG] | [IETF_Chair] | 2020-11-19 | [RFC8973] | Defined TXT keys: None | ||||
| msrps | tcp | MSRP protocol over TLS | 2014-04-25 | [RFC4976] | Defined TXT keys: |