Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2025-05-05
- Expert(s)
-
TCP/UDP: Joe Touch; Eliot Lear, Kumiko Ono, Wes Eddy, Brian Trammell, Jana Iyengar, 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 |
---|---|---|---|---|---|---|---|---|---|---|---|
lmsocialserver | 1111 | tcp | LM Social Server | [Ron_Lussier] | [Ron_Lussier] | ||||||
lmsocialserver | 1111 | udp | LM Social Server | [Ron_Lussier] | [Ron_Lussier] | ||||||
sgi-soap | 11110 | tcp | Data migration facility (DMF) SOAP is a web server protocol to support remote access to DMF | [SGI] | [John_Sygulla] | 2013-01-07 | |||||
11110 | udp | Reserved | |||||||||
vce | 11111 | tcp | Viral Computing Environment (VCE) | [Fred_Cohen] | [Fred_Cohen] | ||||||
vce | 11111 | udp | Viral Computing Environment (VCE) | [Fred_Cohen] | [Fred_Cohen] | ||||||
dicom | 11112 | tcp | DICOM | [David_Clunie] | [David_Clunie] | 2005-08 | |||||
dicom | 11112 | udp | DICOM | [David_Clunie] | [David_Clunie] | 2005-08 | |||||
11113-11160 | Unassigned | ||||||||||
fs-qos | 41111 | tcp | Foursticks QoS Protocol | [Chee_Kent_Lam] | [Chee_Kent_Lam] | 2002-04 | |||||
fs-qos | 41111 | udp | Foursticks QoS Protocol | [Chee_Kent_Lam] | [Chee_Kent_Lam] | 2002-04 |
Contact Information
ID | Name | Organization | Contact URI | Last Updated |
---|---|---|---|---|
[Chee_Kent_Lam] | Chee Kent Lam | mailto:cklam&foursticks.com | 2002-04 | |
[David_Clunie] | David Clunie | mailto:dclunie&dclunie.com | 2005-08 | |
[Fred_Cohen] | Fred Cohen | mailto:fc&all.net | ||
[John_Sygulla] | John Sygulla | SGI | mailto:jsygulla&sgi.com | 2013-01-07 |
[Ron_Lussier] | Ron Lussier | mailto:coyote&likeminds.com | ||
[SGI] | SGI | mailto:jsygulla&sgi.com | 2013-01-07 |