Service Name and Transport Protocol Port Number Registry

Last Updated
2026-09-11
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
discard 9 dccp Discard [Eddie_Kohler] [Eddie_Kohler] [RFC4340] 1145656131
spmp 656 tcp SPMP [Jakob_Kaivo] [Jakob_Kaivo]
spmp 656 udp SPMP [Jakob_Kaivo] [Jakob_Kaivo]
owamp-control 861 tcp OWAMP-Control [IESG] [IETF_Chair] [RFC4656]
dec-mbadmin-h 1656 tcp dec-mbadmin-h [Nick_Shipman] [Nick_Shipman]
dec-mbadmin-h 1656 udp dec-mbadmin-h [Nick_Shipman] [Nick_Shipman]
kana 2656 tcp Kana [Colin_Goldstein] [Colin_Goldstein]
kana 2656 udp Kana [Colin_Goldstein] [Colin_Goldstein]
turn 3478 tcp TURN over TCP 2019-08-02 [RFC8656]
turn 3478 udp TURN over UDP 2019-08-02 [RFC8656]
abatjss 3656 tcp ActiveBatch Job Scheduler [Ben_Rosenberg] [Ben_Rosenberg] 2003-01
abatjss 3656 udp ActiveBatch Job Scheduler [Ben_Rosenberg] [Ben_Rosenberg] 2003-01
mupdate 3905 tcp Mailbox Update (MUPDATE) protocol [RFC3656]
mupdate 3905 udp Mailbox Update (MUPDATE) protocol [RFC3656]
turns 5349 tcp TURN over TLS 2019-08-02 [RFC8656]
turns 5349 udp TURN over DTLS [IESG] [IETF_Chair] 2019-08-02 [RFC7350] This service name was initially created by [RFC8656].
6559-6565 Unassigned
sane-port 6566 tcp SANE Control Port [Henning_Meier_Geinit] [Henning_Meier_Geinit] 2002-10
sane-port 6566 udp SANE Control Port [Henning_Meier_Geinit] [Henning_Meier_Geinit] 2002-10
6567 Reserved 2007-01 2011-08-26 This entry has been removed on 2011-08-26.
canit-store 6568 tcp CanIt Storage Manager

IANA assigned this well-formed service name as a replacement for "canit_store".
[Dianne_Skoll] [Dianne_Skoll] 2009-04-22 2017-05-25
canit_store 6568 tcp CanIt Storage Manager [Dianne_Skoll] [Dianne_Skoll] 2009-04-22 2017-05-25 This entry is an alias to "canit-store". This entry is now historic, not usable for use with many common service discovery mechanisms.
rp-reputation 6568 udp Roaring Penguin IP Address Reputation Collection [Dianne_Skoll] [Dianne_Skoll] 2010-02-05 2017-05-25
6569-6578 Unassigned
emgmsg 6656 tcp Emergency Message Control Service [Gerry_Gorman] [Gerry_Gorman] 2010-12-06
6656 udp Reserved
snip-slave 33656 tcp SNIP Slave [Dr_Chris_Tucker] [Dr_Chris_Tucker] 2005-08
snip-slave 33656 udp SNIP Slave [Dr_Chris_Tucker] [Dr_Chris_Tucker] 2005-08

Contact Information

ID Name Organization Contact URI Last Updated
[Ben_Rosenberg] Ben Rosenberg mailto:brosenberg&advsyscon.com 2003-01
[Colin_Goldstein] Colin Goldstein mailto:Colin&kana.com
[Dianne_Skoll] Dianne Skoll mailto:dfs&roaringpenguin.com 2017-05-25
[Dr_Chris_Tucker] Dr. Chris Tucker mailto:chris.tucker&ioltd.co.uk 2005-08
[Eddie_Kohler] Eddie Kohler IETF dccp WG mailto:kohler&cs.ucla.edu
[Gerry_Gorman] Gerry Gorman mailto:gerry.gorman&emclock.com 2010-12-06
[Henning_Meier_Geinit] Henning Meier-Geinitz mailto:henning&meier-geinitz.de 2002-10
[IESG] IESG mailto:iesg&ietf.org
[IETF_Chair] IETF Chair IETF mailto:chair&ietf.org
[Jakob_Kaivo] Jakob Kaivo mailto:jkaivo&nodomainname.net
[Nick_Shipman] Nick Shipman mailto:Nick.Shipman&mrmog.reo.dec.com