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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| sco-inetmgr | 615 | tcp | Internet Configuration Manager | ||||||||
| sco-inetmgr | 615 | udp | Internet Configuration Manager | ||||||||
| netbill-auth | 1615 | tcp | NetBill Authorization Server | ||||||||
| netbill-auth | 1615 | udp | NetBill Authorization Server | ||||||||
| firepower | 2615 | tcp | firepower | [Jason_Volk] | [Jason_Volk] | ||||||
| firepower | 2615 | udp | firepower | [Jason_Volk] | [Jason_Volk] | ||||||
| start-network | 3615 | tcp | Start Messaging Network | [Peter_Rocca] | [Peter_Rocca] | 2002-10 | |||||
| start-network | 3615 | udp | Start Messaging Network | [Peter_Rocca] | [Peter_Rocca] | 2002-10 | |||||
| 6150-6158 | Unassigned | ||||||||||
| efb-aci | 6159 | tcp | EFB Application Control Interface | [Jonathan_Schaaf] | [Jonathan_Schaaf] | 2010-02-10 | |||||
| 6159 | udp | Reserved | |||||||||
| imink | 8615 | tcp | Imink Service Control | [Canon_Inc] | [KEN_ICHI_FUJII] | 2011-10-10 | |||||
| 8615 | udp | Reserved | |||||||||
| 9615 | Unassigned |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Canon_Inc] | Canon Inc. | mailto:fujii.ken-ichi149&canon.co.jp | 2011-10-10 | |
| [Jason_Volk] | Jason Volk | mailto:jason&teknidude.com | ||
| [Jonathan_Schaaf] | Jonathan Schaaf | mailto:j.schaaf&astronautics.com | 2010-02-10 | |
| [KEN_ICHI_FUJII] | Ken'ichi FUJII | Canon Inc. | mailto:fujii.ken-ichi149&canon.co.jp | 2011-10-10 |
| [Peter_Rocca] | Peter Rocca | mailto:rocca&multiboard.com | 2002-10 |