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-rdb | 446 | tcp | DDM-Remote Relational Database Access | ||||||||
| ddm-rdb | 446 | udp | DDM-Remote Relational Database Access | ||||||||
| ora-lm | 1446 | tcp | Optical Research Associates License Manager | ||||||||
| ora-lm | 1446 | udp | Optical Research Associates License Manager | ||||||||
| bues-service | 2446 | tcp | bues_service IANA assigned this well-formed service name as a replacement for "bues_service". |
[Leonhard_Diekmann] | [Leonhard_Diekmann] | ||||||
| bues_service | 2446 | tcp | bues_service | [Leonhard_Diekmann] | [Leonhard_Diekmann] | This entry is an alias to "bues-service". This entry is now historic, not usable for use with many common service discovery mechanisms. | |||||
| bues-service | 2446 | udp | bues_service IANA assigned this well-formed service name as a replacement for "bues_service". |
[Leonhard_Diekmann] | [Leonhard_Diekmann] | ||||||
| bues_service | 2446 | udp | bues_service | [Leonhard_Diekmann] | [Leonhard_Diekmann] | This entry is an alias to "bues-service". This entry is now historic, not usable for use with many common service discovery mechanisms. | |||||
| 3comfaxrpc | 3446 | tcp | 3Com FAX RPC port | [Christopher_Wells_2] | [Christopher_Wells_2] | 2002-04 | |||||
| 3comfaxrpc | 3446 | udp | 3Com FAX RPC port | [Christopher_Wells_2] | [Christopher_Wells_2] | 2002-04 | |||||
| n1-fwp | 4446 | tcp | N1-FWP | ||||||||
| n1-fwp | 4446 | udp | N1-FWP | ||||||||
| ntske | 4460 | tcp | Network Time Security Key Establishment | [IESG] | [IETF_Chair] | 2020-04-07 | [RFC8915] | ||||
| 4460 | udp | Reserved | |||||||||
| 4461-4479 | Unassigned | ||||||||||
| 5446-5449 | Unassigned | ||||||||||
| mysql-proxy | 6446 | tcp | MySQL Proxy | [Kay_Roepke] | [Kay_Roepke] | 2009-04-22 | |||||
| mysql-proxy | 6446 | udp | MySQL Proxy | [Kay_Roepke] | [Kay_Roepke] | 2009-04-22 | |||||
| 8446-8447 | Unassigned | ||||||||||
| 9446-9449 | Unassigned | ||||||||||
| 24387-24464 | Unassigned | ||||||||||
| tonidods | 24465 | tcp | Tonido Domain Server | [Madhan_Kanagavel] | [Madhan_Kanagavel] | 2008-07-18 | |||||
| tonidods | 24465 | udp | Tonido Domain Server | [Madhan_Kanagavel] | [Madhan_Kanagavel] | 2008-07-18 | |||||
| 24466-24553 | Unassigned | ||||||||||
| 44446-44543 | Unassigned | Known UNAUTHORIZED USE: Ports 44515 & 44516 | |||||||||
| 44600 | tcp | Reserved | |||||||||
| asihpi | 44600 | udp | AudioScience HPI | [Eliot_Blennerhassett] | [Eliot_Blennerhassett] | 2011-07-07 | |||||
| 44601-44817 | Unassigned |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Christopher_Wells_2] | Christopher Wells | mailto:christopher_wells&3com.com | 2002-04 | |
| [Eliot_Blennerhassett] | Eliot Blennerhassett | mailto:eblennerhassett&audioscience.com | 2011-07-07 | |
| [IESG] | IESG | mailto:iesg&ietf.org | ||
| [IETF_Chair] | IETF Chair | IETF | mailto:chair&ietf.org | |
| [Kay_Roepke] | Kay Roepke | mailto:Kay.Roepke&sun.com | 2009-04-22 | |
| [Leonhard_Diekmann] | Leonhard Diekmann | mailto:diekmann&04.mstr02.telekom400.dbp.de | ||
| [Madhan_Kanagavel] | Madhan Kanagavel | mailto:madhan&codelathe.com | 2008-07-18 |