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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| dctp | 675 | tcp | DCTP | [Andre_Kramer] | [Andre_Kramer] | ||||||
| dctp | 675 | udp | DCTP | [Andre_Kramer] | [Andre_Kramer] | ||||||
| 6a44 | 1027 | udp | IPv6 Behind NAT44 CPEs | [IESG] | [IETF_Chair] | 2012-08-02 | [RFC6751] | ||||
| pdp | 1675 | tcp | Pacific Data Products | [Gary_Morton] | [Gary_Morton] | ||||||
| pdp | 1675 | udp | Pacific Data Products | [Gary_Morton] | [Gary_Morton] | ||||||
| ttc-etap | 2675 | tcp | TTC ETAP | [Daniel_Becker] | [Daniel_Becker] | ||||||
| ttc-etap | 2675 | udp | TTC ETAP | [Daniel_Becker] | [Daniel_Becker] | ||||||
| calltrax | 3675 | tcp | CallTrax Data Port | [Oliver_Bailey] | [Oliver_Bailey] | 2003-01 | |||||
| calltrax | 3675 | udp | CallTrax Data Port | [Oliver_Bailey] | [Oliver_Bailey] | 2003-01 | |||||
| dhct-status | 4675 | tcp | BIAP Device Status | ||||||||
| dhct-status | 4675 | udp | BIAP Device Status | ||||||||
| v5ua | 5675 | tcp | V5UA application port | [RFC3807] | |||||||
| v5ua | 5675 | udp | V5UA application port | [RFC3807] | |||||||
| v5ua | 5675 | sctp | V5UA application port | [RFC3807] | |||||||
| imqtunnel | 7675 | tcp | iMQ Tunnel | [Shailesh_S_Bavadeka] | [Shailesh_S_Bavadeka] | 2002-04 | |||||
| imqtunnel | 7675 | udp | iMQ Tunnel | [Shailesh_S_Bavadeka] | [Shailesh_S_Bavadeka] | 2002-04 | |||||
| msi-cps-rm | 8675 | tcp | Motorola Solutions Customer Programming Software for Radio Management | [Motorola_Solutions_Inc] | [Jenish_Amin] | 2012-03-14 | |||||
| msi-cps-rm-disc | 8675 | udp | Motorola Solutions Customer Programming Software for Radio Management Discovery | [Motorola_Solutions_Inc] | [Jenish_Amin] | 2012-03-14 | |||||
| 24667-24675 | Unassigned | ||||||||||
| 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 |
|---|---|---|---|---|
| [Andre_Kramer] | Andre Kramer | mailto:Andre.Kramer&ansa.co.uk | ||
| [Daniel_Becker] | Daniel Becker | mailto:becker2d&ttc.com | ||
| [Gary_Morton] | Gary Morton | mailto:mortong&pacdata.com | ||
| [IESG] | IESG | mailto:iesg&ietf.org | ||
| [IETF_Chair] | IETF Chair | IETF | mailto:chair&ietf.org | |
| [Jenish_Amin] | Jenish Amin | Motorola Solutions, Inc. | mailto:jenish&motorolasolutions.com | 2012-03-14 |
| [Motorola_Solutions_Inc] | Motorola Solutions, Inc. | mailto:jenish&motorolasolutions.com | 2012-03-14 | |
| [Oliver_Bailey] | Oliver Bailey | mailto:zzf66jjlm&time-lines.com | 2003-01 | |
| [Patrick_Stein] | Patrick Stein | mailto:Patrick.Stein&jinx.eu | 2011-10-24 | |
| [Shailesh_S_Bavadeka] | Shailesh S. Bavadekar | mailto:shailesh.bavadekar&sun.com | 2002-04 |