Service Name and Transport Protocol Port Number Registry
- Last Updated
 - 2025-10-30
 - 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 | 
|---|---|---|---|---|---|---|---|---|---|---|---|
| 585 | De-registered | 2006-04-25 | Use of 585 is not recommended, use 993 instead | ||||||||
| iris-lwz | 715 | tcp | IRIS-LWZ | [RFC4993] | |||||||
| iris-lwz | 715 | udp | IRIS-LWZ | [RFC4993] | |||||||
| imaps | 993 | tcp | IMAP over TLS protocol | [IESG] | [IETF_Chair] | 2021-02-22 | [RFC3501][RFC8314][RFC9051] | ||||
| 993 | udp | Reserved | 2021-02-22 | [RFC9051] | |||||||
| snmp-tcp-port | 1993 | tcp | cisco SNMP TCP port | ||||||||
| snmp-tcp-port | 1993 | udp | cisco SNMP TCP port | ||||||||
| veritas-vis1 | 2993 | tcp | VERITAS VIS1 | ||||||||
| veritas-vis1 | 2993 | udp | VERITAS VIS1 | ||||||||
| bv-agent | 3993 | tcp | BindView-Agent | [David_A_Gayler] | [David_A_Gayler] | 2005-08 | |||||
| bv-agent | 3993 | udp | BindView-Agent | [David_A_Gayler] | [David_A_Gayler] | 2005-08 | |||||
| cim-rs | 5993 | tcp | DMTF WBEM CIM REST | [WS_Inc] | [Jim_Davis_2] | 2015-04-24 | |||||
| 5993 | udp | Reserved | |||||||||
| palace-2 | 9993 | tcp | OnLive-2 | [Douglas_Crockford] | [Douglas_Crockford] | ||||||
| palace-2 | 9993 | udp | OnLive-2 | [Douglas_Crockford] | [Douglas_Crockford] | ||||||
| amt-soap-https | 16993 | tcp | Intel(R) AMT SOAP/HTTPS | [David_T_Hines] | [David_T_Hines] | 2005-02 | |||||
| amt-soap-https | 16993 | udp | Intel(R) AMT SOAP/HTTPS | [David_T_Hines] | [David_T_Hines] | 2005-02 | 
Contact Information
| ID | Name | Organization | Contact URI | Last Updated | 
|---|---|---|---|---|
| [David_A_Gayler] | David A. Gayler | mailto:David.Gayler&bindview.com | 2005-08 | |
| [David_T_Hines] | David T. Hines | mailto:david.hines&intel.com | 2005-02 | |
| [Douglas_Crockford] | Douglas Crockford | mailto:douglas&crockford.com | ||
| [IESG] | IESG | mailto:iesg&ietf.org | ||
| [IETF_Chair] | IETF Chair | IETF | mailto:chair&ietf.org | |
| [Jim_Davis_2] | Jim Davis | WS, Inc | mailto:Jim.Davis&ws-inc.com | 2015-04-24 | 
| [WS_Inc] | WS, Inc | mailto:Jim.Davis&ws-inc.com | 2015-04-24 |