Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2026-09-07
- 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| nucleus-sand | 1201 | tcp | Nucleus Sand Database Server | [James_Marsh] | [James_Marsh] | ||||||
| nucleus-sand | 1201 | udp | Nucleus Sand Database Server | [James_Marsh] | [James_Marsh] | ||||||
| smsqp | 11201 | tcp | smsqp | [Andres_Seco_Hernande] | [Andres_Seco_Hernande] | ||||||
| smsqp | 11201 | udp | smsqp | [Andres_Seco_Hernande] | [Andres_Seco_Hernande] | ||||||
| edbsrvr | 12010 | tcp | ElevateDB Server | [Tim_Young] | [Tim_Young] | 2009-05-06 | |||||
| 12010 | udp | Reserved | |||||||||
| 12011 | Unassigned | ||||||||||
| vipera | 12012 | tcp | Vipera Messaging Service | [Silvano_Maffeis_2] | [Silvano_Maffeis_2] | 2005-08 | |||||
| vipera | 12012 | udp | Vipera Messaging Service | [Silvano_Maffeis_2] | [Silvano_Maffeis_2] | 2005-08 | |||||
| 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 | |||||
| 12014-12108 | Unassigned |
Contact Information
| ID | Name | Contact URI | Last Updated |
|---|---|---|---|
| [Andres_Seco_Hernande] | Andres Seco Hernandez | mailto:AndresSH&alamin.org | |
| [James_Marsh] | James Marsh | mailto:James_T_Marsh&hotmail.com | |
| [Silvano_Maffeis_2] | Silvano Maffeis | mailto:maffeis&acm.org | 2008-01-16 |
| [Tim_Young] | Tim Young | mailto:timyoung&elevatesoft.com | 2009-05-06 |