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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| ansatrader | 124 | tcp | ANSA REX Trader | [Nicola_J_Howarth] | [Nicola_J_Howarth] | ||||||
| ansatrader | 124 | udp | ANSA REX Trader | [Nicola_J_Howarth] | [Nicola_J_Howarth] | ||||||
| hpvmmcontrol | 1124 | tcp | HP VMM Control | ||||||||
| hpvmmcontrol | 1124 | udp | HP VMM Control | ||||||||
| instantia | 1240 | tcp | Instantia | [Ruth_Slater] | [Ruth_Slater] | ||||||
| instantia | 1240 | udp | Instantia | [Ruth_Slater] | [Ruth_Slater] | ||||||
| nessus | 1241 | tcp | nessus | [Jordan_Hrycaj] | [Jordan_Hrycaj] | ||||||
| nessus | 1241 | udp | nessus | [Jordan_Hrycaj] | [Jordan_Hrycaj] | ||||||
| nmasoverip | 1242 | tcp | NMAS over IP | [Hal_Henderson] | [Hal_Henderson] | ||||||
| nmasoverip | 1242 | udp | NMAS over IP | [Hal_Henderson] | [Hal_Henderson] | ||||||
| serialgateway | 1243 | tcp | SerialGateway | [Stephen_LaValley] | [Stephen_LaValley] | ||||||
| serialgateway | 1243 | udp | SerialGateway | [Stephen_LaValley] | [Stephen_LaValley] | ||||||
| isbconference1 | 1244 | tcp | isbconference1 | ||||||||
| isbconference1 | 1244 | udp | isbconference1 | ||||||||
| isbconference2 | 1245 | tcp | isbconference2 | [Arnold_Dittmann] | [Arnold_Dittmann] | ||||||
| isbconference2 | 1245 | udp | isbconference2 | [Arnold_Dittmann] | [Arnold_Dittmann] | ||||||
| payrouter | 1246 | tcp | payrouter | [David_Wilson] | [David_Wilson] | ||||||
| payrouter | 1246 | udp | payrouter | [David_Wilson] | [David_Wilson] | ||||||
| visionpyramid | 1247 | tcp | VisionPyramid | [Gavin_Hutchinson] | [Gavin_Hutchinson] | ||||||
| visionpyramid | 1247 | udp | VisionPyramid | [Gavin_Hutchinson] | [Gavin_Hutchinson] | ||||||
| hermes | 1248 | tcp | hermes | ||||||||
| hermes | 1248 | udp | hermes | ||||||||
| mesavistaco | 1249 | tcp | Mesa Vista Co | [Rick_LaBanca] | [Rick_LaBanca] | ||||||
| mesavistaco | 1249 | udp | Mesa Vista Co | [Rick_LaBanca] | [Rick_LaBanca] | ||||||
| elatelink | 2124 | tcp | ELATELINK | [Tim_Lawrence] | [Tim_Lawrence] | ||||||
| elatelink | 2124 | udp | ELATELINK | [Tim_Lawrence] | [Tim_Lawrence] | ||||||
| beacon-port | 3124 | tcp | Beacon Port | [James_Paul_Duncan] | [James_Paul_Duncan] | ||||||
| beacon-port | 3124 | udp | Beacon Port | [James_Paul_Duncan] | [James_Paul_Duncan] | ||||||
| tigv2 | 4124 | tcp | Rohill TetraNode Ip Gateway v2 | [Bert_Bouwers] | [Bert_Bouwers] | 2007-05 | |||||
| tigv2 | 4124 | udp | Rohill TetraNode Ip Gateway v2 | [Bert_Bouwers] | [Bert_Bouwers] | 2007-05 | |||||
| pnbs | 6124 | tcp | Phlexible Network Backup Service | [William_R_Lear_2] | [William_R_Lear_2] | 2008-10-23 | |||||
| pnbs | 6124 | udp | Phlexible Network Backup Service | [William_R_Lear_2] | [William_R_Lear_2] | 2008-10-23 | |||||
| 7124-7127 | Unassigned | ||||||||||
| 9124-9130 | Unassigned | ||||||||||
| 10118-10124 | Unassigned | ||||||||||
| 22006-22124 | Unassigned | ||||||||||
| 33124-33330 | Unassigned | ||||||||||
| 44124-44320 | Unassigned |
Contact Information
| ID | Name | Contact URI | Last Updated |
|---|---|---|---|
| [Arnold_Dittmann] | Arnold Dittmann | mailto:dittmann&isbcad.de | |
| [Bert_Bouwers] | Bert Bouwers | mailto:e.bouwers&rohill.nl | 2007-05 |
| [David_Wilson] | David Wilson | mailto:dwilson&integral-ie.com | |
| [Gavin_Hutchinson] | Gavin Hutchinson | mailto:gavinh&visionlogistics.com | |
| [Hal_Henderson] | Hal Henderson | mailto:hhenders&novell.com | |
| [James_Paul_Duncan] | James Paul Duncan | mailto:pduncan&beaconcrm.com | |
| [Jordan_Hrycaj] | Jordan Hrycaj | mailto:jordan&mjh.teddy-net.com | |
| [Nicola_J_Howarth] | Nicola J. Howarth | mailto:njh&ansa.co.uk | |
| [Rick_LaBanca] | Rick LaBanca | mailto:rel&mesasys.com | |
| [Ruth_Slater] | Ruth Slater | mailto:ruth.slater&ideagen.co.uk | |
| [Stephen_LaValley] | Stephen LaValley | mailto:lavalley&lucent.com | |
| [Tim_Lawrence] | Tim Lawrence | mailto:lawrence&tao-group.com | |
| [William_R_Lear_2] | William R. Lear | mailto:wlear&phlexible.com | 2008-10-23 |