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
irc-serv 529 tcp IRC-SERV [Brian_Tackett] [Brian_Tackett]
irc-serv 529 udp IRC-SERV [Brian_Tackett] [Brian_Tackett]
xmlrpc-beep 602 tcp XML-RPC over BEEP [RFC3529]
xmlrpc-beep 602 udp XML-RPC over BEEP [RFC3529]
coauthor 1529 tcp oracle
coauthor 1529 udp oracle
utsftp 2529 tcp UTS FTP [David_Moore] [David_Moore]
utsftp 2529 udp UTS FTP [David_Moore] [David_Moore]
jboss-iiop-ssl 3529 tcp JBoss IIOP/SSL [Francisco_Reverbel] [Francisco_Reverbel] 2002-06
jboss-iiop-ssl 3529 udp JBoss IIOP/SSL [Francisco_Reverbel] [Francisco_Reverbel] 2002-06
5283-5297 Unassigned
presence 5298 tcp XMPP Link-Local Messaging [Eric_St_Onge] [Eric_St_Onge] 2008-01-14 Defined TXT keys: See http://www.xmpp.org/registrar/linklocal.html
presence 5298 udp XMPP Link-Local Messaging [Eric_St_Onge] [Eric_St_Onge] 2008-01-14 Defined TXT keys: See http://www.xmpp.org/registrar/linklocal.html
nlg-data 5299 tcp NLG Data Service [Andy_Shellam] [Andy_Shellam] 2008-02-19
nlg-data 5299 udp NLG Data Service [Andy_Shellam] [Andy_Shellam] 2008-02-19

Contact Information

ID Name Contact URI Last Updated
[Andy_Shellam] Andy Shellam mailto:andy&networkmail.eu 2008-02-19
[Brian_Tackett] Brian Tackett mailto:cym&acrux.net
[David_Moore] David Moore mailto:dmoore&uttc-uts.com
[Eric_St_Onge] Eric St. Onge mailto:stonge&apple.com 2008-01-14
[Francisco_Reverbel] Francisco Reverbel mailto:reverbel&ime.usp.br 2002-06