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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| fairview | 38202 | tcp | Fairview Message Service | [Jim_Lyle] | [Jim_Lyle] | 2005-11 | Defined TXT keys: DevID=<device id>, DevType=<device type>, DevStat=<device status> | ||||
| fairview | 38202 | udp | Fairview Message Service | [Jim_Lyle] | [Jim_Lyle] | 2005-11 | Defined TXT keys: DevID=<device id>, DevType=<device type>, DevStat=<device status> | ||||
| agpolicy | 38203 | tcp | AppGate Policy Server | [Martin_Forssen] | [Martin_Forssen] | 2004-11 | |||||
| agpolicy | 38203 | udp | AppGate Policy Server | [Martin_Forssen] | [Martin_Forssen] | 2004-11 | |||||
| 38204-38411 | Unassigned | ||||||||||
| 39682-39999 | Unassigned | ||||||||||
| 45679-45823 | Unassigned | ||||||||||
| dai-shell | 45824 | tcp | Server for the DAI family of client-server products | [Data_Access_Inc] | [Adam_Robinson] | 2012-04-30 | |||||
| 45824 | udp | Reserved | |||||||||
| qdb2service | 45825 | tcp | Qpuncture Data Access Service | [Michael_Yun] | [Michael_Yun] | 2007-10-24 | |||||
| qdb2service | 45825 | udp | Qpuncture Data Access Service | [Michael_Yun] | [Michael_Yun] | 2007-10-24 | |||||
| 45826-45965 | Unassigned |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Adam_Robinson] | Adam Robinson | Data Access, Inc. | mailto:adam&dataaccessinc.com | 2012-04-30 |
| [Data_Access_Inc] | Data Access, Inc. | mailto:development&dataaccessinc.com | 2012-04-30 | |
| [Jim_Lyle] | Jim Lyle | mailto:jim.lyle&siliconimage.com | 2005-11 | |
| [Martin_Forssen] | Martin Forssen | mailto:maf&appgate.com | 2004-11 | |
| [Michael_Yun] | Michael Yun | mailto:cinnanda&gmail.com | 2007-10-24 |