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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| scx-proxy | 470 | tcp | scx-proxy | [Scott_Narveson] | [Scott_Narveson] | ||||||
| scx-proxy | 470 | udp | scx-proxy | [Scott_Narveson] | [Scott_Narveson] | ||||||
| nas | 991 | tcp | Netnews Administration System | [Vera_Heinau][Heiko_Schlichting] | [Vera_Heinau][Heiko_Schlichting] | 2017-02-10 | [RFC4707] | ||||
| nas | 991 | udp | Netnews Administration System | [Vera_Heinau][Heiko_Schlichting] | [Vera_Heinau][Heiko_Schlichting] | 2017-02-10 | [RFC4707] | ||||
| uaiact | 1470 | tcp | Universal Analytics | [Mark_R_Ludwig] | [Mark_R_Ludwig] | ||||||
| uaiact | 1470 | udp | Universal Analytics | [Mark_R_Ludwig] | [Mark_R_Ludwig] | ||||||
| mil-2045-47001 | 1581 | tcp | MIL-2045-47001 | [Eric_Whitehill] | [Eric_Whitehill] | ||||||
| mil-2045-47001 | 1581 | udp | MIL-2045-47001 | [Eric_Whitehill] | [Eric_Whitehill] | ||||||
| taskman-port | 2470 | tcp | taskman port | [Boris_Panteleev] | [Boris_Panteleev] | ||||||
| taskman-port | 2470 | udp | taskman port | [Boris_Panteleev] | [Boris_Panteleev] | ||||||
| jt400 | 3470 | tcp | jt400 | ||||||||
| jt400 | 3470 | udp | jt400 | ||||||||
| netxms-agent | 4700 | tcp | NetXMS Agent | ||||||||
| netxms-agent | 4700 | udp | NetXMS Agent | ||||||||
| netxms-mgmt | 4701 | tcp | NetXMS Management | ||||||||
| netxms-mgmt | 4701 | udp | NetXMS Management | ||||||||
| netxms-sync | 4702 | tcp | NetXMS Server Synchronization | [Victor_Kirhenshtein] | [Victor_Kirhenshtein] | 2006-07 | |||||
| netxms-sync | 4702 | udp | NetXMS Server Synchronization | [Victor_Kirhenshtein] | [Victor_Kirhenshtein] | 2006-07 | |||||
| npqes-test | 4703 | tcp | Network Performance Quality Evaluation System Test Service | [Zhengli] | [Zhengli] | 2010-06-28 | |||||
| 4703 | udp | Reserved | |||||||||
| assuria-ins | 4704 | tcp | Assuria Insider | [Nick_Connor] | [Nick_Connor] | 2010-06-30 | |||||
| 4704 | udp | Reserved | |||||||||
| 4705-4710 | Unassigned | ||||||||||
| apsolab-col | 5470 | tcp | The Apsolab company's data collection protocol (native api) | [Apsolab_Inc] | [Jean-Francois_Gauthier] | 2014-11-10 | |||||
| 5470 | udp | Reserved | |||||||||
| 6465-6470 | Unassigned | ||||||||||
| 7444-7470 | Unassigned | ||||||||||
| cisco-avp | 8470 | tcp | Cisco Address Validation Protocol | [Cullen_Jennings] | [Cullen_Jennings] | 2009-02-13 | |||||
| 8470 | udp | Reserved | |||||||||
| 25101-25470 | Unassigned | ||||||||||
| mbus | 47000 | tcp | Message Bus | [Dirk_Kutscher] | [Dirk_Kutscher] | ||||||
| mbus | 47000 | udp | Message Bus | [Dirk_Kutscher] | [Dirk_Kutscher] | ||||||
| winrm | 47001 | tcp | Windows Remote Management Service | [Ryan_Mack] | [Ryan_Mack] | 2009-04-29 | |||||
| 47001 | udp | Reserved | |||||||||
| 47002-47099 | Unassigned |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Apsolab_Inc] | Apsolab Inc. | mailto:admin&apsolab.com | 2014-11-10 | |
| [Boris_Panteleev] | Boris Panteleev | mailto:bpanteleev&himel.com | ||
| [Cullen_Jennings] | Cullen Jennings | mailto:fluffy&cisco.com | 2010-02-03 | |
| [Dirk_Kutscher] | Dirk Kutscher | mailto:dku&informatik.uni-bremen.de | ||
| [Eric_Whitehill] | Eric Whitehill | mailto:Eric.Whitehill&itt.com | ||
| [Heiko_Schlichting] | Heiko Schlichting | mailto:heiko.schlichting&fu-berlin.de | 2022-06-07 | |
| [Jean-Francois_Gauthier] | Jean-Francois Gauthier | Apsolab Inc. | mailto:jfgauthier&apsolab.com | 2014-11-10 |
| [Mark_R_Ludwig] | Mark R. Ludwig | mailto:Mark-Ludwig&uai.com | ||
| [Nick_Connor] | Nick Connor | mailto:nickc&assuria.com | 2010-06-30 | |
| [Ryan_Mack] | Ryan Mack | mailto:rmackµsoft.com | 2009-04-29 | |
| [Scott_Narveson] | Scott Narveson | mailto:sjn&cray.com | ||
| [Vera_Heinau] | Vera Heinau | mailto:vera.heinau&fu-berlin.de | 2022-06-07 | |
| [Victor_Kirhenshtein] | Victor Kirhenshtein | mailto:victor&opticom.lv | 2006-07 | |
| [Zhengli] | Zhengli | mailto:std&iwncomm.com | 2010-06-28 |