Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2026-02-02
- 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 47100 | tcp | Reserved | |||||||||
| 47809 | tcp | Reserved | |||||||||
| 48004 | udp | Reserved | |||||||||
| 48005 | udp | Reserved | |||||||||
| 48048 | udp | Reserved | |||||||||
| 48049 | udp | Reserved | |||||||||
| 48050 | udp | Reserved | |||||||||
| 49000 | udp | Reserved | |||||||||
| 49150 | udp | Reserved | |||||||||
| 49151 | Reserved | 2024-12-20 | [RFC6335] | ||||||||
| device-info | Device Info | [Stuart_Cheshire][Marc_Krochmal] | [Stuart_Cheshire][Marc_Krochmal] | Not a service type. Special name reserved for DNS-SD device info. | |||||||
| dns-sd | DNS Service Discovery | [Stuart_Cheshire][Marc_Krochmal] | [Stuart_Cheshire][Marc_Krochmal] | Not a service type. Special name reserved for DNS-SD meta queries. | |||||||
| example | Example Service Type | Not a real service type. Special 'pretend' service types ("_example._udp" and "_example._tcp") reserved for use in illustrative examples in books and other documentation. | |||||||||
| services | DNS Service Discovery | [Stuart_Cheshire][Marc_Krochmal] | [Stuart_Cheshire][Marc_Krochmal] | Not a service type. Special name reserved for DNS-SD meta queries. |
Contact Information
| ID | Name | Contact URI | Last Updated |
|---|---|---|---|
| [Marc_Krochmal] | Marc Krochmal | mailto:marc&apple.com | |
| [Stuart_Cheshire] | Stuart Cheshire | mailto:cheshire&apple.com | 2022-07-11 |