Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2026-09-02
- 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| rmc | 657 | tcp | RMC | [Michael_Schmidt] | [Michael_Schmidt] | ||||||
| rmc | 657 | udp | RMC | [Michael_Schmidt] | [Michael_Schmidt] | ||||||
| fujitsu-mmpdc | 1657 | tcp | fujitsu-mmpdc | [Katsumi_Oomuro] | [Katsumi_Oomuro] | ||||||
| fujitsu-mmpdc | 1657 | udp | fujitsu-mmpdc | [Katsumi_Oomuro] | [Katsumi_Oomuro] | ||||||
| sns-dispatcher | 2657 | tcp | SNS Dispatcher | ||||||||
| sns-dispatcher | 2657 | udp | SNS Dispatcher | ||||||||
| immedianet-bcn | 3657 | tcp | ImmediaNet Beacon | [Bill_Homan] | [Bill_Homan] | 2003-01 | |||||
| immedianet-bcn | 3657 | udp | ImmediaNet Beacon | [Bill_Homan] | [Bill_Homan] | 2003-01 | |||||
| 4647-4657 | Unassigned | ||||||||||
| 6569-6578 | Unassigned | ||||||||||
| affiliate | 6579 | tcp | Affiliate | [David_Catmull] | [David_Catmull] | 2006-01 | |||||
| affiliate | 6579 | udp | Affiliate | [David_Catmull] | [David_Catmull] | 2006-01 | |||||
| 6657 | tcp | Reserved | |||||||||
| palcom-disc | 6657 | udp | PalCom Discovery | [Boris_Magnusson] | [Boris_Magnusson] | 2010-12-06 | |||||
| 33657-33889 | Unassigned |
Contact Information
| ID | Name | Contact URI | Last Updated |
|---|---|---|---|
| [Bill_Homan] | Bill Homan | mailto:bhoman&spanworks.com | 2003-01 |
| [Boris_Magnusson] | Boris Magnusson | mailto:boris&cs.lth.se | 2010-12-06 |
| [David_Catmull] | David Catmull | mailto:uncommon&uncommonplace.com | 2006-01 |
| [Katsumi_Oomuro] | Katsumi Oomuro | mailto:NAE01421&niftyserve.or.jp | |
| [Michael_Schmidt] | Michael Schmidt | mailto:mmaass&us.ibm.com |