Internet Assigned Numbers Authority

Service Name and Transport Protocol Port Number Registry

Last Updated
2022-10-03
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
krb524 4444 tcp KRB524 [B_Clifford_Neuman] [B_Clifford_Neuman] krb524 assigned the port, nv used it without an assignment
krb524 4444 udp KRB524 [B_Clifford_Neuman] [B_Clifford_Neuman] krb524 assigned the port, nv used it without an assignment
nv-video 4444 tcp NV Video default [Ron_Frederick] [Ron_Frederick] krb524 assigned the port, nv used it without an assignment
nv-video 4444 udp NV Video default [Ron_Frederick] [Ron_Frederick] krb524 assigned the port, nv used it without an assignment
44324-44443 Unassigned
cognex-dataman 44444 tcp Cognex DataMan Management Protocol [Cognex] [Mario_Joussen] 2012-08-28
44444 udp Reserved
acronis-backup 44445 tcp Acronis Backup Gateway service port [Acronis] [Kevin_Reed] 2019-11-25
44445 udp Reserved
44446-44543 Unassigned Known UNAUTHORIZED USE: Ports 44515 & 44516

Contact Information

ID Name Organization Contact URI Last Updated
[Acronis] Acronis mailto:kr&acronis.com 2019-11-25
[B_Clifford_Neuman] B. Clifford Neuman mailto:bcn&isi.edu 2022-02-18
[Cognex] Cognex Corporation mailto:contactus&cognex.com 2012-08-28
[Kevin_Reed] Kevin Reed mailto:kr&acronis.com 2019-11-25
[Mario_Joussen] Mario Joussen Cognex Corporation mailto:mario.joussen&cognex.com 2012-08-28
[Ron_Frederick] Ron Frederick mailto:frederick&parc.xerox.com