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
intecourier 495 tcp intecourier [Steve_Favor] [Steve_Favor]
intecourier 495 udp intecourier [Steve_Favor] [Steve_Favor]
cvc 1495 tcp cvc [Bill_Davidson] [Bill_Davidson]
cvc 1495 udp cvc [Bill_Davidson] [Bill_Davidson]
fast-rem-serv 2495 tcp Fast Remote Services [Scott_St_Clair] [Scott_St_Clair]
fast-rem-serv 2495 udp Fast Remote Services [Scott_St_Clair] [Scott_St_Clair]
seclayer-tcp 3495 tcp securitylayer over tcp
seclayer-tcp 3495 udp securitylayer over tcp
sybasesrvmon 4950 tcp Sybase Server Monitor [Chris_Irie] [Chris_Irie] 2008-03-26
sybasesrvmon 4950 udp Sybase Server Monitor [Chris_Irie] [Chris_Irie] 2008-03-26
pwgwims 4951 tcp PWG WIMS [Ira_McDonald] [Ira_McDonald] 2005-12
pwgwims 4951 udp PWG WIMS [Ira_McDonald] [Ira_McDonald] 2005-12
sagxtsds 4952 tcp SAG Directory Server [Michael_Chirila] [Michael_Chirila] 2006-01
sagxtsds 4952 udp SAG Directory Server [Michael_Chirila] [Michael_Chirila] 2006-01
dbsyncarbiter 4953 tcp Synchronization Arbiter [Dave_Neudoerffer_2] [Dave_Neudoerffer_2] 2009-11-18
4953 udp Reserved
4954-4968 Unassigned Known UNAUTHORIZED USE: port 4967

Contact Information

ID Name Contact URI Last Updated
[Bill_Davidson] Bill Davidson mailto:billd&equalizer.cray.com
[Chris_Irie] Chris Irie mailto:irie&sybase.com 2008-03-26
[Dave_Neudoerffer_2] Dave Neudoerffer mailto:dave.neudoerffer&sybase.com 2009-11-18
[Ira_McDonald] Ira McDonald mailto:imcdonald&sharplabs.com 2005-12
[Michael_Chirila] Michael Chirila mailto:Michael.Chirila&softwareag.com 2006-01
[Scott_St_Clair] Scott St. Clair mailto:stclair&ntc.adaptec.com
[Steve_Favor] Steve Favor mailto:sfavor&tigger.intecom.com