Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2026-05-11
- 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| epp | 700 | tcp | Extensible Provisioning Protocol | [RFC5734] | |||||||
| epp | 700 | udp | Extensible Provisioning Protocol | [RFC5734] | |||||||
| els | 1315 | tcp | E.L.S., Event Listener Service | [Jim_Cleppe] | [Jim_Cleppe] | ||||||
| els | 1315 | udp | E.L.S., Event Listener Service | [Jim_Cleppe] | [Jim_Cleppe] | ||||||
| eppc | 3031 | tcp | Remote AppleEvents/PPC Toolbox | [Steve_Zellers] | [Steve_Zellers] | ||||||
| eppc | 3031 | udp | Remote AppleEvents/PPC Toolbox | [Steve_Zellers] | [Steve_Zellers] | ||||||
| epp | 3044 | tcp | EndPoint Protocol | [Stephen_Cipolli] | [Stephen_Cipolli] | ||||||
| epp | 3044 | udp | EndPoint Protocol | [Stephen_Cipolli] | [Stephen_Cipolli] | ||||||
| acplt | 7509 | tcp | ACPLT - process automation service | [Chair_for_Process_Control_Engineering] | [Ulrich_Epple] | 2010-12-07 | 2012-08-07 |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Chair_for_Process_Control_Engineering] | The Chair for Process Control Engineering | mailto:ks&plt.rwth-aachen.de | 2012-08-07 | |
| [Jim_Cleppe] | Jim Cleppe | mailto:clep13&hotmail.com | ||
| [Stephen_Cipolli] | Stephen Cipolli | mailto:scipolli&radvision.com | ||
| [Steve_Zellers] | Steve Zellers | mailto:zellers&apple.com | ||
| [Ulrich_Epple] | Ulrich Epple | mailto:ks&plt.rwth-aachen.de | 2012-08-07 |