Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2026-08-17
- 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| dtag-ste-sb | 352 | tcp | DTAG | [Ruediger_Wald] | [Ruediger_Wald] | (assigned long ago) | |||||
| dtag-ste-sb | 352 | udp | DTAG | [Ruediger_Wald] | [Ruediger_Wald] | (assigned long ago) | |||||
| bhoedap4 | 352 | tcp | bhoedap4 | [John_Kelly] | [John_Kelly] | This entry records an unassigned but widespread use (added 5/21/97) | |||||
| bhoedap4 | 352 | udp | bhoedap4 | [John_Kelly] | [John_Kelly] | This entry records an unassigned but widespread use (added 5/21/97) | |||||
| xmlrpc-beep | 602 | tcp | XML-RPC over BEEP | [RFC3529] | |||||||
| xmlrpc-beep | 602 | udp | XML-RPC over BEEP | [RFC3529] | |||||||
| lotusnote | 1352 | tcp | Lotus Note | [Greg_Pflaum] | [Greg_Pflaum] | 1992-07 | |||||
| lotusnote | 1352 | udp | Lotus Note | [Greg_Pflaum] | [Greg_Pflaum] | 1992-07 | |||||
| pslserver | 2352 | tcp | pslserver | ||||||||
| pslserver | 2352 | udp | pslserver | ||||||||
| ssql | 3352 | tcp | Scalable SQL | [Chuck_Talk] | [Chuck_Talk] | ||||||
| ssql | 3352 | udp | Scalable SQL | [Chuck_Talk] | [Chuck_Talk] | ||||||
| galileolog | 3520 | tcp | Netvion Galileo Log Port | [Ray_Caruso] | [Ray_Caruso] | 2002-06 | |||||
| galileolog | 3520 | udp | Netvion Galileo Log Port | [Ray_Caruso] | [Ray_Caruso] | 2002-06 | |||||
| mc3ss | 3521 | tcp | Telequip Labs MC3SS | [Michael_Sparks] | [Michael_Sparks] | 2002-06 | |||||
| mc3ss | 3521 | udp | Telequip Labs MC3SS | [Michael_Sparks] | [Michael_Sparks] | 2002-06 | |||||
| nssocketport | 3522 | tcp | DO over NSSocketPort | [Douglas_Davidson] | [Douglas_Davidson] | 2002-06 | |||||
| nssocketport | 3522 | udp | DO over NSSocketPort | [Douglas_Davidson] | [Douglas_Davidson] | 2002-06 | |||||
| odeumservlink | 3523 | tcp | Odeum Serverlink | [Mads_Peter_Back] | [Mads_Peter_Back] | 2002-06 | |||||
| odeumservlink | 3523 | udp | Odeum Serverlink | [Mads_Peter_Back] | [Mads_Peter_Back] | 2002-06 | |||||
| ecmport | 3524 | tcp | ECM Server port | ||||||||
| ecmport | 3524 | udp | ECM Server port | ||||||||
| eisport | 3525 | tcp | EIS Server port | [Paul_Kraus] | [Paul_Kraus] | 2002-06 | |||||
| eisport | 3525 | udp | EIS Server port | [Paul_Kraus] | [Paul_Kraus] | 2002-06 | |||||
| starquiz-port | 3526 | tcp | starQuiz Port | [Adam_Ernst_2] | [Adam_Ernst_2] | 2002-06 | |||||
| starquiz-port | 3526 | udp | starQuiz Port | [Adam_Ernst_2] | [Adam_Ernst_2] | 2002-06 | |||||
| beserver-msg-q | 3527 | tcp | VERITAS Backup Exec Server | [Katherine_Wattwood] | [Katherine_Wattwood] | 2002-06 | |||||
| beserver-msg-q | 3527 | udp | VERITAS Backup Exec Server | [Katherine_Wattwood] | [Katherine_Wattwood] | 2002-06 | |||||
| jboss-iiop | 3528 | tcp | JBoss IIOP | ||||||||
| jboss-iiop | 3528 | udp | JBoss IIOP | ||||||||
| jboss-iiop-ssl | 3529 | tcp | JBoss IIOP/SSL | [Francisco_Reverbel] | [Francisco_Reverbel] | 2002-06 | |||||
| jboss-iiop-ssl | 3529 | udp | JBoss IIOP/SSL | [Francisco_Reverbel] | [Francisco_Reverbel] | 2002-06 | |||||
| asap-udp | 3863 | udp | asap udp port | [RFC5352] | |||||||
| asap-sctp | 3863 | sctp | asap sctp | [RFC5352] | |||||||
| asap-tcp-tls | 3864 | tcp | asap/tls tcp port | [RFC5352] | |||||||
| asap-sctp-tls | 3864 | sctp | asap-sctp/tls | [RFC5352] | |||||||
| pjlink | 4352 | tcp | Projector Link | [Mitsuo_Kodama] | [Mitsuo_Kodama] | 2005-06 | |||||
| pjlink | 4352 | udp | Projector Link | [Mitsuo_Kodama] | [Mitsuo_Kodama] | 2005-06 | |||||
| dns-llq | 5352 | tcp | DNS Long-Lived Queries | [Stuart_Cheshire] | [Stuart_Cheshire] | 2005-08 | 2019-08-26 | [RFC8764] | |||
| dns-llq | 5352 | udp | DNS Long-Lived Queries | [Stuart_Cheshire] | [Stuart_Cheshire] | 2005-08 | 2019-08-26 | [RFC8764] | |||
| pon-ictp | 7202 | tcp | Inter-Channel Termination Protocol (ICTP) for multi-wavelength PON (Passive Optical Network) systems | [Broadband_Forum] | [Broadband_Forum] | 2017-02-22 | 2019-12-16 | [TR-352][Inter-Channel-Termination protocol (ICTP) is a peer-to-peer protocol with a binary message format that is used by a set of optical line terminal (OLT) channel terminations (CT) comprising a 40-Gigabit-capable next-generation passive optical network (NG-PON2) system to exchange channel profile configuration and status information and to coordinate the operation of tunable optical network units (ONUs) in a multi-wavelength channel environment.] | |||
| 8352-8375 | Unassigned | ||||||||||
| 22352-22536 | Unassigned | ||||||||||
| carddav | tcp | vCard Extensions to WebDAV (CardDAV) - non-TLS | [IESG] | [IETF_Chair] | 2012-02-17 | [RFC6352] | This is an extension of the http service. Defined TXT keys: path=<context path> | ||||
| carddavs | tcp | vCard Extensions to WebDAV (CardDAV) - over TLS | [IESG] | [IETF_Chair] | 2012-02-17 | [RFC6352] | This is an extension of the https service. Defined TXT keys: path=<context path> |