Service Name and Transport Protocol Port Number Registry

Last Updated

  • 2026-10-22

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

  • RFC 6335: Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry

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 basis, as described in RFC 6335.

Port numbers are divided into three ranges, with their uses and assignment procedures specified in Section 8.1.2 of RFC 6335:

The registration procedures for service names and port numbers are specified in RFC 6335, while the registration policies referenced above are defined in RFC 8126.

Assigned ports both System and User ports SHOULD NOT be used without or prior to IANA registration.

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.

Registration Forms

Available Formats

Service Name Port Number Transport Protocol Description Assignee Contact Registration Date Modification Date Reference Service Code Unauthorized Use Reported Assignment Notes
scc-security 582 tcp SCC Security Prashant Dholakia Prashant Dholakia
scc-security 582 udp SCC Security Prashant Dholakia Prashant Dholakia
msims 1582 tcp MSIMS Glenn Olander Glenn Olander
msims 1582 udp MSIMS Glenn Olander Glenn Olander
argis-ds 2582 tcp ARGIS DS John Legh-Page John Legh-Page
argis-ds 2582 udp ARGIS DS John Legh-Page John Legh-Page
press 3582 tcp PEG PRESS Server Jim DeLisle Jim DeLisle 2002-08
press 3582 udp PEG PRESS Server Jim DeLisle Jim DeLisle 2002-08
fac-restore 5582 tcp T-Mobile SMS Protocol Message 3 Jessica Yan Jessica Yan 2008-02-19
fac-restore 5582 udp T-Mobile SMS Protocol Message 3 Jessica Yan Jessica Yan 2008-02-19
autopassdaemon 5820 tcp AutoPass licensing opentext AutoPass 2022-06-10 2024-08-01
5820 udp Reserved
5821-5840 Unassigned
parsec-game 6582 tcp Parsec Gameserver Andreas Varga Andreas Varga
parsec-game 6582 udp Parsec Gameserver Andreas Varga Andreas Varga
45679-45823 Unassigned
dai-shell 45824 tcp Server for the DAI family of client-server products Data Access, Inc. Adam Robinson 2012-04-30
45824 udp Reserved
qdb2service 45825 tcp Qpuncture Data Access Service Michael Yun Michael Yun 2007-10-24
qdb2service 45825 udp Qpuncture Data Access Service Michael Yun Michael Yun 2007-10-24
45826-45965 Unassigned

Contact Information

Name Organization Contact URI Last Updated
Adam Robinson Data Access, Inc. adam&dataaccessinc.com 2012-04-30
Andreas Varga sid&parsec.org
AutoPass MFI-swpdl.apls_core&opentext.com 2024-08-01
Data Access, Inc. development&dataaccessinc.com 2012-04-30
Glenn Olander gjo&msi.com
Jessica Yan jessica.yan2&t-mobile.com 2008-02-19
Jim DeLisle jdelisle&swellsoftware.com 2002-08
John Legh-Page john.legh-page&argis.com
Michael Yun cinnanda&gmail.com 2007-10-24
opentext MFI-swpdl.apls_core&opentext.com 2024-08-01
Prashant Dholakia prashant&semaphorecom.com