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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| teedtap | 559 | tcp | TEEDTAP | [Charlie_Limoges] | [Charlie_Limoges] | ||||||
| teedtap | 559 | udp | TEEDTAP | [Charlie_Limoges] | [Charlie_Limoges] | ||||||
| web2host | 1559 | tcp | web2host | [Stephen_Johnson] | [Stephen_Johnson] | ||||||
| web2host | 1559 | udp | web2host | [Stephen_Johnson] | [Stephen_Johnson] | ||||||
| lstp | 2559 | tcp | LSTP | [Waiki_Wright] | [Waiki_Wright] | ||||||
| lstp | 2559 | udp | LSTP | [Waiki_Wright] | [Waiki_Wright] | ||||||
| cctv-port | 3559 | tcp | CCTV control port | [John_Skidmore] | [John_Skidmore] | 2002-07 | |||||
| cctv-port | 3559 | udp | CCTV control port | [John_Skidmore] | [John_Skidmore] | 2002-07 | |||||
| hylafax | 4559 | tcp | HylaFAX | [Lee_Howard] | [Lee_Howard] | 2002-03 | |||||
| hylafax | 4559 | udp | HylaFAX | [Lee_Howard] | [Lee_Howard] | 2002-03 | |||||
| snmpssh | 5161 | tcp | SNMP over SSH Transport Model | [RFC5592] | |||||||
| snmpssh-trap | 5162 | tcp | SNMP Notification over SSH Transport Model | [RFC5592] | Known Unauthorized Use on port 5162 | ||||||
| 5587-5596 | Unassigned | ||||||||||
| ininmessaging | 5597 | tcp | inin secure messaging | [Mike_Gagle_2] | [Mike_Gagle_2] | 2006-05 | |||||
| ininmessaging | 5597 | udp | inin secure messaging | [Mike_Gagle_2] | [Mike_Gagle_2] | 2006-05 | |||||
| mctfeed | 5598 | tcp | MCT Market Data Feed | [Stephane_Touizer] | [Stephane_Touizer] | 2006-05 | |||||
| mctfeed | 5598 | udp | MCT Market Data Feed | [Stephane_Touizer] | [Stephane_Touizer] | 2006-05 | |||||
| esinstall | 5599 | tcp | Enterprise Security Remote Install | [Kimberly_Gibbs] | [Kimberly_Gibbs] | ||||||
| esinstall | 5599 | udp | Enterprise Security Remote Install | [Kimberly_Gibbs] | [Kimberly_Gibbs] | ||||||
| 6559-6565 | Unassigned | ||||||||||
| 7552-7559 | Unassigned | ||||||||||
| pim-port | 8471 | tcp | PIM over Reliable Transport | [IESG] | [IETF_Chair] | 2008-08-21 | [RFC6559] | ||||
| pim-port | 8471 | sctp | PIM over Reliable Transport | [IESG] | [IETF_Chair] | 2008-08-21 | [RFC6559] | ||||
| p4runtime | 9559 | tcp | P4Runtime gRPC Service | [Open_Networking_Foundation] | [Antonin_Bas] | 2020-09-22 | |||||
| 9559 | udp | Reserved |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Antonin_Bas] | Antonin Bas | Open Networking Foundation | mailto:antonin.bas&gmail.com | 2020-09-22 |
| [Charlie_Limoges] | Charlie Limoges | mailto:Charlie.Limoges&gdc4s.com | ||
| [IESG] | IESG | mailto:iesg&ietf.org | ||
| [IETF_Chair] | IETF Chair | IETF | mailto:chair&ietf.org | |
| [John_Skidmore] | John Skidmore | mailto:JSkidmore&vicon-cctv.com | 2002-07 | |
| [Kimberly_Gibbs] | Kimberly Gibbs | mailto:kimgib&ccgate-ut.axent.com | ||
| [Lee_Howard] | Lee Howard | mailto:iana&hylafax.org | 2002-03 | |
| [Mike_Gagle_2] | Mike Gagle | mailto:mikeg&inin.com | 2006-05 | |
| [Open_Networking_Foundation] | Open Networking Foundation | mailto:iana&opennetworking.org | 2013-07-18 | |
| [Stephane_Touizer] | Stephane Touizer | mailto:touizerµcaptrade.com | 2006-05 | |
| [Stephen_Johnson] | Stephen Johnson | mailto:sjohnson&mindspring.com | ||
| [Waiki_Wright] | Waiki Wright | mailto:waiki&us.ibm.com |