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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| discard | 9 | dccp | Discard | [Eddie_Kohler] | [Eddie_Kohler] | [RFC4340] | 1145656131 | ||||
| monitor | 561 | tcp | |||||||||
| monitor | 561 | udp | |||||||||
| facilityview | 1561 | tcp | facilityview | [Ed_Green] | [Ed_Green] | ||||||
| facilityview | 1561 | udp | facilityview | [Ed_Green] | [Ed_Green] | ||||||
| mosaixcc | 2561 | tcp | MosaixCC | [Steven_Frare] | [Steven_Frare] | ||||||
| mosaixcc | 2561 | udp | MosaixCC | [Steven_Frare] | [Steven_Frare] | ||||||
| bmc-onekey | 3561 | tcp | BMC-OneKey | [Portnoy_Boxman] | [Portnoy_Boxman] | 2002-08 | |||||
| bmc-onekey | 3561 | udp | BMC-OneKey | [Portnoy_Boxman] | [Portnoy_Boxman] | 2002-08 | |||||
| 5606-5617 | Unassigned | ||||||||||
| efr | 5618 | tcp | Fiscal Registering Protocol | [efsta_IT_Services_GmbH] | [Ernst_Bewersdorff] | 2013-08-13 | 2022-02-02 | ||||
| 5618 | udp | Reserved | |||||||||
| 5619-5626 | Unassigned | ||||||||||
| 7561-7562 | Unassigned |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Ed_Green] | Ed Green | mailto:egreen&pmeasuring.com | ||
| [Eddie_Kohler] | Eddie Kohler | IETF dccp WG | mailto:kohler&cs.ucla.edu | |
| [efsta_IT_Services_GmbH] | efsta IT Services GmbH | mailto:admin&efsta.eu | 2022-02-02 | |
| [Ernst_Bewersdorff] | Ernst Bewersdorff | efsta IT Services GmbH | mailto:e.bewersdorff&efsta.eu | 2022-02-02 |
| [Portnoy_Boxman] | Portnoy Boxman | mailto:portnoy_boxman&bmc.com | 2005-01 | |
| [Steven_Frare] | Steven Frare | mailto:stevefr&mosaix.com |