Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2024-11-19
- 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 |
---|---|---|---|---|---|---|---|---|---|---|---|
30101-30259 | Unassigned | ||||||||||
32250-32399 | Unassigned | ||||||||||
34250-34377 | Unassigned | ||||||||||
36425-36442 | Unassigned | ||||||||||
36525-36601 | Unassigned | ||||||||||
41798-42507 | Unassigned | Unauthorized Use Known on port 42000 | |||||||||
candp | 42508 | tcp | Computer Associates network discovery protocol | [Jon_Press] | [Jon_Press] | 2005-09 | |||||
candp | 42508 | udp | Computer Associates network discovery protocol | [Jon_Press] | [Jon_Press] | 2005-09 | |||||
candrp | 42509 | tcp | CA discovery response | [Jon_Press] | [Jon_Press] | 2005-08 | |||||
candrp | 42509 | udp | CA discovery response | [Jon_Press] | [Jon_Press] | 2005-08 | |||||
caerpc | 42510 | tcp | CA eTrust RPC | [Jon_Press] | [Jon_Press] | 2005-08 | |||||
caerpc | 42510 | udp | CA eTrust RPC | [Jon_Press] | [Jon_Press] | 2005-08 | |||||
42511-42998 | Unassigned | ||||||||||
qdb2service | 45825 | tcp | Qpuncture Data Access Service | [Michael_Yun] | [Michael_Yun] | 2007-10-24 | |||||
qdb2service | 45825 | udp | Qpuncture Data Access Service | [Michael_Yun] | [Michael_Yun] | 2007-10-24 | |||||
47625-47805 | Unassigned | ||||||||||
ip-x25 | Internet Protocol on X.25 Networks | ||||||||||
dnssd-srp | tcp | DNS-Based Service Discovery | [IESG] | [IETF_Chair] | 2024-04-12 | 2024-09-05 | [RFC-ietf-dnssd-srp-25] | Defined TXT keys: None | |||
dnssd-srp-tls | tcp | DNS-Based Service Discovery (TLS) | [IESG] | [IETF_Chair] | 2024-04-12 | 2024-09-05 | [RFC-ietf-dnssd-srp-25] | Defined TXT keys: None | |||
jnx-kcsync | tcp | jollys keychain cloud sync protocol | [Patrick_Stein] | [Patrick_Stein] | 2011-10-24 | Defined TXT keys: hash=<40hex characters> salt=<40hex characters> uuid=<40hex characters> Example: hash=5e7580598c0d7064d4fc79faaeb42585e1a675f8 salt=f0164cb3a0c3d7efe75abea8fda86d2d56c8dda9 uuid=db61dc092922252e45bbb264f59147138c7fd5fa |
Contact Information
ID | Name | Organization | Contact URI | Last Updated |
---|---|---|---|---|
[IESG] | IESG | mailto:iesg&ietf.org | ||
[IETF_Chair] | IETF Chair | IETF | mailto:chair&ietf.org | |
[Jon_Press] | Jon Press | mailto:IANA.Registions&ca.com | 2005-09 | |
[Michael_Yun] | Michael Yun | mailto:cinnanda&gmail.com | 2007-10-24 | |
[Patrick_Stein] | Patrick Stein | mailto:Patrick.Stein&jinx.eu | 2011-10-24 |