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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| p2pq | 1981 | tcp | p2pQ | [Warren_Alexander] | [Warren_Alexander] | ||||||
| p2pq | 1981 | udp | p2pQ | [Warren_Alexander] | [Warren_Alexander] | ||||||
| mylxamport | 2981 | tcp | MYLXAMPORT | [Wei_Gao] | [Wei_Gao] | ||||||
| mylxamport | 2981 | udp | MYLXAMPORT | [Wei_Gao] | [Wei_Gao] | ||||||
| starfish | 3981 | tcp | Starfish System Admin | [Dan_Razzell] | [Dan_Razzell] | 2006-06 | |||||
| starfish | 3981 | udp | Starfish System Admin | [Dan_Razzell] | [Dan_Razzell] | 2006-06 | |||||
| 4981-4982 | Unassigned | ||||||||||
| 6981-6996 | Unassigned | ||||||||||
| sossd-collect | 7981 | tcp | Spotlight on SQL Server Desktop Collect | [Rob_Griffin_2] | [Rob_Griffin_2] | 2010-08-30 | |||||
| 7981 | udp | Reserved | |||||||||
| nod-client | 8981 | udp | Network of Devices Client | [David_Muller] | [David_Muller] | 2015-02-22 | |||||
| 8981 | tcp | Reserved | |||||||||
| pumpkindb | 9981 | tcp | Event sourcing database engine with a built-in programming language | [Eventsourcing_Inc] | [Yurii_Rashkovskii] | 2017-04-18 | |||||
| 9981 | udp | Reserved | |||||||||
| 34981-34999 | Unassigned |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Dan_Razzell] | Dan Razzell | mailto:dan&starfishsystems.ca | 2006-06 | |
| [David_Muller] | David Müller | mailto:david.muller.cz&gmail.com | 2015-02-22 | |
| [Eventsourcing_Inc] | Eventsourcing, Inc. | mailto:accounts&eventsourcing.com | 2017-04-18 | |
| [Rob_Griffin_2] | Rob Griffin | mailto:rob.gri55in&gmail.com | 2010-09-13 | |
| [Warren_Alexander] | Warren Alexander | mailto:warren&chameleon-creative.co.uk | ||
| [Wei_Gao] | Wei Gao | mailto:wei&mylex.com | ||
| [Yurii_Rashkovskii] | Yurii Rashkovskii | mailto:yrashk&eventsourcing.com | 2017-04-18 |