Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2025-10-22
- Expert(s)
-
TCP/UDP: Joe Touch; Eliot Lear, Kumiko Ono, Wes Eddy, Brian Trammell, Jana Iyengar, 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 |
---|---|---|---|---|---|---|---|---|---|---|---|
http-rpc-epmap | 593 | tcp | HTTP RPC Ep Map | [Edward_Reus] | [Edward_Reus] | ||||||
http-rpc-epmap | 593 | udp | HTTP RPC Ep Map | [Edward_Reus] | [Edward_Reus] | ||||||
mainsoft-lm | 1593 | tcp | mainsoft-lm | [Anand_Gangadharan] | [Anand_Gangadharan] | ||||||
mainsoft-lm | 1593 | udp | mainsoft-lm | [Anand_Gangadharan] | [Anand_Gangadharan] | ||||||
mns-mail | 2593 | tcp | MNS Mail Notice Service | [Rumiko_Kikuta] | [Rumiko_Kikuta] | ||||||
mns-mail | 2593 | udp | MNS Mail Notice Service | [Rumiko_Kikuta] | [Rumiko_Kikuta] | ||||||
bpmd | 3593 | tcp | BP Model Debugger | [Keith_Fligg] | [Keith_Fligg] | 2002-09 | |||||
bpmd | 3593 | udp | BP Model Debugger | [Keith_Fligg] | [Keith_Fligg] | 2002-09 | |||||
ipt-anri-anri | 4593 | tcp | IPT (ANRI-ANRI) | ||||||||
ipt-anri-anri | 4593 | udp | IPT (ANRI-ANRI) | ||||||||
cba8 | 9593 | tcp | LANDesk Management Agent (cba8) | [Trevor_Perkes] | [Trevor_Perkes] | 2010-02-01 | |||||
cba8 | 9593 | udp | LANDesk Management Agent (cba8) | [Trevor_Perkes] | [Trevor_Perkes] | 2010-02-01 |
Contact Information
ID | Name | Contact URI | Last Updated |
---|---|---|---|
[Anand_Gangadharan] | Anand Gangadharan | mailto:anand&goa.mainsoft.com | |
[Edward_Reus] | Edward Reus | mailto:edwardrµsoft.com | |
[Keith_Fligg] | Keith Fligg | mailto:keith&projtech.com | 2002-09 |
[Rumiko_Kikuta] | Rumiko Kikuta | mailto:kiku&nd.net.fujitsu.co.jp | |
[Trevor_Perkes] | Trevor Perkes | mailto:trevor.perkes&landesk.com | 2010-02-01 |