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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| cybercash | 551 | tcp | cybercash | [Donald_E_Eastlake] | [Donald_E_Eastlake] | [RFC1898] | |||||
| cybercash | 551 | udp | cybercash | [Donald_E_Eastlake] | [Donald_E_Eastlake] | [RFC1898] | |||||
| hecmtl-db | 1551 | tcp | HECMTL-DB | [Maxime_Belanger] | [Maxime_Belanger] | ||||||
| hecmtl-db | 1551 | udp | HECMTL-DB | [Maxime_Belanger] | [Maxime_Belanger] | ||||||
| isg-uda-server | 2551 | tcp | ISG UDA Server | [Dror_Harari] | [Dror_Harari] | ||||||
| isg-uda-server | 2551 | udp | ISG UDA Server | [Dror_Harari] | [Dror_Harari] | ||||||
| apcupsd | 3551 | tcp | Apcupsd Information Port | [Riccardo_Facchetti] | [Riccardo_Facchetti] | 2002-07 | |||||
| apcupsd | 3551 | udp | Apcupsd Information Port | [Riccardo_Facchetti] | [Riccardo_Facchetti] | 2002-07 | |||||
| ieee-mih | 4551 | tcp | MIH Services | [RFC5677] | |||||||
| ieee-mih | 4551 | udp | MIH Services | [RFC5677] | |||||||
| avt-profile-1 | 5004 | tcp | RTP media data | [RFC3551][RFC4571] | |||||||
| avt-profile-1 | 5004 | udp | RTP media data | [RFC3551] | |||||||
| avt-profile-1 | 5004 | dccp | RTP media data | [RFC3551][RFC5762] | |||||||
| avt-profile-2 | 5005 | tcp | RTP control protocol | [RFC3551][RFC4571] | |||||||
| avt-profile-2 | 5005 | udp | RTP control protocol | [RFC3551] | |||||||
| avt-profile-2 | 5005 | dccp | RTP control protocol | [RFC3551][RFC5762] | |||||||
| 5551-5552 | Unassigned | ||||||||||
| sum | 6551 | tcp | Software Update Manager | [Jan_Dirven] | [Jan_Dirven] | 2007-12-13 | |||||
| sum | 6551 | udp | Software Update Manager | [Jan_Dirven] | [Jan_Dirven] | 2007-12-13 | |||||
| controlone-con | 7551 | tcp | ControlONE Console signaling | [BYNE] | [Andre_Nazario] | 2014-11-07 | 2017-06-13 | ||||
| 7551 | udp | Reserved | |||||||||
| 45186-45513 | Unassigned | ||||||||||
| cloudcheck | 45514 | tcp | ASSIA CloudCheck WiFi Management System | [ASSIA_Inc] | [Leonardo_Dagum] | 2016-08-29 | |||||
| cloudcheck-ping | 45514 | udp | ASSIA CloudCheck WiFi Management keepalive | [ASSIA_Inc] | [Leonardo_Dagum] | 2016-08-29 | |||||
| 45515-45677 | Unassigned |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Andre_Nazario] | Andre Nazario | mailto:andre.nazario&byne.com.br | 2017-06-13 | |
| [ASSIA_Inc] | ASSIA Inc. | mailto:info&assia-inc.com | 2016-08-29 | |
| [BYNE] | BYNE | mailto:devel&byne.com.br | 2017-06-13 | |
| [Donald_E_Eastlake] | Donald E. Eastlake 3rd | mailto:d3e3e3&gmail.com | ||
| [Dror_Harari] | Dror Harari | mailto:Dror.Harari&isgsoft.com | ||
| [Jan_Dirven] | Jan Dirven | mailto:jan.dirven&agfa.com | 2007-12-13 | |
| [Leonardo_Dagum] | Leonardo Dagum | mailto:ldagum&assia-inc.com | 2016-08-29 | |
| [Maxime_Belanger] | Maxime Belanger | mailto:R173&hec.ca | ||
| [Riccardo_Facchetti] | Riccardo Facchetti | mailto:riccardo&inetcosmos.org | 2002-07 |