Internet Assigned Numbers Authority

Service Name and Transport Protocol Port Number Registry

Last Updated
2025-03-28
Expert(s)
TCP/UDP: Joe Touch; Eliot Lear, Kumiko Ono, Wes Eddy, Brian Trammell, 
Jana Iyengar, 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
saft 487 tcp saft Simple Asynchronous File Transfer [Ulli_Horlacher] [Ulli_Horlacher]
saft 487 udp saft Simple Asynchronous File Transfer [Ulli_Horlacher] [Ulli_Horlacher]
localinfosrvr 1487 tcp LocalInfoSrvr [Brian_Matthews_2] [Brian_Matthews_2]
localinfosrvr 1487 udp LocalInfoSrvr [Brian_Matthews_2] [Brian_Matthews_2]
pns 2487 tcp Policy Notice Service [Akiyoshi_Ochi] [Akiyoshi_Ochi]
pns 2487 udp Policy Notice Service [Akiyoshi_Ochi] [Akiyoshi_Ochi]
ltctcp 3487 tcp LISA TCP Transfer Channel
ltcudp 3487 udp LISA UDP Transfer Channel [Pit_Vetterick] [Pit_Vetterick] 2002-05
prex-tcp 4487 tcp Protocol for Remote Execution over TCP [Daniel_Ruppert] [Daniel_Ruppert] 2010-09-16
4487 udp Reserved
cc-tracking 4870 tcp Citcom Tracking Service [Wolfgang_Weidner] [Wolfgang_Weidner] 2005-12
cc-tracking 4870 udp Citcom Tracking Service [Wolfgang_Weidner] [Wolfgang_Weidner] 2005-12
wired 4871 tcp Wired [Axel_Andersson] [Axel_Andersson] 2006-02
wired 4871 udp Wired [Axel_Andersson] [Axel_Andersson] 2006-02
4872-4875 Unassigned
tritium-can 4876 tcp Tritium CAN Bus Bridge Service [James_Kennedy] [James_Kennedy] 2011-02-15
tritium-can 4876 udp Tritium CAN Bus Bridge Service [James_Kennedy] [James_Kennedy] 2011-02-15
lmcs 4877 tcp Lighting Management Control System [Timothy_Parry] [Timothy_Parry] 2011-02-15
lmcs 4877 udp Lighting Management Control System [Timothy_Parry] [Timothy_Parry] 2011-02-15
4878 tcp Reserved
inst-discovery 4878 udp Agilent Instrument Discovery [Charles_F_Steele] [Charles_F_Steele] 2011-02-15
wsdl-event 4879 tcp WSDL Event Receiver [Charles_F_Steele] [Charles_F_Steele] 2011-02-15
4879 udp Reserved
sun-sr-iiop-aut 6487 tcp Service Registry Default IIOPAuth Domain [Paul_Sterk] [Paul_Sterk] 2006-03
sun-sr-iiop-aut 6487 udp Service Registry Default IIOPAuth Domain [Paul_Sterk] [Paul_Sterk] 2006-03
exoconfig 26487 tcp EXOconfig [Urban_Fosseus] [Urban_Fosseus] 2008-12-24
exoconfig 26487 udp EXOconfig [Urban_Fosseus] [Urban_Fosseus] 2008-12-24
mtrace 33435 udp IP Multicast Traceroute [IESG] [IETF_Chair] 2017-12-13 2019-08-09 [RFC8487] Known Unauthorized Use on port 33435

Contact Information

ID Name Organization Contact URI Last Updated
[Akiyoshi_Ochi] Akiyoshi Ochi mailto:akiyoshi&net.paso.fujitsu.co.jp
[Axel_Andersson] Axel Andersson mailto:axel&zankasoftware.com 2006-02
[Brian_Matthews_2] Brian Matthews mailto:brian_matthews&ibist.ibis.com
[Charles_F_Steele] Charles F Steele mailto:charles_steele&agilent.com 2011-02-15
[Daniel_Ruppert] Daniel Ruppert mailto:daniel&kaffi.lu 2010-09-16
[IESG] IESG mailto:iesg&ietf.org
[IETF_Chair] IETF Chair IETF mailto:chair&ietf.org
[James_Kennedy] James Kennedy mailto:james&tritium.com.au 2011-02-15
[Paul_Sterk] Paul Sterk mailto:paul.sterk&sun.com 2006-03
[Pit_Vetterick] Pit Vetterick mailto:pit&3dgo.com 2002-05
[Timothy_Parry] Timothy Parry mailto:tim&lumenergi.com 2011-02-15
[Ulli_Horlacher] Ulli Horlacher mailto:framstag&rus.uni-stuttgart.de
[Urban_Fosseus] Urban Fosseus mailto:urban.fosseus&regin.se 2008-12-24
[Wolfgang_Weidner] Wolfgang Weidner mailto:ww&citcom.de 2005-12