Service Name and Transport Protocol Port Number Registry
- Last Updated
- 2026-09-02
- 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| ptp-event | 319 | tcp | PTP Event | [Kang_Lee] | [Kang_Lee] | 2010-07-27 | |||||
| ptp-event | 319 | udp | PTP Event | [Kang_Lee] | [Kang_Lee] | 2010-07-27 | |||||
| syslog-conn | 601 | tcp | Reliable Syslog Service | [RFC3195] | |||||||
| syslog-conn | 601 | udp | Reliable Syslog Service | [RFC3195] | |||||||
| amx-icsp | 1319 | tcp | AMX-ICSP | [Jeff_Burch] | [Jeff_Burch] | ||||||
| amx-icsp | 1319 | udp | AMX-ICSP | [Jeff_Burch] | [Jeff_Burch] | ||||||
| infolibria | 2319 | tcp | InfoLibria | [Chris_Chiotasso] | [Chris_Chiotasso] | ||||||
| infolibria | 2319 | udp | InfoLibria | [Chris_Chiotasso] | [Chris_Chiotasso] | ||||||
| csvr-proxy | 3190 | tcp | ConServR Proxy | ||||||||
| csvr-proxy | 3190 | udp | ConServR Proxy | ||||||||
| csvr-sslproxy | 3191 | tcp | ConServR SSL Proxy | [Mikhail_Kruk] | [Mikhail_Kruk] | ||||||
| csvr-sslproxy | 3191 | udp | ConServR SSL Proxy | [Mikhail_Kruk] | [Mikhail_Kruk] | ||||||
| firemonrcc | 3192 | tcp | FireMon Revision Control | [Michael_Bishop] | [Michael_Bishop] | ||||||
| firemonrcc | 3192 | udp | FireMon Revision Control | [Michael_Bishop] | [Michael_Bishop] | ||||||
| spandataport | 3193 | tcp | SpanDataPort | [Jesse_McKay] | [Jesse_McKay] | ||||||
| spandataport | 3193 | udp | SpanDataPort | [Jesse_McKay] | [Jesse_McKay] | ||||||
| magbind | 3194 | tcp | Rockstorm MAG protocol | [Jens_Nilsson] | [Jens_Nilsson] | ||||||
| magbind | 3194 | udp | Rockstorm MAG protocol | [Jens_Nilsson] | [Jens_Nilsson] | ||||||
| ncu-1 | 3195 | tcp | Network Control Unit | ||||||||
| ncu-1 | 3195 | udp | Network Control Unit | ||||||||
| ncu-2 | 3196 | tcp | Network Control Unit | [Charlie_Hundre] | [Charlie_Hundre] | ||||||
| ncu-2 | 3196 | udp | Network Control Unit | [Charlie_Hundre] | [Charlie_Hundre] | ||||||
| embrace-dp-s | 3197 | tcp | Embrace Device Protocol Server | ||||||||
| embrace-dp-s | 3197 | udp | Embrace Device Protocol Server | ||||||||
| embrace-dp-c | 3198 | tcp | Embrace Device Protocol Client | [Elliot_Schwartz] | [Elliot_Schwartz] | ||||||
| embrace-dp-c | 3198 | udp | Embrace Device Protocol Client | [Elliot_Schwartz] | [Elliot_Schwartz] | ||||||
| dmod-workspace | 3199 | tcp | DMOD WorkSpace | [Nick_Plante] | [Nick_Plante] | ||||||
| dmod-workspace | 3199 | udp | DMOD WorkSpace | [Nick_Plante] | [Nick_Plante] | ||||||
| sdt-lmd | 3319 | tcp | SDT License Manager | [Salvo_Nassisi] | [Salvo_Nassisi] | ||||||
| sdt-lmd | 3319 | udp | SDT License Manager | [Salvo_Nassisi] | [Salvo_Nassisi] | ||||||
| skytale | 4319 | tcp | Sentyron SkyTale encrypted communication | [Sentyron_B.V.] | [Mark_Revier] | 2022-01-20 | 2025-10-30 | ||||
| skytale | 4319 | udp | Sentyron SkyTale encrypted communication | [Sentyron_B.V.] | [Mark_Revier] | 2022-01-20 | 2025-10-30 | ||||
| roughtime | 5319 | tcp | Roughtime time synchronization | [IESG] | [IETF_Chair] | 2026-03-27 | [RFC-ietf-ntp-roughtime-19] | ||||
| roughtime | 5319 | udp | Roughtime time synchronization | [IESG] | [IETF_Chair] | 2026-03-27 | [RFC-ietf-ntp-roughtime-19] | ||||
| 6319 | Unassigned | ||||||||||
| 8314-8319 | Unassigned | ||||||||||
| 9319-9320 | Unassigned | ||||||||||
| imip | 11319 | tcp | IMIP | [Len_Zuvela] | [Len_Zuvela] | ||||||
| imip | 11319 | udp | IMIP | [Len_Zuvela] | [Len_Zuvela] | ||||||
| 31766-31947 | Unassigned | ||||||||||
| iceedcp-tx | 31948 | tcp | Embedded Device Configuration Protocol TX IANA assigned this well-formed service name as a replacement for "iceedcp_tx". |
[Oliver_Lewis] | [Oliver_Lewis] | 2006-08 | |||||
| iceedcp_tx | 31948 | tcp | Embedded Device Configuration Protocol TX | [Oliver_Lewis] | [Oliver_Lewis] | 2006-08 | This entry is an alias to "iceedcp-tx". This entry is now historic, not usable for use with many common service discovery mechanisms. | ||||
| iceedcp-tx | 31948 | udp | Embedded Device Configuration Protocol TX IANA assigned this well-formed service name as a replacement for "iceedcp_tx". |
[Oliver_Lewis] | [Oliver_Lewis] | 2006-08 | |||||
| iceedcp_tx | 31948 | udp | Embedded Device Configuration Protocol TX | [Oliver_Lewis] | [Oliver_Lewis] | 2006-08 | This entry is an alias to "iceedcp-tx". This entry is now historic, not usable for use with many common service discovery mechanisms. | ||||
| iceedcp-rx | 31949 | tcp | Embedded Device Configuration Protocol RX IANA assigned this well-formed service name as a replacement for "iceedcp_rx". |
[Oliver_Lewis] | [Oliver_Lewis] | 2006-08 | |||||
| iceedcp_rx | 31949 | tcp | Embedded Device Configuration Protocol RX | [Oliver_Lewis] | [Oliver_Lewis] | 2006-08 | This entry is an alias to "iceedcp-rx". This entry is now historic, not usable for use with many common service discovery mechanisms. | ||||
| iceedcp-rx | 31949 | udp | Embedded Device Configuration Protocol RX IANA assigned this well-formed service name as a replacement for "iceedcp_rx". |
[Oliver_Lewis] | [Oliver_Lewis] | 2006-08 | |||||
| iceedcp_rx | 31949 | udp | Embedded Device Configuration Protocol RX | [Oliver_Lewis] | [Oliver_Lewis] | 2006-08 | This entry is an alias to "iceedcp-rx". This entry is now historic, not usable for use with many common service discovery mechanisms. | ||||
| 31950-32033 | Unassigned | ||||||||||
| ip-provision | 43190 | tcp | IP-PROVISION | [Roman_Kriis] | [Roman_Kriis] | ||||||
| ip-provision | 43190 | udp | IP-PROVISION | [Roman_Kriis] | [Roman_Kriis] | ||||||
| noit-transport | 43191 | tcp | Reconnoiter Agent Data Transport | [Theo_Schlossnagle] | [Theo_Schlossnagle] | 2009-05-19 | |||||
| 43191 | udp | Reserved | |||||||||
| 43192-43209 | Unassigned |