Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2026-09-11
- 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| devshr-nts | 552 | tcp | DeviceShare | [Benjamin_Rosenberg] | [Benjamin_Rosenberg] | ||||||
| devshr-nts | 552 | udp | DeviceShare | [Benjamin_Rosenberg] | [Benjamin_Rosenberg] | ||||||
| pciarray | 1552 | tcp | pciarray | [Ron_Folk] | [Ron_Folk] | ||||||
| pciarray | 1552 | udp | pciarray | [Ron_Folk] | [Ron_Folk] | ||||||
| call-logging | 2552 | tcp | Call Logging | [Dean_Webb] | [Dean_Webb] | ||||||
| call-logging | 2552 | udp | Call Logging | [Dean_Webb] | [Dean_Webb] | ||||||
| taserver | 3552 | tcp | TeamAgenda Server Port | [Dany_Ayotte] | [Dany_Ayotte] | 2002-07 | |||||
| taserver | 3552 | udp | TeamAgenda Server Port | [Dany_Ayotte] | [Dany_Ayotte] | 2002-07 | |||||
| menandmice-mon | 4552 | tcp | Men and Mice Monitoring | [Carsten_Strotmann] | [Carsten_Strotmann] | 2009-05-20 | |||||
| menandmice-mon | 4552 | udp | Men and Mice Monitoring | [Carsten_Strotmann] | [Carsten_Strotmann] | 2009-05-20 | |||||
| 5551-5552 | Unassigned | ||||||||||
| 6552-6555 | Unassigned | ||||||||||
| 7552-7559 | Unassigned | ||||||||||
| 21338-21552 | Unassigned | ||||||||||
| 44545-44552 | Unassigned |
Contact Information
| ID | Name | Contact URI | Last Updated |
|---|---|---|---|
| [Benjamin_Rosenberg] | Benjamin Rosenberg | mailto:brosenberg&advsyscon.com | |
| [Carsten_Strotmann] | Carsten Strotmann | mailto:carsten.strotmann&menandmice.com | 2009-05-20 |
| [Dany_Ayotte] | Dany Ayotte | mailto:ayotte&teamsoft.com | 2002-07 |
| [Dean_Webb] | Dean Webb | mailto:dean.webb&ascend.com | |
| [Ron_Folk] | Ron Folk | mailto:rfolkes&avl.com |