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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| mrm | 679 | tcp | MRM | [Liming_Wei] | [Liming_Wei] | ||||||
| mrm | 679 | udp | MRM | [Liming_Wei] | [Liming_Wei] | ||||||
| darcorp-lm | 1679 | tcp | darcorp-lm | [DARcorp] | [DARcorp] | ||||||
| darcorp-lm | 1679 | udp | darcorp-lm | [DARcorp] | [DARcorp] | ||||||
| syncserverssl | 2679 | tcp | Sync Server SSL | [Shawn_Casey] | [Shawn_Casey] | ||||||
| syncserverssl | 2679 | udp | Sync Server SSL | [Shawn_Casey] | [Shawn_Casey] | ||||||
| newton-dock | 3679 | tcp | Newton Dock | [Paul_Guyot] | [Paul_Guyot] | 2025-01-23 | |||||
| newton-dock | 3679 | udp | Newton Dock | [Paul_Guyot] | [Paul_Guyot] | 2025-01-23 | |||||
| mgesupervision | 4679 | tcp | MGE UPS Supervision | ||||||||
| mgesupervision | 4679 | udp | MGE UPS Supervision | ||||||||
| dccm | 5679 | tcp | Direct Cable Connect Manager | [Mark_Miller_2] | [Mark_Miller_2] | ||||||
| dccm | 5679 | udp | Direct Cable Connect Manager | [Mark_Miller_2] | [Mark_Miller_2] | ||||||
| osaut | 6679 | tcp | Osorno Automation | [Peter_Hombach] | [Peter_Hombach] | 2011-03-16 | |||||
| osaut | 6679 | udp | Osorno Automation | [Peter_Hombach] | [Peter_Hombach] | 2011-03-16 | |||||
| hnmp | 6790 | tcp | HNMP | [Jude_George] | [Jude_George] | ||||||
| hnmp | 6790 | udp | HNMP | [Jude_George] | [Jude_George] | ||||||
| hnm | 6791 | tcp | Halcyon Network Manager | [Fortra] | [Henriët_Wilkinson] | 2005-05 | 2023-05-24 | ||||
| hnm | 6791 | udp | Halcyon Network Manager | [Fortra] | [Henriët_Wilkinson] | 2005-05 | 2023-05-24 | ||||
| 6792-6800 | Unassigned | ||||||||||
| 7678-7679 | Unassigned | ||||||||||
| 16790-16899 | Unassigned | ||||||||||
| 24679 | Unassigned | ||||||||||
| 45679-45823 | Unassigned | ||||||||||
| mihcs | MIH Command Services | [RFC5679] | |||||||||
| mihes | MIH Event Services | [RFC5679] | |||||||||
| mihis | MIH Information Services | [RFC5679] |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [DARcorp] | mailto:DARcorp&aol.com | |||
| [Fortra] | Fortra | mailto:info&fortra.com | 2023-05-24 | |
| [Henriët_Wilkinson] | Henriët Wilkinson | mailto:henriet.wilkinson&fortra.com | 2023-05-24 | |
| [Jude_George] | Jude George | mailto:jude&nas.nasa.gov | ||
| [Liming_Wei] | Liming Wei | mailto:lwei&cisco.com | ||
| [Mark_Miller_2] | Mark Miller | mailto:mmillerµsoft.com | ||
| [Paul_Guyot] | Paul Guyot | mailto:pguyot&kallisys.net | 2003-01 | |
| [Peter_Hombach] | Peter Hombach | mailto:p.hombach&osorno.ca | 2011-03-16 | |
| [Shawn_Casey] | Shawn Casey | mailto:Shawn.Casey&matrixone.com |