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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| apex-mesh | 912 | tcp | APEX relay-relay service | ||||||||
| apex-mesh | 912 | udp | APEX relay-relay service | ||||||||
| rhp-iibp | 1912 | tcp | rhp-iibp | [George_Nachman][Tom_Lake] | [George_Nachman][Tom_Lake] | ||||||
| rhp-iibp | 1912 | udp | rhp-iibp | [George_Nachman][Tom_Lake] | [George_Nachman][Tom_Lake] | ||||||
| epicon | 2912 | tcp | Epicon | [Michael_Khalandovsky] | [Michael_Khalandovsky] | ||||||
| epicon | 2912 | udp | Epicon | [Michael_Khalandovsky] | [Michael_Khalandovsky] | ||||||
| gbmt-stars | 3912 | tcp | Global Maintech Stars | [Harry_Goldschmitt] | [Harry_Goldschmitt] | 2003-11 | |||||
| gbmt-stars | 3912 | udp | Global Maintech Stars | [Harry_Goldschmitt] | [Harry_Goldschmitt] | 2003-11 | |||||
| lutap | 4912 | tcp | Technicolor LUT Access Protocol | [Markus_Loeffler] | [Markus_Loeffler] | 2009-02-17 | |||||
| 4912 | udp | Reserved | |||||||||
| ais-met | 5912 | tcp | Aeronautical Information Service/Meteorological applications using ACARS | [Eivan_Cerasi] | [Greg_Saccone] | 2008-10-10 | 2022-08-08 | ||||
| ais-met | 5912 | udp | Aeronautical Information Service/Meteorological applications using ACARS | [Eivan_Cerasi] | [Greg_Saccone] | 2008-10-10 | 2022-08-08 | ||||
| fis | 5912 | sctp | Flight Information Services | [Justin_Yu] | [Justin_Yu] | 2011-05-25 | |||||
| 7904-7912 | Unassigned | ||||||||||
| wcbackup | 8912 | tcp | Windows Client Backup | [Jim_Lyon] | [Jim_Lyon] | 2005-11 | |||||
| wcbackup | 8912 | udp | Windows Client Backup | [Jim_Lyon] | [Jim_Lyon] | 2005-11 | |||||
| 9120-9121 | Unassigned | ||||||||||
| grcmp | 9122 | tcp | Global Relay compliant mobile instant messaging protocol | [Global_Relay_Communications_Inc] | [Lu_Vo] | 2012-11-28 | 2025-06-12 | ||||
| 9122 | udp | Reserved | |||||||||
| grcp | 9123 | tcp | Global Relay compliant instant messaging protocol | [Global_Relay_Communications_Inc] | [Lu_Vo] | 2012-11-28 | 2025-06-12 | ||||
| 9123 | udp | Reserved | |||||||||
| 9124-9130 | Unassigned | ||||||||||
| 9912-9924 | Unassigned |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Eivan_Cerasi] | Eivan Cerasi | mailto:eivan.cerasi&eurocontrol.int | 2022-08-08 | |
| [George_Nachman] | George Nachman | |||
| [Global_Relay_Communications_Inc] | Global Relay Communications Inc | mailto:info&globalrelay.net | 2025-06-12 | |
| [Greg_Saccone] | Greg Saccone | mailto:gregory.t.saccone&boeing.com | 2022-08-08 | |
| [Harry_Goldschmitt] | Harry Goldschmitt | mailto:hgoldschmitt&hgac.com | 2003-11 | |
| [Jim_Lyon] | Jim Lyon | mailto:JimLyonµsoft.com | 2005-11 | |
| [Justin_Yu] | Justin Yu | mailto:yyu&mitre.org | 2011-05-25 | |
| [Lu_Vo] | Lu Vo | Global Relay Communications Inc | mailto:lu.vo&globalrelay.net | 2025-06-12 |
| [Markus_Loeffler] | Markus Loeffler | mailto:markus.loeffler&thomson.net | 2009-02-17 | |
| [Michael_Khalandovsky] | Michael Khalandovsky | mailto:mlk&epicon.com | ||
| [Tom_Lake] | Tom Lake | mailto:tlake&m-ware.com |