Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2026-09-11
- 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| bgs-nsi | 482 | tcp | bgs-nsi | [Jon_Saperia] | [Jon_Saperia] | ||||||
| bgs-nsi | 482 | udp | bgs-nsi | [Jon_Saperia] | [Jon_Saperia] | ||||||
| miteksys-lm | 1482 | tcp | Miteksys License Manager | [Shane_McRoberts] | [Shane_McRoberts] | ||||||
| miteksys-lm | 1482 | udp | Miteksys License Manager | [Shane_McRoberts] | [Shane_McRoberts] | ||||||
| giop-ssl | 2482 | tcp | Oracle GIOP SSL | ||||||||
| giop-ssl | 2482 | udp | Oracle GIOP SSL | ||||||||
| vulture | 3482 | tcp | Vulture Monitoring System | [Jason_Santos] | [Jason_Santos] | 2002-04 | |||||
| vulture | 3482 | udp | Vulture Monitoring System | [Jason_Santos] | [Jason_Santos] | 2002-04 | |||||
| 4805-4826 | Unassigned | ||||||||||
| htcp | 4827 | tcp | HTCP | [Paul_Vixie] | [Paul_Vixie] | ||||||
| htcp | 4827 | udp | HTCP | [Paul_Vixie] | [Paul_Vixie] | ||||||
| 4828-4836 | Unassigned | ||||||||||
| ldoms-mgmt | 6482 | tcp | Logical Domains Management Interface | [Eric_Sharakan] | [Eric_Sharakan] | 2008-02-14 | |||||
| ldoms-mgmt | 6482 | udp | Logical Domains Management Interface | [Eric_Sharakan] | [Eric_Sharakan] | 2008-02-14 | |||||
| 32401-32482 | Unassigned | ||||||||||
| 37476-37482 | Unassigned |
Contact Information
| ID | Name | Contact URI | Last Updated |
|---|---|---|---|
| [Eric_Sharakan] | Eric Sharakan | mailto:ldoms-iana-ports&sun.com | 2008-02-14 |
| [Jason_Santos] | Jason Santos | mailto:jason.santos&megaslow.net | 2002-04 |
| [Jon_Saperia] | Jon Saperia | mailto:saperia&bgs.com | |
| [Paul_Vixie] | Paul Vixie | mailto:paul&vix.com | |
| [Shane_McRoberts] | Shane McRoberts | mailto:mcroberts&miteksys.com |