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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| soap-beep | 605 | tcp | SOAP over BEEP | [RFC4227] | |||||||
| soap-beep | 605 | udp | SOAP over BEEP | [RFC4227] | |||||||
| slp | 1605 | tcp | Salutation Manager (Salutation Protocol) | ||||||||
| slp | 1605 | udp | Salutation Manager (Salutation Protocol) | ||||||||
| nsc-posa | 2605 | tcp | NSC POSA | [Tom_Findley] | [Tom_Findley] | ||||||
| nsc-posa | 2605 | udp | NSC POSA | [Tom_Findley] | [Tom_Findley] | ||||||
| comcam-io | 3605 | tcp | ComCam IO Port | [Don_Gilbreath] | [Don_Gilbreath] | 2002-09 | |||||
| comcam-io | 3605 | udp | ComCam IO Port | [Don_Gilbreath] | [Don_Gilbreath] | 2002-09 | |||||
| sixchat | 4605 | tcp | Direct End to End Secure Chat Protocol | [Sixscape_Communications_Pte_Ltd] | [Lawrence_E._Hughes] | 2014-09-11 | |||||
| 4605 | udp | Reserved | |||||||||
| a4-sdunode | 5605 | tcp | A4-SDUNode | [Mike_Dolan] | [Mike_Dolan] | ||||||
| a4-sdunode | 5605 | udp | A4-SDUNode | [Mike_Dolan] | [Mike_Dolan] | ||||||
| 7589-7605 | Unassigned | ||||||||||
| 25605-25792 | Unassigned |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Don_Gilbreath] | Don Gilbreath | mailto:don&comcam.net | 2002-09 | |
| [Lawrence_E._Hughes] | Lawrence E. Hughes | Sixscape Communications, Ltd. | mailto:lhughes&sixscape.com | 2014-03-17 |
| [Mike_Dolan] | Mike Dolan | mailto:MDolan&ihcmail.ih.lucent.com | ||
| [Sixscape_Communications_Pte_Ltd] | Sixscape Communications, Pte. Ltd. | mailto:lhughes&sixscape.com | 2014-08-26 | |
| [Tom_Findley] | Tom Findley | mailto:tom.findley&networksciences.net |