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
videotex 516 tcp videotex [Daniel_Mavrakis] [Daniel_Mavrakis]
videotex 516 udp videotex [Daniel_Mavrakis] [Daniel_Mavrakis]
vpad 1516 tcp Virtual Places Audio data
vpad 1516 udp Virtual Places Audio data
maincontrol 2516 tcp Main Control [Nathan_Sadia] [Nathan_Sadia]
maincontrol 2516 udp Main Control [Nathan_Sadia] [Nathan_Sadia]
smartcard-port 3516 tcp Smartcard Port [Scott_Guthery] [Scott_Guthery] 2002-05
smartcard-port 3516 udp Smartcard Port [Scott_Guthery] [Scott_Guthery] 2002-05
5158-5160 Unassigned
snmpssh 5161 tcp SNMP over SSH Transport Model [RFC5592]
5161 udp Reserved
snmpssh-trap 5162 tcp SNMP Notification over SSH Transport Model [RFC5592] Known Unauthorized Use on port 5162
5162 udp Reserved Known Unauthorized Use on port 5162
sbackup 5163 tcp Shadow Backup [Glenn_Allen] [Glenn_Allen] 2009-08-05
5163 udp Reserved
vpa 5164 tcp Virtual Protocol Adapter [Douglas_Goodall] [Douglas_Goodall] 2009-08-05
vpa-disc 5164 udp Virtual Protocol Adapter Discovery [Douglas_Goodall] [Douglas_Goodall] 2009-08-05
ife-icorp 5165 tcp ife_1corp

IANA assigned this well-formed service name as a replacement for "ife_icorp".
[Paul_Annala] [Paul_Annala]
ife_icorp 5165 tcp ife_1corp [Paul_Annala] [Paul_Annala] This entry is an alias to "ife-icorp". This entry is now historic, not usable for use with many common service discovery mechanisms.
ife-icorp 5165 udp ife_1corp

IANA assigned this well-formed service name as a replacement for "ife_icorp".
[Paul_Annala] [Paul_Annala]
ife_icorp 5165 udp ife_1corp [Paul_Annala] [Paul_Annala] This entry is an alias to "ife-icorp". This entry is now historic, not usable for use with many common service discovery mechanisms.
winpcs 5166 tcp WinPCS Service Connection [Complan_Network_AS] [Complan_Network_AS] 2006-02
winpcs 5166 udp WinPCS Service Connection [Complan_Network_AS] [Complan_Network_AS] 2006-02
scte104 5167 tcp SCTE104 Connection [Thomas_Russell] [Thomas_Russell] 2005-05
scte104 5167 udp SCTE104 Connection [Thomas_Russell] [Thomas_Russell] 2005-05
scte30 5168 tcp SCTE30 Connection [Thomas_Russell] [Thomas_Russell] 2005-05
scte30 5168 udp SCTE30 Connection [Thomas_Russell] [Thomas_Russell] 2005-05
5169-5171 Unassigned
6516-6542 Unassigned
18516 tcp Reserved
heythings 18516 udp HeyThings Device communicate service [Guangdong_OPPO_Mobile_Telecommunications_Corp_Ltd] [Zhai_Zhaoxuan] 2020-05-13 Defined TXT keys: heythings
44446-44543 Unassigned Known UNAUTHORIZED USE: Ports 44515 & 44516

Contact Information

ID Name Organization Contact URI Last Updated
[Complan_Network_AS] Complan Network AS mailto:knut&winpcs.com 2006-02
[Daniel_Mavrakis] Daniel Mavrakis mailto:system&venus.mctel.fr
[Douglas_Goodall] Douglas Goodall mailto:douglas_goodall&mac.com 2009-08-05
[Glenn_Allen] Glenn Allen mailto:gallen&goorooinc.com 2009-08-05
[Guangdong_OPPO_Mobile_Telecommunications_Corp_Ltd] Guangdong OPPO Mobile Telecommunications Corp.,Ltd. mailto:zhaizhaoxuan&oppo.com 2020-05-13
[Nathan_Sadia] Nathan Sadia mailto:sadia&maincontrol.com
[Paul_Annala] Paul Annala mailto:paa&bull.se
[Scott_Guthery] Scott Guthery mailto:sguthery&mobile-mind.com 2002-05
[Thomas_Russell] Thomas Russell mailto:trussell&scte.org 2005-05
[Zhai_Zhaoxuan] Zhai Zhaoxuan Guangdong OPPO Mobile Telecommunications Corp.,Ltd. mailto:zhaizhaoxuan&oppo.com 2020-05-13