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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| dhcp-failover | 647 | tcp | DHCP Failover | [IESG] | [IETF_Chair] | 2018-05-21 | [RFC8156] | ||||
| dhcp-failover | 647 | udp | DHCP Failover | [Bernard_Volz] | [Bernard_Volz] | ||||||
| rsap | 1647 | tcp | rsap | [Holger_Reif] | [Holger_Reif] | ||||||
| rsap | 1647 | udp | rsap | [Holger_Reif] | [Holger_Reif] | ||||||
| syncserver | 2647 | tcp | SyncServer | [Shawn_Casey] | [Shawn_Casey] | ||||||
| syncserver | 2647 | udp | SyncServer | [Shawn_Casey] | [Shawn_Casey] | ||||||
| splitlock-gw | 3647 | tcp | Splitlock Gateway | [Andrew_Tune] | [Andrew_Tune] | 2003-01 | |||||
| splitlock-gw | 3647 | udp | Splitlock Gateway | [Andrew_Tune] | [Andrew_Tune] | 2003-01 | |||||
| 4647-4657 | Unassigned | ||||||||||
| 5647-5665 | Unassigned | ||||||||||
| 6465-6470 | Unassigned | ||||||||||
| lvision-lm | 6471 | tcp | LVision License Manager | [Brian_McKinnon] | [Brian_McKinnon] | ||||||
| lvision-lm | 6471 | udp | LVision License Manager | [Brian_McKinnon] | [Brian_McKinnon] | ||||||
| 6472-6479 | Unassigned | ||||||||||
| 7634-7647 | Unassigned |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Andrew_Tune] | Andrew Tune | mailto:Andrew.Tune&splitlock.com | 2003-01 | |
| [Bernard_Volz] | Bernard Volz | mailto:bevolz&gmail.com | 2022-08-03 | |
| [Brian_McKinnon] | Brian McKinnon | mailto:bmk&lvision.com | ||
| [Holger_Reif] | Holger Reif | mailto:Holger.Reif&prakinf.tu-ilmenau.de | ||
| [IESG] | IESG | mailto:iesg&ietf.org | ||
| [IETF_Chair] | IETF Chair | IETF | mailto:chair&ietf.org | |
| [Shawn_Casey] | Shawn Casey | mailto:Shawn.Casey&matrixone.com |