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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1783 | Decomissioned Port 04/14/00, ms | [naonao] | [naonao] | ||||||||
| aises | 2783 | tcp | AISES | [Daniel_Grazioli] | [Daniel_Grazioli] | ||||||
| aises | 2783 | udp | AISES | [Daniel_Grazioli] | [Daniel_Grazioli] | ||||||
| bim-pem | 3783 | tcp | Impact Mgr./PEM Gateway | [Walter_G_Giroir] | [Walter_G_Giroir] | 2003-07 | |||||
| bim-pem | 3783 | udp | Impact Mgr./PEM Gateway | [Walter_G_Giroir] | [Walter_G_Giroir] | 2003-07 | |||||
| 4775-4783 | Unassigned | ||||||||||
| 3par-mgmt-ssl | 5783 | tcp | 3PAR Management Service with SSL | [Don_Marselle] | [Don_Marselle] | 2008-03-19 | |||||
| 3par-mgmt-ssl | 5783 | udp | 3PAR Management Service with SSL | [Don_Marselle] | [Don_Marselle] | 2008-03-19 | |||||
| 6779-6783 | Unassigned | ||||||||||
| 7782-7783 | Unassigned | ||||||||||
| vopied | 13783 | tcp | VOPIED Protocol | [Jeff_Holmbeck] | [Jeff_Holmbeck] | ||||||
| vopied | 13783 | udp | VOPIED Protocol | [Jeff_Holmbeck] | [Jeff_Holmbeck] | ||||||
| 27783-27875 | Unassigned |
Contact Information
| ID | Name | Contact URI | Last Updated |
|---|---|---|---|
| [Daniel_Grazioli] | Daniel Grazioli | mailto:dgrazioli&pgaero.co.uk | |
| [Don_Marselle] | Don Marselle | mailto:don.marselle&3par.com | 2008-04-09 |
| [Jeff_Holmbeck] | Jeff Holmbeck | mailto:Jeff.Holmbeck&veritas.com | |
| [Walter_G_Giroir] | Walter G. Giroir | mailto:walt_giroir&bmc.com | 2003-07 |
| [naonao] | mailto:naonao&kikaku.mmp.fujitsu.co.jp |