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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| ddm-dfm | 447 | tcp | DDM-Distributed File Management | [Steven_Ritland] | [Steven_Ritland] | ||||||
| ddm-dfm | 447 | udp | DDM-Distributed File Management | [Steven_Ritland] | [Steven_Ritland] | ||||||
| apri-lm | 1447 | tcp | Applied Parallel Research LM | [Jim_Dillon] | [Jim_Dillon] | ||||||
| apri-lm | 1447 | udp | Applied Parallel Research LM | [Jim_Dillon] | [Jim_Dillon] | ||||||
| ovwdb | 2447 | tcp | OpenView NNM daemon | [Eric_Pulsipher_2] | [Eric_Pulsipher_2] | ||||||
| ovwdb | 2447 | udp | OpenView NNM daemon | [Eric_Pulsipher_2] | [Eric_Pulsipher_2] | ||||||
| directnet | 3447 | tcp | DirectNet IM System | [Gregory_Richards] | [Gregory_Richards] | 2002-04 | |||||
| directnet | 3447 | udp | DirectNet IM System | [Gregory_Richards] | [Gregory_Richards] | 2002-04 | |||||
| n1-rmgmt | 4447 | tcp | N1-RMGMT | [Lori_Tassin] | [Lori_Tassin] | ||||||
| n1-rmgmt | 4447 | udp | N1-RMGMT | [Lori_Tassin] | [Lori_Tassin] | ||||||
| 4461-4479 | Unassigned | ||||||||||
| 6447-6454 | Unassigned | ||||||||||
| 8446-8447 | Unassigned |
Contact Information
| ID | Name | Contact URI | Last Updated |
|---|---|---|---|
| [Eric_Pulsipher_2] | Eric Pulsipher | mailto:eric_pulsipher&fc.hp.com | |
| [Gregory_Richards] | Gregory Richards | mailto:Richards&codu.org | 2002-04 |
| [Jim_Dillon] | Jim Dillon | mailto:jed&apri.com | |
| [Lori_Tassin] | Lori Tassin | mailto:Ramsey&network-1.com | |
| [Steven_Ritland] | Steven Ritland | mailto:srr&us.ibm.com |