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
1 2
Service Name | Port Number | Transport Protocol | Description | Assignee | Contact | Registration Date | Modification Date | Reference | Service Code | Unauthorized Use Reported | Assignment Notes |
---|---|---|---|---|---|---|---|---|---|---|---|
3par-mgmt-ssl | 5783 | udp | 3PAR Management Service with SSL | [Don_Marselle] | [Don_Marselle] | 2008-03-19 | |||||
wsmans | 5986 | tcp | WBEM WS-Management HTTP over TLS/SSL | [Jim_Davis] | [Jim_Davis] | 2006-11 | |||||
wsmans | 5986 | udp | WBEM WS-Management HTTP over TLS/SSL | [Jim_Davis] | [Jim_Davis] | 2006-11 | |||||
tl1-raw-ssl | 6251 | tcp | TL1 Raw Over SSL/TLS | [Jim_Humphreys] | [Jim_Humphreys] | 2008-01-29 | |||||
tl1-raw-ssl | 6251 | udp | TL1 Raw Over SSL/TLS | [Jim_Humphreys] | [Jim_Humphreys] | 2008-01-29 | |||||
odette-ftps | 6619 | tcp | ODETTE-FTP over TLS/SSL | [Ieuan_Friend] | [Ieuan_Friend] | 2006-03 | [RFC5024] | ||||
odette-ftps | 6619 | udp | ODETTE-FTP over TLS/SSL | [Ieuan_Friend] | [Ieuan_Friend] | 2006-03 | [RFC5024] | ||||
ircs-u | 6697 | tcp | Internet Relay Chat via TLS/SSL | 2014-02-11 | [RFC7194] | ||||||
imqstomps | 7673 | tcp | iMQ STOMP Server over SSL | [Amy_Kang] | [Amy_Kang] | 2009-03-10 | |||||
imqtunnels | 7674 | tcp | iMQ SSL tunnel | [Shailesh_S_Bavadeka] | [Shailesh_S_Bavadeka] | 2002-04 | |||||
imqtunnels | 7674 | udp | iMQ SSL tunnel | [Shailesh_S_Bavadeka] | [Shailesh_S_Bavadeka] | 2002-04 | |||||
sunwebadmins | 8989 | tcp | Sun Web Server SSL Admin Service | [Jyri_J_Virkki] | [Jyri_J_Virkki] | 2005-12 | |||||
sunwebadmins | 8989 | udp | Sun Web Server SSL Admin Service | [Jyri_J_Virkki] | [Jyri_J_Virkki] | 2005-12 | |||||
sqlexec-ssl | 9089 | tcp | IBM Informix SQL Interface - Encrypted | [Jonathan_Leffler] | [Jonathan_Leffler] | 2005-12 | |||||
sqlexec-ssl | 9089 | udp | IBM Informix SQL Interface - Encrypted | [Jonathan_Leffler] | [Jonathan_Leffler] | 2005-12 | |||||
davsrcs | 9802 | tcp | WebDAV Source TLS/SSL | [Rob_Isaac] | [Rob_Isaac] | 2003-07 | |||||
davsrcs | 9802 | udp | WebDAV Source TLS/SSL | [Rob_Isaac] | [Rob_Isaac] | 2003-07 | |||||
intrepid-ssl | 11751 | tcp | Intrepid SSL | [Robert_Eden] | [Robert_Eden] | 2003-03 | |||||
intrepid-ssl | 11751 | udp | Intrepid SSL | [Robert_Eden] | [Robert_Eden] | 2003-03 | |||||
vipera-ssl | 12013 | tcp | Vipera Messaging Service over SSL Communication | [Silvano_Maffeis_2] | [Silvano_Maffeis_2] | 2008-01-16 | |||||
vipera-ssl | 12013 | udp | Vipera Messaging Service over SSL Communication | [Silvano_Maffeis_2] | [Silvano_Maffeis_2] | 2008-01-16 | |||||
rets-ssl | 12109 | tcp | RETS over SSL | [Jeremy_Crawford] | [Jeremy_Crawford] | 2003-02 | |||||
rets-ssl | 12109 | udp | RETS over SSL | [Jeremy_Crawford] | [Jeremy_Crawford] | 2003-02 | |||||
z-wave-s | 41230 | tcp | Z-Wave Protocol over SSL/TLS | [Sigma_Designs_3] | [Anders_Brandt_4] | 2015-06-26 | |||||
activeraid-ssl | Encrypted transport of Active Storage Proprietary Device Management Protocol | [Skip_Levens] | [Skip_Levens] | Defined TXT keys: None | |||||||
https | tcp | HTTP over SSL/TLS | [Tim_Berners_Lee] | [Tim_Berners_Lee] | Web browsers like Safari and Internet Explorer (with the Bonjour for Windows plugin) DO NOT browse for DNS-SD service type "_https._tcp" in addition to browsing for "_http._tcp". This is a conscious decision to reduce proliferation of service types, to help keep DNS-SD efficient on the network. Today, if a user types http://www.mybank.com/ into their web browser, the web server automatically redirects the user to https://www.mybank.com/. Rather than having an entirely different DNS-SD service type for https, we recommend using the same redirection mechanism: advertise a plain "http" service, which consists of nothing except an HTTP redirection to the desired "https" URL. Work is currently being done on adding mechanisms to HTTP and TLS to allow the server to tell the client that it needs to activate TLS on the current connection before proceeding. If this becomes widely adopted, it further justifies the decision to not create a separate DNS-SD service type "_https._tcp", because security becomes just another one of the things that is negotiated on a per-connection basis (like content-type negotiation today) rather than being an entirely separate thing. | ||||||
llrp-secure | RFID reader Low Level Reader Protocol over SSL/TLS | [Jason_Schoon_2] | [Jason_Schoon_2] | Defined TXT keys: None | |||||||
mother | Mother script server protocol | [Jonathan] | [Jonathan] | Defined TXT keys: user, ssl | |||||||
pstmailsync-ssl | tcp | Secured file synchronization protocol for Pst Mail Sync | [Arrow_Bit_SL] | [Javier_Nigro] | 2012-04-26 | Defined TXT keys: uuid=<unique instance identifier> | |||||
spearcat | sPearCat Host Discovery | [Pierre_Frisch_2] | [Pierre_Frisch_2] | Defined TXT keys: applicationname=<Application Name>, osname=<OS Name>, sslsupport=<Uses SSL> | |||||||
twinlevel | tcp | detect sanitary product | [Oblamatik_AG] | [Simon_Ensslen] | 2012-09-05 | Defined TXT keys: None | |||||
webdavs | WebDAV over SSL/TLS | [Y_Y_Goland] | [Y_Y_Goland] | Defined TXT keys: u=<username> p=<password> path=<path> |
1 2