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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| cisco-fna | 130 | tcp | cisco FNATIVE | ||||||||
| cisco-fna | 130 | udp | cisco FNATIVE | ||||||||
| casp | 1130 | tcp | CAC App Service Protocol | ||||||||
| casp | 1130 | udp | CAC App Service Protocol | ||||||||
| h323hostcallsc | 1300 | tcp | H.323 Secure Call Control Signalling | [ITU-T] | [ITU-T_TSB] | 2013-01-31 | |||||
| h323hostcallsc | 1300 | udp | H.323 Secure Call Control Signalling | [ITU-T] | [ITU-T_TSB] | 2013-01-31 | |||||
| 1301 | tcp | Reserved | 2019-10-30 | De-Assigned on 2019-10-30 | |||||||
| 1301 | udp | Reserved | 2019-10-30 | De-Assigned on 2019-10-30 | |||||||
| 1302 | tcp | Reserved | 2019-10-30 | De-Assigned on 2019-10-30 | |||||||
| 1302 | udp | Reserved | 2019-10-30 | De-Assigned on 2019-10-30 | |||||||
| sftsrv | 1303 | tcp | sftsrv | [Robert_Frazier] | [Robert_Frazier] | ||||||
| sftsrv | 1303 | udp | sftsrv | [Robert_Frazier] | [Robert_Frazier] | ||||||
| boomerang | 1304 | tcp | Boomerang | [Bruce_Lueckenhoff] | [Bruce_Lueckenhoff] | ||||||
| boomerang | 1304 | udp | Boomerang | [Bruce_Lueckenhoff] | [Bruce_Lueckenhoff] | ||||||
| pe-mike | 1305 | tcp | pe-mike | [Stephen_Hemminger] | [Stephen_Hemminger] | ||||||
| pe-mike | 1305 | udp | pe-mike | [Stephen_Hemminger] | [Stephen_Hemminger] | ||||||
| re-conn-proto | 1306 | tcp | RE-Conn-Proto | [Sandeep_Singhal] | [Sandeep_Singhal] | ||||||
| re-conn-proto | 1306 | udp | RE-Conn-Proto | [Sandeep_Singhal] | [Sandeep_Singhal] | ||||||
| pacmand | 1307 | tcp | Pacmand | [Edward_T_O_Shea] | [Edward_T_O_Shea] | ||||||
| pacmand | 1307 | udp | Pacmand | [Edward_T_O_Shea] | [Edward_T_O_Shea] | ||||||
| odsi | 1308 | tcp | Optical Domain Service Interconnect (ODSI) | [K_Arvind] | [K_Arvind] | ||||||
| odsi | 1308 | udp | Optical Domain Service Interconnect (ODSI) | [K_Arvind] | [K_Arvind] | ||||||
| jtag-server | 1309 | tcp | JTAG server | [Altera_Corporation] | [Kok_Kuan_Chang] | 2026-04-09 | |||||
| jtag-server | 1309 | udp | JTAG server | [Altera_Corporation] | [Kok_Kuan_Chang] | 2026-04-09 | |||||
| xds | 2130 | tcp | XDS | [Peter_Zurich] | [Peter_Zurich] | ||||||
| xds | 2130 | udp | XDS | [Peter_Zurich] | [Peter_Zurich] | ||||||
| icpv2 | 3130 | tcp | ICPv2 | [Duane_Wessels] | [Duane_Wessels] | ||||||
| icpv2 | 3130 | udp | ICPv2 | [Duane_Wessels] | [Duane_Wessels] | ||||||
| fronet | 4130 | tcp | FRONET message protocol | [Christer_Nygren] | [Christer_Nygren] | 2007-08-07 | |||||
| fronet | 4130 | udp | FRONET message protocol | [Christer_Nygren] | [Christer_Nygren] | 2007-08-07 | |||||
| damewaremobgtwy | 6130 | tcp | The DameWare Mobile Gateway Service | [SolarWinds] | [David_Gayler] | 2013-05-29 | |||||
| 6130 | udp | Reserved | |||||||||
| bfd-lag | 6784 | udp | Bidirectional Forwarding Detection (BFD) on Link Aggregation Group (LAG) Interfaces | [IESG] | [BFD_Chairs] | 2012-11-08 | 2014-01-09 | [RFC7130] | |||
| 7130-7160 | Unassigned | ||||||||||
| indigo-vrmi | 8130 | tcp | INDIGO-VRMI | [Colin_Caughie] | [Colin_Caughie] | ||||||
| indigo-vrmi | 8130 | udp | INDIGO-VRMI | [Colin_Caughie] | [Colin_Caughie] | ||||||
| 9124-9130 | Unassigned | ||||||||||
| 10130-10159 | Unassigned | ||||||||||
| 48130-48555 | Unassigned |