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
ssh 22 tcp The Secure Shell (SSH) Protocol [RFC4251] Defined TXT keys: u=<username> p=<password>
ssh 22 udp The Secure Shell (SSH) Protocol [RFC4251] Defined TXT keys: u=<username> p=<password>
icad-el 425 tcp ICAD [Larry_Stone] [Larry_Stone]
icad-el 425 udp ICAD [Larry_Stone] [Larry_Stone]
zion-lm 1425 tcp Zion Software License Manager [David_Ferrero] [David_Ferrero]
zion-lm 1425 udp Zion Software License Manager [David_Ferrero] [David_Ferrero]
fjitsuappmgr 2425 tcp Fujitsu App Manager [Hiroyuki_Kawabuchi] [Hiroyuki_Kawabuchi]
fjitsuappmgr 2425 udp Fujitsu App Manager [Hiroyuki_Kawabuchi] [Hiroyuki_Kawabuchi]
agps-port 3425 tcp AGPS Access Port [Kristoffer_Nilsson] [Kristoffer_Nilsson] 2002-02
agps-port 3425 udp AGPS Access Port [Kristoffer_Nilsson] [Kristoffer_Nilsson] 2002-02
netrockey6 4425 tcp NetROCKEY6 SMART Plus Service [Feitian_Technologies] [Feitian_Technologies] 2010-09-15
netrockey6 4425 udp NetROCKEY6 SMART Plus Service [Feitian_Technologies] [Feitian_Technologies] 2010-09-15
br-channel 5425 tcp Beyond Remote Command Channel [Michael_Berg] [Michael_Berg] 2005-08
br-channel 5425 udp Beyond Remote Command Channel [Michael_Berg] [Michael_Berg] 2005-08
syslog-tls 6514 tcp Syslog over TLS [RFC5425]
7422-7425 Unassigned
cps 14250 tcp Fencing Server [Mayank_Vasa] [Mayank_Vasa] 2008-04-03
cps 14250 udp Fencing Server [Mayank_Vasa] [Mayank_Vasa] 2008-04-03
14251-14413 Unassigned
24250-24320 Unassigned
34250-34377 Unassigned
36425-36442 Unassigned
41798-42507 Unassigned Unauthorized Use Known on port 42000
candp 42508 tcp Computer Associates network discovery protocol [Jon_Press] [Jon_Press] 2005-09
candp 42508 udp Computer Associates network discovery protocol [Jon_Press] [Jon_Press] 2005-09
candrp 42509 tcp CA discovery response [Jon_Press] [Jon_Press] 2005-08
candrp 42509 udp CA discovery response [Jon_Press] [Jon_Press] 2005-08
caerpc 42510 tcp CA eTrust RPC [Jon_Press] [Jon_Press] 2005-08
caerpc 42510 udp CA eTrust RPC [Jon_Press] [Jon_Press] 2005-08
42511-42998 Unassigned
jnx-kcsync tcp jollys keychain cloud sync protocol [Patrick_Stein] [Patrick_Stein] 2011-10-24 Defined TXT keys: hash=<40hex characters> salt=<40hex characters> uuid=<40hex characters> Example: hash=5e7580598c0d7064d4fc79faaeb42585e1a675f8 salt=f0164cb3a0c3d7efe75abea8fda86d2d56c8dda9 uuid=db61dc092922252e45bbb264f59147138c7fd5fa

Contact Information

ID Name Contact URI Last Updated
[David_Ferrero] David Ferrero mailto:david&zion.com
[Feitian_Technologies] Feitian Technologies mailto:product&ftsafe.com 2010-09-15
[Hiroyuki_Kawabuchi] Hiroyuki Kawabuchi mailto:buchi&ael.fujitsu.co.jp
[Jon_Press] Jon Press mailto:IANA.Registions&ca.com 2005-09
[Kristoffer_Nilsson] Kristoffer Nilsson mailto:kristoffer.nilsson&hutchison3g.com 2002-02
[Larry_Stone] Larry Stone mailto:lcs&icad.com
[Mayank_Vasa] Mayank Vasa mailto:mayank_vasa&symantec.com 2008-04-03
[Michael_Berg] Michael Berg mailto:mike&dataapples.com 2005-08
[Patrick_Stein] Patrick Stein mailto:Patrick.Stein&jinx.eu 2011-10-24