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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| manet | 269 | tcp | MANET Protocols | [RFC5498] | |||||||
| manet | 269 | udp | MANET Protocols | [RFC5498] | |||||||
| idfp | 549 | tcp | IDFP | [Ramana_Kovi] | [Ramana_Kovi] | ||||||
| idfp | 549 | udp | IDFP | [Ramana_Kovi] | [Ramana_Kovi] | ||||||
| shivahose | 1549 | tcp | Shiva Hose | ||||||||
| shivasound | 1549 | udp | Shiva Sound | [Kin_Chan] | [Kin_Chan] | ||||||
| ipass | 2549 | tcp | IPASS | [Michael_Fischer] | [Michael_Fischer] | ||||||
| ipass | 2549 | udp | IPASS | [Michael_Fischer] | [Michael_Fischer] | ||||||
| tellumat-nms | 3549 | tcp | Tellumat MDR NMS | [Hennie_van_der_Merwe] | [Hennie_van_der_Merwe] | 2002-07 | |||||
| tellumat-nms | 3549 | udp | Tellumat MDR NMS | [Hennie_van_der_Merwe] | [Hennie_van_der_Merwe] | 2002-07 | |||||
| aegate | 4549 | tcp | Aegate PMR Service | [Nick_Warrington] | [Nick_Warrington] | 2006-03 | |||||
| aegate | 4549 | udp | Aegate PMR Service | [Nick_Warrington] | [Nick_Warrington] | 2006-03 | |||||
| 5476-5499 | Unassigned | ||||||||||
| 5544-5549 | Unassigned | ||||||||||
| apc-6549 | 6549 | tcp | APC 6549 | [American_Power_Conve] | [American_Power_Conve] | ||||||
| apc-6549 | 6549 | udp | APC 6549 | [American_Power_Conve] | [American_Power_Conve] | ||||||
| nls-tl | 7549 | tcp | Network Layer Signaling Transport Layer | [Melinda_Shore] | [Melinda_Shore] | 2006-05 | |||||
| nls-tl | 7549 | udp | Network Layer Signaling Transport Layer | [Melinda_Shore] | [Melinda_Shore] | 2006-05 | |||||
| 10549-10630 | Unassigned |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [American_Power_Conve] | American Power Conversion | mailto:ports&apcc.com | 2002-02 | |
| [Hennie_van_der_Merwe] | Hennie van der Merwe | mailto:hvandermerwe&tellumat.com | 2002-07 | |
| [Kin_Chan] | Kin Chan | mailto:kchan&shiva.com | ||
| [Melinda_Shore] | Melinda Shore | mailto:mshore&cisco.com | 2006-05 | |
| [Michael_Fischer] | Michael Fischer | mailto:otterley&pass.com | ||
| [Nick_Warrington] | Nick Warrington | mailto:nick.warrington&paconsulting.com | 2006-03 | |
| [Ramana_Kovi] | Ramana Kovi | mailto:ramana&kovi.com |