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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| snpp | 444 | tcp | Simple Network Paging Protocol | [RFC1568] | |||||||
| snpp | 444 | udp | Simple Network Paging Protocol | [RFC1568] | |||||||
| ms-shuttle | 568 | tcp | microsoft shuttle | [Rudolph_Balaz] | [Rudolph_Balaz] | ||||||
| ms-shuttle | 568 | udp | microsoft shuttle | [Rudolph_Balaz] | [Rudolph_Balaz] | ||||||
| tsspmap | 1568 | tcp | tsspmap | [Paul_W_Nelson] | [Paul_W_Nelson] | ||||||
| tsspmap | 1568 | udp | tsspmap | [Paul_W_Nelson] | [Paul_W_Nelson] | ||||||
| spamtrap | 2568 | tcp | SPAM TRAP | [Charles_Bennett] | [Charles_Bennett] | 2008-08-29 | |||||
| spamtrap | 2568 | udp | SPAM TRAP | [Charles_Bennett] | [Charles_Bennett] | 2008-08-29 | |||||
| dof-tunnel-sec | 3568 | tcp | DOF Secure Tunnel | [OpenDOF] | [Bryant_Eastham] | 2003-01 | 2015-04-23 | ||||
| dof-tunnel-sec | 3568 | udp | DOF Secure Tunnel | [OpenDOF] | [Bryant_Eastham] | 2003-01 | 2015-04-23 | ||||
| bmc-reporting | 4568 | tcp | BMC Reporting | [Portnoy_Boxman] | [Portnoy_Boxman] | ||||||
| bmc-reporting | 4568 | udp | BMC Reporting | [Portnoy_Boxman] | [Portnoy_Boxman] | ||||||
| sdt | 5568 | tcp | Session Data Transport Multicast | [Daniel_W_Antonuk] | [Daniel_W_Antonuk] | 2006-05 | |||||
| sdt | 5568 | udp | Session Data Transport Multicast | [Daniel_W_Antonuk] | [Daniel_W_Antonuk] | 2006-05 | |||||
| auriga-router | 5680 | tcp | Auriga Router Service | [Vincent_Gaudeul] | [Vincent_Gaudeul] | 2006-02 | |||||
| auriga-router | 5680 | udp | Auriga Router Service | [Vincent_Gaudeul] | [Vincent_Gaudeul] | 2006-02 | |||||
| ncxcp | 5681 | tcp | Net-coneX Control Protocol | [Ryan_Werber] | [Ryan_Werber] | 2006-06 | |||||
| ncxcp | 5681 | udp | Net-coneX Control Protocol | [Ryan_Werber] | [Ryan_Werber] | 2006-06 | |||||
| 5682 | tcp | Reserved | |||||||||
| brightcore | 5682 | udp | BrightCore control & data transfer exchange | [Marko_Bjelac] | [Marko_Bjelac] | 2010-06-10 | |||||
| coap | 5683 | tcp | Constrained Application Protocol (CoAP) | [IESG] | [IETF_Chair] | 2017-12-22 | [RFC8323] | ||||
| coap | 5683 | udp | Constrained Application Protocol | [IESG] | [IETF_Chair] | 2011-06-13 | 2013-07-25 | [RFC7252] | |||
| 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] | ||||
| 5685-5686 | Unassigned | ||||||||||
| gog-multiplayer | 5687 | udp | GOG multiplayer game protocol | [GOG.com] | [Michal_Gruchala] | 2014-07-31 | 2014-10-09 | ||||
| 5687 | tcp | Reserved | |||||||||
| ggz | 5688 | tcp | GGZ Gaming Zone | [Josef_Spillner] | [Josef_Spillner] | 2003-01 | |||||
| ggz | 5688 | udp | GGZ Gaming Zone | [Josef_Spillner] | [Josef_Spillner] | 2003-01 | |||||
| qmvideo | 5689 | tcp | QM video network management protocol | [Jamie_Lokier] | [Jamie_Lokier] | 2006-05 | |||||
| qmvideo | 5689 | udp | QM video network management protocol | [Jamie_Lokier] | [Jamie_Lokier] | 2006-05 | |||||
| canit-store | 6568 | tcp | CanIt Storage Manager IANA assigned this well-formed service name as a replacement for "canit_store". |
[Dianne_Skoll] | [Dianne_Skoll] | 2009-04-22 | 2017-05-25 | ||||
| canit_store | 6568 | tcp | CanIt Storage Manager | [Dianne_Skoll] | [Dianne_Skoll] | 2009-04-22 | 2017-05-25 | This entry is an alias to "canit-store". This entry is now historic, not usable for use with many common service discovery mechanisms. | |||
| rp-reputation | 6568 | udp | Roaring Penguin IP Address Reputation Collection | [Dianne_Skoll] | [Dianne_Skoll] | 2010-02-05 | 2017-05-25 | ||||
| 7567-7568 | Unassigned | ||||||||||
| 8568-8599 | Unassigned | ||||||||||
| 34568-34961 | Unassigned |