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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| mondex | 471 | tcp | Mondex | [Bill_Reding] | [Bill_Reding] | ||||||
| mondex | 471 | udp | Mondex | [Bill_Reding] | [Bill_Reding] | ||||||
| csdmbase | 1471 | tcp | csdmbase | ||||||||
| csdmbase | 1471 | udp | csdmbase | ||||||||
| seaodbc | 2471 | tcp | SeaODBC | [Adrian_Hornby] | [Adrian_Hornby] | ||||||
| seaodbc | 2471 | udp | SeaODBC | [Adrian_Hornby] | [Adrian_Hornby] | ||||||
| jt400-ssl | 3471 | tcp | jt400-ssl | [Clifton_Nock] | [Clifton_Nock] | ||||||
| jt400-ssl | 3471 | udp | jt400-ssl | [Clifton_Nock] | [Clifton_Nock] | ||||||
| 4705-4710 | Unassigned | ||||||||||
| trinity-dist | 4711 | tcp | Trinity Trust Network Node Communication | [P3KI_GmbH] | [Gregor_Jehle] | 2017-01-12 | |||||
| trinity-dist | 4711 | udp | Trinity Trust Network Node Communication | [P3KI_GmbH] | [Gregor_Jehle] | 2017-01-12 | |||||
| trinity-dist | 4711 | sctp | Trinity Trust Network Node Communication | [P3KI_GmbH] | [Gregor_Jehle] | 2017-01-12 | |||||
| 4712-4724 | Unassigned | ||||||||||
| apsolab-cols | 5471 | tcp | The Apsolab company's secure data collection protocol (native api) | [Apsolab_Inc] | [Jean-Francois_Gauthier] | 2014-11-10 | |||||
| 5471 | udp | Reserved | |||||||||
| lvision-lm | 6471 | tcp | LVision License Manager | [Brian_McKinnon] | [Brian_McKinnon] | ||||||
| lvision-lm | 6471 | udp | LVision License Manager | [Brian_McKinnon] | [Brian_McKinnon] | ||||||
| sttunnel | 7471 | tcp | Stateless Transport Tunneling Protocol | [Bruce_Davie_3] | [Bruce_Davie_3] | 2014-04-28 | |||||
| 7471 | udp | Reserved | |||||||||
| raqmon-pdu | 7744 | tcp | RAQMON PDU | [RFC4712] | |||||||
| raqmon-pdu | 7744 | udp | RAQMON PDU | [RFC4712] | |||||||
| pim-port | 8471 | tcp | PIM over Reliable Transport | [IESG] | [IETF_Chair] | 2008-08-21 | [RFC6559] | ||||
| pim-port | 8471 | sctp | PIM over Reliable Transport | [IESG] | [IETF_Chair] | 2008-08-21 | [RFC6559] | ||||
| 8471 | udp | Reserved | |||||||||
| rna | 25471 | sctp | RNSAP User Adaptation for Iurh | [Dario_S_Tonesi] | [Dario_S_Tonesi] | 2011-02-07 | |||||
| 36866-37471 | Unassigned | ||||||||||
| 38463-38471 | Unassigned | ||||||||||
| jvl-mactalk | 47100 | udp | Configuration of motors connected to Industrial Ethernet | [JVL_Industri_Elektronik] | [Kim_Berthelsen] | 2012-12-21 | |||||
| 47100 | tcp | Reserved | |||||||||
| 47101-47556 | 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 |