Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2026-09-02
- 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| ibm-mqseries | 1414 | tcp | IBM MQSeries | [Roger_Meli] | [Roger_Meli] | ||||||
| ibm-mqseries | 1414 | udp | IBM MQSeries | [Roger_Meli] | [Roger_Meli] | ||||||
| 14035-14140 | Unassigned | ||||||||||
| vcs-app | 14141 | tcp | VCS Application | [Ming_Xu] | [Ming_Xu] | ||||||
| vcs-app | 14141 | udp | VCS Application | [Ming_Xu] | [Ming_Xu] | ||||||
| icpp | 14142 | tcp | IceWall Cert Protocol | [Tsutomu_Fujinami] | [Tsutomu_Fujinami] | 2005-08 | |||||
| icpp | 14142 | udp | IceWall Cert Protocol | [Tsutomu_Fujinami] | [Tsutomu_Fujinami] | 2005-08 | |||||
| icpps | 14143 | tcp | IceWall Cert Protocol over TLS | [Kenta_Kambara] | [Kenta_Kambara] | 2016-05-24 | |||||
| 14143 | udp | Reserved | |||||||||
| 14144 | Unassigned | ||||||||||
| gcm-app | 14145 | tcp | GCM Application | [Ming_Xu] | [Ming_Xu] | ||||||
| gcm-app | 14145 | udp | GCM Application | [Ming_Xu] | [Ming_Xu] | ||||||
| 14146-14148 | Unassigned | ||||||||||
| vrts-tdd | 14149 | tcp | Veritas Traffic Director | [Sameer_Deokule] | [Sameer_Deokule] | 2002-03 | |||||
| vrts-tdd | 14149 | udp | Veritas Traffic Director | [Sameer_Deokule] | [Sameer_Deokule] | 2002-03 |
Contact Information
| ID | Name | Contact URI | Last Updated |
|---|---|---|---|
| [Kenta_Kambara] | Kenta Kambara | mailto:kenta.kambara&hpe.com | 2016-05-24 |
| [Ming_Xu] | Ming Xu | mailto:ming&veritas.com | |
| [Roger_Meli] | Roger Meli | mailto:rmmeli%25winvmd@vnet.ibm.com | |
| [Sameer_Deokule] | Sameer Deokule | mailto:sameer.deokule&veritas.com | 2002-03 |
| [Tsutomu_Fujinami] | Tsutomu Fujinami | mailto:tsutomu.fujinami&hp.com | 2005-08 |