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
ingres-net 134 tcp INGRES-NET Service [Mike_Berrow] [Mike_Berrow]
ingres-net 134 udp INGRES-NET Service [Mike_Berrow] [Mike_Berrow]
aplx 1134 tcp MicroAPL APLX [Richard_Nabavi] [Richard_Nabavi] 2006-02
aplx 1134 udp MicroAPL APLX [Richard_Nabavi] [Richard_Nabavi] 2006-02
naap 1340 tcp NAAP [Henry_Haverinen] [Henry_Haverinen]
naap 1340 udp NAAP [Henry_Haverinen] [Henry_Haverinen]
qubes 1341 tcp QuBES [Eric_Grange] [Eric_Grange]
qubes 1341 udp QuBES [Eric_Grange] [Eric_Grange]
esbroker 1342 tcp ESBroker [Alexander_Medvinsky] [Alexander_Medvinsky]
esbroker 1342 udp ESBroker [Alexander_Medvinsky] [Alexander_Medvinsky]
re101 1343 tcp re101 [Doriano_Blengino] [Doriano_Blengino]
re101 1343 udp re101 [Doriano_Blengino] [Doriano_Blengino]
icap 1344 tcp ICAP [Jeremy_Elson] [Jeremy_Elson]
icap 1344 udp ICAP [Jeremy_Elson] [Jeremy_Elson]
vpjp 1345 tcp VPJP [Michael_Collins] [Michael_Collins]
vpjp 1345 udp VPJP [Michael_Collins] [Michael_Collins]
alta-ana-lm 1346 tcp Alta Analytics License Manager
alta-ana-lm 1346 udp Alta Analytics License Manager
bbn-mmc 1347 tcp multi media conferencing
bbn-mmc 1347 udp multi media conferencing
bbn-mmx 1348 tcp multi media conferencing
bbn-mmx 1348 udp multi media conferencing
sbook 1349 tcp Registration Network Protocol
sbook 1349 udp Registration Network Protocol
avenue 2134 tcp AVENUE [Jason_Cater] [Jason_Cater]
avenue 2134 udp AVENUE [Jason_Cater] [Jason_Cater]
ecp 3134 tcp Extensible Code Protocol [Jim_Trek][Mark_Bocko] [Jim_Trek][Mark_Bocko]
ecp 3134 udp Extensible Code Protocol [Jim_Trek][Mark_Bocko] [Jim_Trek][Mark_Bocko]
nifty-hmi 4134 tcp NIFTY-Serve HMI protocol [Ryuichi_Suzuki] [Ryuichi_Suzuki]
nifty-hmi 4134 udp NIFTY-Serve HMI protocol [Ryuichi_Suzuki] [Ryuichi_Suzuki]
ppactivation 5134 tcp PP ActivationServer [Ian_Bradley] [Ian_Bradley] 2009-10-14
5134 udp Reserved
6134-6139 Unassigned
doip-data 13400 tcp DoIP Data [Joerg_Schneider] [Joerg_Schneider] 2011-01-26
doip-disc 13400 udp DoIP Discovery [Joerg_Schneider] [Joerg_Schneider] 2011-01-26
13401-13719 Unassigned
26134-26207 Unassigned

Contact Information

ID Name Contact URI Last Updated
[Alexander_Medvinsky] Alexander Medvinsky mailto:smedvinsky&gi.com
[Doriano_Blengino] Doriano Blengino mailto:tecnico_remove_&_remove_xonelectronics.it
[Eric_Grange] Eric Grange mailto:egrange&creative-it.net 2002-08
[Henry_Haverinen] Henry Haverinen mailto:henry.haverinen&nokia.com
[Ian_Bradley] Ian Bradley mailto:ian.bradley&pocketprograms.com
mailto:development&pocketprograms.com
2009-10-14
[Jason_Cater] Jason Cater mailto:jason&ncsmags.com
[Jeremy_Elson] Jeremy Elson mailto:jelson&isi.edu
[Jim_Trek] Jim Trek mailto:jtrek&rochester.rr.com
[Joerg_Schneider] Joerg Schneider mailto:joerg.s.schneider&daimler.com 2011-01-26
[Mark_Bocko] Mark Bocko mailto:bocko&ece.rochester.edu
[Michael_Collins] Michael Collins mailto:UBMCollins&aol.com
[Mike_Berrow] Mike Berrow
[Richard_Nabavi] Richard Nabavi mailto:nabavi&microapl.co.uk 2006-02
[Ryuichi_Suzuki] Ryuichi Suzuki mailto:SCI00376&niftyserve.or.jp