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
timed 525 tcp timeserver
timed 525 udp timeserver
orasrv 1525 tcp oracle
orasrv 1525 udp oracle
prospero-np 1525 tcp Prospero Directory Service non-priv
prospero-np 1525 udp Prospero Directory Service non-priv
ms-v-worlds 2525 tcp MS V-Worlds [Pete_Wong] [Pete_Wong]
ms-v-worlds 2525 udp MS V-Worlds [Pete_Wong] [Pete_Wong]
eisport 3525 tcp EIS Server port [Paul_Kraus] [Paul_Kraus] 2002-06
eisport 3525 udp EIS Server port [Paul_Kraus] [Paul_Kraus] 2002-06
soagateway 5250 tcp soaGateway [Greg_Bodine] [Greg_Bodine] 2002-02
soagateway 5250 udp soaGateway [Greg_Bodine] [Greg_Bodine] 2002-02
caevms 5251 tcp CA eTrust VM Service [Kevin_Bond] [Kevin_Bond] 2004-11
caevms 5251 udp CA eTrust VM Service [Kevin_Bond] [Kevin_Bond] 2004-11
movaz-ssc 5252 tcp Movaz SSC [Lou_Berger] [Lou_Berger] 2004-11
movaz-ssc 5252 udp Movaz SSC [Lou_Berger] [Lou_Berger] 2004-11
kpdp 5253 tcp Kohler Power Device Protocol [Bill_Gross] [Bill_Gross] 2010-11-01
5253 udp Reserved
logcabin 5254 tcp LogCabin storage service [Diego_Ongaro] [Diego_Ongaro] 2015-04-14
5254 udp Reserved
5255-5263 Unassigned
36525-36601 Unassigned

Contact Information

ID Name Contact URI Last Updated
[Bill_Gross] Bill Gross mailto:william.gross&kohler.com 2010-11-01
[Diego_Ongaro] Diego Ongaro mailto:ongaro&cs.stanford.edu 2015-04-14
[Greg_Bodine] Greg Bodine mailto:gregory.bodine&ca.com 2002-02
[Kevin_Bond] Kevin Bond mailto:kevin.bond&ca.com 2004-11
[Lou_Berger] Lou Berger mailto:lberger&movaz.com 2004-11
[Paul_Kraus] Paul Kraus mailto:paul.kraus&veritas.com 2002-06
[Pete_Wong] Pete Wong mailto:petewong&microsoft.com