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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| corba-iiop-ssl | 684 | tcp | CORBA IIOP SSL | [Andrew_Watson] | [Andrew_Watson] | ||||||
| corba-iiop-ssl | 684 | udp | CORBA IIOP SSL | [Andrew_Watson] | [Andrew_Watson] | ||||||
| tbrpf | 712 | tcp | TBRPF | [RFC3684] | |||||||
| tbrpf | 712 | udp | TBRPF | [RFC3684] | |||||||
| snaresecure | 1684 | tcp | SnareSecure | [Marty_Batchelder] | [Marty_Batchelder] | ||||||
| snaresecure | 1684 | udp | SnareSecure | [Marty_Batchelder] | [Marty_Batchelder] | ||||||
| mpnjsosv | 2684 | tcp | mpnjsosv | ||||||||
| mpnjsosv | 2684 | udp | mpnjsosv | ||||||||
| faxstfx-port | 3684 | tcp | FAXstfX | [Alec_Carlson] | [Alec_Carlson] | 2003-01 | |||||
| faxstfx-port | 3684 | udp | FAXstfX | [Alec_Carlson] | [Alec_Carlson] | 2003-01 | |||||
| rfid-rp1 | 4684 | tcp | RFID Reader Protocol 1.0 | [Michael_Mealling_2] | [Michael_Mealling_2] | 2005-08 | |||||
| rfid-rp1 | 4684 | udp | RFID Reader Protocol 1.0 | [Michael_Mealling_2] | [Michael_Mealling_2] | 2005-08 | |||||
| coaps | 5684 | tcp | Constrained Application Protocol (CoAP) | [IESG] | [IETF_Chair] | 2017-12-22 | [RFC7301][RFC8323] | ||||
| coaps | 5684 | udp | DTLS-secured CoAP | [IESG] | [IETF_Chair] | 2013-07-25 | [RFC7252] | ||||
| 6832-6840 | Unassigned | ||||||||||
| netmo-default | 6841 | tcp | Netmo Default | [Urs_Bertschinger] | [Urs_Bertschinger] | ||||||
| netmo-default | 6841 | udp | Netmo Default | [Urs_Bertschinger] | [Urs_Bertschinger] | ||||||
| netmo-http | 6842 | tcp | Netmo HTTP | [Urs_Bertschinger] | [Urs_Bertschinger] | ||||||
| netmo-http | 6842 | udp | Netmo HTTP | [Urs_Bertschinger] | [Urs_Bertschinger] | ||||||
| 6843-6849 | Unassigned | ||||||||||
| 7684-7686 | Unassigned | ||||||||||
| 31621-31684 | Unassigned |
Contact Information
| ID | Name | Organization | Contact URI | Last Updated |
|---|---|---|---|---|
| [Alec_Carlson] | Alec Carlson | mailto:acarlson&smithmicro.com | 2003-01 | |
| [Andrew_Watson] | Andrew Watson | mailto:andrew&omg.org | ||
| [IESG] | IESG | mailto:iesg&ietf.org | ||
| [IETF_Chair] | IETF Chair | IETF | mailto:chair&ietf.org | |
| [Marty_Batchelder] | Marty Batchelder | mailto:marty&capres.com | ||
| [Michael_Mealling_2] | Michael Mealling | mailto:michael&refactored-networks.com | 2005-08 | |
| [Urs_Bertschinger] | Urs Bertschinger | mailto:urs&netmosphere.com |