Service Name and Transport Protocol Port Number Registry

Last Updated
2026-09-04
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
iims 4800 tcp Icona Instant Messenging System
iims 4800 udp Icona Instant Messenging System
nimcontroller 48000 tcp Nimbus Controller [Carstein_Seeberg_2] [Carstein_Seeberg_2]
nimcontroller 48000 udp Nimbus Controller [Carstein_Seeberg_2] [Carstein_Seeberg_2]
nimspooler 48001 tcp Nimbus Spooler [Carstein_Seeberg_2] [Carstein_Seeberg_2]
nimspooler 48001 udp Nimbus Spooler [Carstein_Seeberg_2] [Carstein_Seeberg_2]
nimhub 48002 tcp Nimbus Hub [Carstein_Seeberg_2] [Carstein_Seeberg_2]
nimhub 48002 udp Nimbus Hub [Carstein_Seeberg_2] [Carstein_Seeberg_2]
nimgtw 48003 tcp Nimbus Gateway [Carstein_Seeberg_2] [Carstein_Seeberg_2]
nimgtw 48003 udp Nimbus Gateway [Carstein_Seeberg_2] [Carstein_Seeberg_2]
nimbusdb 48004 tcp NimbusDB Connector [Stephen_Harrison] [Stephen_Harrison] 2011-01-24
48004 udp Reserved
nimbusdbctrl 48005 tcp NimbusDB Control [Stephen_Harrison] [Stephen_Harrison] 2011-01-24
48005 udp Reserved
48006-48047 Unassigned

Contact Information

ID Name Contact URI Last Updated
[Carstein_Seeberg_2] Carstein Seeberg mailto:case&nimsoft.no
[Stephen_Harrison] Stephen Harrison mailto:sharrison&nimbusdb.com 2011-01-24