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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| ris-cm | 748 | tcp | Russell Info Sci Calendar Manager | ||||||||
| ris-cm | 748 | udp | Russell Info Sci Calendar Manager | ||||||||
| oracle-em1 | 1748 | tcp | oracle-em1 | [Bob_Purvy] | [Bob_Purvy] | ||||||
| oracle-em1 | 1748 | udp | oracle-em1 | [Bob_Purvy] | [Bob_Purvy] | ||||||
| fjippol-polsvr | 2748 | tcp | |||||||||
| fjippol-polsvr | 2748 | udp | |||||||||
| webdata | 3748 | tcp | webData | [Michael_Whiteley] | [Michael_Whiteley] | 2003-04 | |||||
| webdata | 3748 | udp | webData | [Michael_Whiteley] | [Michael_Whiteley] | 2003-04 | |||||
| 4748-4748 | Unassigned | ||||||||||
| tunalyzer | 5748 | tcp | Wildbits Tunalyzer | [Sylvain_Demongeot] | [Sylvain_Demongeot] | 2005-08 | |||||
| tunalyzer | 5748 | udp | Wildbits Tunalyzer | [Sylvain_Demongeot] | [Sylvain_Demongeot] | 2005-08 | |||||
| 7748-7776 | Unassigned | ||||||||||
| 9748-9749 | Unassigned | ||||||||||
| 37476-37482 | Unassigned | ||||||||||
| gdrive-sync | 37483 | tcp | Google Drive Sync | [Google_Inc] | [Jason_Schiller] | 2013-02-01 | 2015-07-31 | ||||
| 37483 | udp | Reserved | |||||||||
| 37484-37600 | Unassigned |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Bob_Purvy] | Bob Purvy | mailto:bpurvy&us.oracle.com | ||
| [Google_Inc] | Google Inc. | mailto:numbers&google.com | 2015-07-31 | |
| [Jason_Schiller] | Jason Schiller | Google Inc. | mailto:jschiller&google.com | 2015-07-31 |
| [Michael_Whiteley] | Michael Whiteley | mailto:michael&whiteley.com | 2003-04 | |
| [Sylvain_Demongeot] | Sylvain Demongeot | mailto:sylvain.demongeot&wildbits.com | 2005-08 |