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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| idxp | 603 | tcp | IDXP | [RFC4767] | |||||||
| idxp | 603 | udp | IDXP | [RFC4767] | |||||||
| picodbc | 1603 | tcp | pickodbc | [John_Lombardo] | [John_Lombardo] | ||||||
| picodbc | 1603 | udp | pickodbc | [John_Lombardo] | [John_Lombardo] | ||||||
| servicemeter | 2603 | tcp | Service Meter | [Duncan_Hare] | [Duncan_Hare] | ||||||
| servicemeter | 2603 | udp | Service Meter | [Duncan_Hare] | [Duncan_Hare] | ||||||
| int-rcv-cntrl | 3603 | tcp | Integrated Rcvr Control | [Dave_Stone] | [Dave_Stone] | 2002-09 | |||||
| int-rcv-cntrl | 3603 | udp | Integrated Rcvr Control | [Dave_Stone] | [Dave_Stone] | 2002-09 | |||||
| menandmice-upg | 4603 | tcp | Men & Mice Upgrade Agent | [Eggert_Thorlacius_2] | [Eggert_Thorlacius_2] | 2010-01-27 | |||||
| 4603 | udp | Reserved | |||||||||
| a1-bs | 5603 | tcp | A1-BS | [Mike_Dolan] | [Mike_Dolan] | ||||||
| a1-bs | 5603 | udp | A1-BS | [Mike_Dolan] | [Mike_Dolan] | ||||||
| 6603-6609 | Unassigned | ||||||||||
| 25577-25603 | Unassigned | ||||||||||
| 36603-36699 | Unassigned |
Contact Information
| ID | Name | Contact URI | Last Updated |
|---|---|---|---|
| [Dave_Stone] | Dave Stone | mailto:dstone01&harris.com | 2002-09 |
| [Duncan_Hare] | Duncan Hare | mailto:Duncan.Hare&synoia.com | |
| [Eggert_Thorlacius_2] | Eggert Thorlacius | mailto:eggi&menandmice.com | 2010-01-27 |
| [John_Lombardo] | John Lombardo | mailto:johnl&picksys.com | |
| [Mike_Dolan] | Mike Dolan | mailto:MDolan&ihcmail.ih.lucent.com |