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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 38473-38637 | Unassigned | ||||||||||
| psqlmws | 38638 | tcp | Premier SQL Middleware Server | [Brain_Patchwork_DX_LLC] | [Ozz_Nixon] | 2022-02-15 | |||||
| 38638 | udp | Reserved | |||||||||
| 38639-38799 | Unassigned | ||||||||||
| 38801-38864 | Unassigned | ||||||||||
| secrmmsafecopya | 38865 | tcp | Security approval process for use of the secRMM SafeCopy program | [Squadra_Technologies] | [Anthony_LaMark] | 2012-03-14 | |||||
| 38865 | udp | Reserved | |||||||||
| 38866-39062 | Unassigned | ||||||||||
| 45186-45513 | Unassigned | ||||||||||
| 48557-48618 | Unassigned | ||||||||||
| iqobject | 48619 | tcp | iqobject | [Bjorn_de_Bonnenfant] | [Bjorn_de_Bonnenfant] | 2003-11 | |||||
| iqobject | 48619 | udp | iqobject | [Bjorn_de_Bonnenfant] | [Bjorn_de_Bonnenfant] | 2003-11 | |||||
| 48620-48652 | Unassigned | ||||||||||
| robotraconteur | 48653 | tcp | Robot Raconteur transport | [Wason_Technology_LLC] | [John_Wason] | 2014-01-27 | |||||
| robotraconteur | 48653 | udp | Robot Raconteur transport | [Wason_Technology_LLC] | [John_Wason] | 2014-01-27 | |||||
| 48654-48999 | Unassigned | ||||||||||
| im | tcp | Instant Messaging | [RFC3861] | ||||||||
| im | udp | Instant Messaging | [RFC3861] | ||||||||
| jmap | tcp | JSON Meta Application Protocol | [IESG] | [IETF_Chair] | 2016-01-22 | 2019-07-16 | [RFC8620] | This service name was previously assigned under the name "JSON Mail Access Protocol". This has been de-assigned and re-assigned with the approval of the previous assignee. | |||
| 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 | |||||
| pkixrep | Public Key Infrastructure Repository Locator Service | [RFC4386] | |||||||||
| pres | tcp | Presence | [RFC3861] | ||||||||
| pres | udp | Presence | [RFC3861] |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Anthony_LaMark] | Anthony LaMark | Squadra Technologies | mailto:anthony&squadratechnologies.com | 2012-03-14 |
| [Bjorn_de_Bonnenfant] | Bjorn de Bonnenfant | mailto:bdeb&iqobject.com | 2003-11 | |
| [Brain_Patchwork_DX_LLC] | Brain Patchwork DX, LLC. | mailto:specifications&brainpatchworkdx.com | 2022-02-15 | |
| [IESG] | IESG | mailto:iesg&ietf.org | ||
| [IETF_Chair] | IETF Chair | IETF | mailto:chair&ietf.org | |
| [John_Wason] | John Wason | Wason Technology, LLC | mailto:wason&wasontech.com | 2014-01-27 |
| [Ozz_Nixon] | Ozz Nixon | Brain Patchwork DX, LLC. | mailto:specifications&bpdx.com | 2022-02-15 |
| [Patrick_Stein] | Patrick Stein | mailto:Patrick.Stein&jinx.eu | 2011-10-24 | |
| [Squadra_Technologies] | Squadra Technologies | mailto:anthony&squadratechnologies.com | 2012-03-14 | |
| [Wason_Technology_LLC] | Wason Technology, LLC | mailto:wason&wasontech.com | 2014-01-27 |