Internet Assigned Numbers Authority

Service Name and Transport Protocol Port Number Registry

Last Updated
2025-01-23
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
kerberos 88 tcp Kerberos [B_Clifford_Neuman] [B_Clifford_Neuman] 2022-02-18 [RFC4120]
kerberos 88 udp Kerberos [B_Clifford_Neuman] [B_Clifford_Neuman] 2022-02-18 [RFC4120]
kerberos-adm 749 tcp kerberos administration
kerberos-adm 749 udp kerberos administration
kerberos-iv 750 udp kerberos version iv [Martin_Hamilton] [Martin_Hamilton]
kftp-data 6620 tcp Kerberos V5 FTP Data [Robert_J_Scott] [Robert_J_Scott] 2005-08
kftp-data 6620 udp Kerberos V5 FTP Data [Robert_J_Scott] [Robert_J_Scott] 2005-08
kftp 6621 tcp Kerberos V5 FTP Control [Robert_J_Scott] [Robert_J_Scott] 2005-08
kftp 6621 udp Kerberos V5 FTP Control [Robert_J_Scott] [Robert_J_Scott] 2005-08
ktelnet 6623 tcp Kerberos V5 Telnet [Robert_J_Scott] [Robert_J_Scott] 2005-08
ktelnet 6623 udp Kerberos V5 Telnet [Robert_J_Scott] [Robert_J_Scott] 2005-08
afs3-kaserver 7004 tcp AFS/Kerberos authentication service
afs3-kaserver 7004 udp AFS/Kerberos authentication service

Contact Information

ID Name Contact URI Last Updated
[B_Clifford_Neuman] B. Clifford Neuman mailto:bcn&isi.edu 2022-02-18
[Martin_Hamilton] Martin Hamilton mailto:martin&mrrl.lut.as.uk
[Robert_J_Scott] Robert J. Scott mailto:rob&hpcmo.hpc.mil 2005-08