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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| tserver | 450 | tcp | Computer Supported Telecomunication Applications | [Harvey_S_Schultz] | [Harvey_S_Schultz] | ||||||
| tserver | 450 | udp | Computer Supported Telecomunication Applications | [Harvey_S_Schultz] | [Harvey_S_Schultz] | ||||||
| dwf | 1450 | tcp | Tandem Distributed Workbench Facility | [Mike_Bert] | [Mike_Bert] | ||||||
| dwf | 1450 | udp | Tandem Distributed Workbench Facility | [Mike_Bert] | [Mike_Bert] | ||||||
| amt | 2268 | tcp | AMT | [IESG] | [IETF_Chair] | 2004-12 | 2014-12-17 | [RFC7450] | |||
| amt | 2268 | udp | AMT | [IESG] | [IETF_Chair] | 2004-12 | 2014-12-17 | [RFC7450] | |||
| netadmin | 2450 | tcp | netadmin | ||||||||
| netadmin | 2450 | udp | netadmin | ||||||||
| castorproxy | 3450 | tcp | CAStorProxy | [Raymond_J_Young] | [Raymond_J_Young] | 2002-04 | |||||
| castorproxy | 3450 | udp | CAStorProxy | [Raymond_J_Young] | [Raymond_J_Young] | 2002-04 | |||||
| camp | 4450 | tcp | Common ASCII Messaging Protocol | [Control_Technology_Inc] | [Clint_Eskew] | 2011-10-28 | |||||
| camp | 4450 | udp | Common ASCII Messaging Protocol | [Control_Technology_Inc] | [Clint_Eskew] | 2011-10-28 | |||||
| ipsec-nat-t | 4500 | tcp | IPsec NAT-Traversal | 2022-09-15 | [RFC9329] | ||||||
| ipsec-nat-t | 4500 | udp | IPsec NAT-Traversal | 2017-07-07 | [RFC3948][RFC7296] | ||||||
| 4501 | Unassigned | [IANA] | [IANA] | De-registered 08 June 2001 | |||||||
| a25-fap-fgw | 4502 | sctp | A25 (FAP-FGW) | [_3GPP_2] | [Zhiming_Li] | 2012-01-11 | |||||
| 4503 | tcp | Reserved | |||||||||
| m-bus-oms | 4503 | udp | M-Bus-OMS over UDP | [OMS-Group_e._V.] | [Ahmed_Kasttet] | 2025-05-19 | |||||
| 4504-4533 | Unassigned | ||||||||||
| tiepie | 5450 | tcp | TiePie engineering data acquisition | [TiePie_engineering] | [Reinder_Feenstra] | 2016-04-01 | |||||
| tiepie-disc | 5450 | udp | TiePie engineering data acquisition (discovery) | [TiePie_engineering] | [Reinder_Feenstra] | 2016-04-01 | |||||
| npmp | 8450 | tcp | npmp | [Ian_Chard] | [Ian_Chard] | ||||||
| npmp | 8450 | udp | npmp | [Ian_Chard] | [Ian_Chard] | ||||||
| sntlkeyssrvr | 9450 | tcp | Sentinel Keys Server | [Martin_Ziskind] | [Martin_Ziskind] | 2008-08-21 | |||||
| sntlkeyssrvr | 9450 | udp | Sentinel Keys Server | [Martin_Ziskind] | [Martin_Ziskind] | 2008-08-21 | |||||
| multicast-ping | 9903 | udp | Multicast Ping Protocol | 2011-12-09 | [RFC6450] | ||||||
| xpra | 14500 | tcp | xpra network protocol | [Xpra] | [Antoine_Martin] | 2016-10-05 | |||||
| 14500 | udp | Reserved | |||||||||
| 14501-14935 | Unassigned | ||||||||||
| asmp | 45000 | tcp | Nuance AutoStore Status Monitoring Protocol (data transfer) | [Nuance_Communications_Inc4] | [Andrew_Andrews] | 2011-09-01 | 2017-04-26 | ||||
| asmp-mon | 45000 | udp | Nuance AutoStore Status Monitoring Protocol (device monitoring) | [Nuance_Communications_Inc4] | [Andrew_Andrews] | 2011-09-01 | 2017-04-26 | ||||
| asmps | 45001 | tcp | Nuance AutoStore Status Monitoring Protocol (secure data transfer) | [Nuance_Communications_Inc4] | [Andrew_Andrews] | 2011-09-01 | 2017-04-26 | ||||
| 45001 | udp | Reserved | |||||||||
| rs-status | 45002 | tcp | Redspeed Status Monitor | [Redspeed_International_Ltd] | [Simon_Griffiths] | 2015-03-10 | |||||
| 45002 | udp | Reserved | |||||||||
| 45003-45044 | Unassigned | ||||||||||
| synctest | 45045 | tcp | Remote application control protocol | [Eleks_Ltd] | [Andriy_Skop] | 2013-04-08 | |||||
| 45045 | udp | Reserved | |||||||||
| 45046-45053 | Unassigned | ||||||||||
| invision-ag | 45054 | tcp | InVision AG | [Matthias_Schroer] | [Matthias_Schroer] | ||||||
| invision-ag | 45054 | udp | InVision AG | [Matthias_Schroer] | [Matthias_Schroer] | ||||||
| 45055-45184 | Unassigned |