Service Name and Transport Protocol Port Number Registry

Last Updated

  • 2026-11-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

  • 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
ldap 389 tcp Lightweight Directory Access Protocol Tim Howes Tim Howes
ldap 389 udp Lightweight Directory Access Protocol Tim Howes Tim Howes
ldaps 636 tcp ldap protocol over TLS/SSL (was sldap) Pat Richard Pat Richard
ldaps 636 udp ldap protocol over TLS/SSL (was sldap) Pat Richard Pat Richard
www-ldap-gw 1760 tcp www-ldap-gw Nick Emery Nick Emery
www-ldap-gw 1760 udp www-ldap-gw Nick Emery Nick Emery
msft-gc-ssl 3269 tcp Microsoft Global Catalog with LDAP/SSL Asaf Kashi Asaf Kashi
msft-gc-ssl 3269 udp Microsoft Global Catalog with LDAP/SSL Asaf Kashi Asaf Kashi
ldap-admin 3407 tcp LDAP admin server port Stephen Tsun Stephen Tsun 2002-02
ldap-admin 3407 udp LDAP admin server port Stephen Tsun Stephen Tsun 2002-02
bmc-ctd-ldap 6301 tcp BMC CONTROL-D LDAP SERVER

IANA assigned this well-formed service name as a replacement for "bmc_ctd_ldap".
Portnoy Boxman Portnoy Boxman 2006-09
bmc_ctd_ldap 6301 tcp BMC CONTROL-D LDAP SERVER Portnoy Boxman Portnoy Boxman 2006-09 This entry is an alias to "bmc-ctd-ldap". This entry is now historic, not usable for use with many common service discovery mechanisms.
bmc-ctd-ldap 6301 udp BMC CONTROL-D LDAP SERVER

IANA assigned this well-formed service name as a replacement for "bmc_ctd_ldap".
Portnoy Boxman Portnoy Boxman 2006-09
bmc_ctd_ldap 6301 udp BMC CONTROL-D LDAP SERVER Portnoy Boxman Portnoy Boxman 2006-09 This entry is an alias to "bmc-ctd-ldap". This entry is now historic, not usable for use with many common service discovery mechanisms.
pgpkey-ldap PGP Keyserver using LDAP Jeroen Massar Jeroen Massar Defined TXT keys: None

Contact Information

Name Contact URI Last Updated
Asaf Kashi asafk&microsoft.com
Jeroen Massar jeroen&unfix.org
Nick Emery Nick.Emery&altavista.digital.com
Pat Richard patr&xcert.com
Portnoy Boxman Portnoy_Boxman&bmc.com 2006-09
Stephen Tsun stsun&calient.net 2002-02
Tim Howes Tim.Howes&terminator.cc.umich.edu