Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2026-03-27
- 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| nntps | 563 | tcp | nntp protocol over TLS/SSL (was snntp) | [IESG] | [IETF_Chair] | 2018-07-06 | [RFC4642] | ||||
| nntps | 563 | udp | nntp protocol over TLS/SSL (was snntp) | [IESG] | [IETF_Chair] | 2018-07-06 | [RFC4642] | ||||
| cadabra-lm | 1563 | tcp | Cadabra License Manager | [Arthur_Castonguay] | [Arthur_Castonguay] | ||||||
| cadabra-lm | 1563 | udp | Cadabra License Manager | [Arthur_Castonguay] | [Arthur_Castonguay] | ||||||
| cti-redwood | 2563 | tcp | CTI Redwood | [Songwon_Chi] | [Songwon_Chi] | ||||||
| cti-redwood | 2563 | udp | CTI Redwood | [Songwon_Chi] | [Songwon_Chi] | ||||||
| watcomdebug | 3563 | tcp | Watcom Debug | [Dave_Neudoerffer] | [Dave_Neudoerffer] | ||||||
| watcomdebug | 3563 | udp | Watcom Debug | [Dave_Neudoerffer] | [Dave_Neudoerffer] | ||||||
| amahi-anywhere | 4563 | tcp | Amahi Anywhere | [Amahi] | [Carlos_Puchol] | 2014-02-27 | |||||
| 4563 | udp | Reserved | |||||||||
| precise-comm | 5630 | tcp | PreciseCommunication | [Alon_Tamir] | [Alon_Tamir] | 2006-04 | |||||
| precise-comm | 5630 | udp | PreciseCommunication | [Alon_Tamir] | [Alon_Tamir] | 2006-04 | |||||
| pcanywheredata | 5631 | tcp | pcANYWHEREdata | [Jon_Rosarky] | [Jon_Rosarky] | ||||||
| pcanywheredata | 5631 | udp | pcANYWHEREdata | [Jon_Rosarky] | [Jon_Rosarky] | ||||||
| pcanywherestat | 5632 | tcp | pcANYWHEREstat | [Jon_Rosarky] | [Jon_Rosarky] | ||||||
| pcanywherestat | 5632 | udp | pcANYWHEREstat | [Jon_Rosarky] | [Jon_Rosarky] | ||||||
| beorl | 5633 | tcp | BE Operations Request Listener | [Chirag_Desai] | [Chirag_Desai] | 2006-02 | |||||
| beorl | 5633 | udp | BE Operations Request Listener | [Chirag_Desai] | [Chirag_Desai] | 2006-02 | |||||
| xprtld | 5634 | tcp | SF Message Service | [VR_Satish] | [VR_Satish] | 2007-08-16 | |||||
| xprtld | 5634 | udp | SF Message Service | [VR_Satish] | [VR_Satish] | 2007-08-16 | |||||
| sfmsso | 5635 | tcp | SFM Authentication Subsystem | [De_Chih_Chien] | [De_Chih_Chien] | 2008-09-15 | |||||
| 5635 | udp | Reserved | |||||||||
| sfm-db-server | 5636 | tcp | SFMdb - SFM DB server | [De_Chih_Chien] | [De_Chih_Chien] | 2008-10-06 | |||||
| 5636 | udp | Reserved | |||||||||
| cssc | 5637 | tcp | Symantec CSSC | [Amol_P_Tambe] | [Amol_P_Tambe] | 2011-02-02 | |||||
| 5637 | udp | Reserved | |||||||||
| flcrs | 5638 | tcp | Symantec Fingerprint Lookup and Container Reference Service | [Symantec_Corp] | [Neel_A_Bhatt] | 2012-01-03 | |||||
| 5638 | udp | Reserved | |||||||||
| ics | 5639 | tcp | Symantec Integrity Checking Service | [Symantec_Corp2] | [Danzhou_Liu] | 2012-05-07 | |||||
| 5639 | udp | Reserved | |||||||||
| cfw | 7563 | tcp | Control Framework | [RFC6230] | |||||||
| 7563 | udp | Reserved |