Port 389/tcp/udp: LDAP (Lightweight Directory Access Protocol)
Category: Name Resolution & Directory Services. Range: well-known. Status: iana registered.
What runs here
LDAP is the protocol clients use to query and modify a directory service, in a Windows environment, Active Directory's own interface for users, groups, computers, group policy, and schema. Port 389/tcp is its IANA-registered default and is defined by RFC 4511 (part of the RFC 4510 series). It also has a genuine UDP role, connectionless LDAP (CLDAP), which Active Directory domain controllers use to answer lightweight LDAP ping queries from the Windows DC Locator service before a client opens a full TCP LDAP session. Standard LDAP traffic on 389 is unencrypted unless upgraded via STARTTLS.
Why it matters
LDAP is the primary interface adversaries use for Active Directory reconnaissance once they have any foothold: enumerating users, group memberships, computer objects, trust relationships, and permissions is almost always done via LDAP queries, directly or through tools like BloodHound, AdFind, or PowerView, so a spike in LDAP query volume from an unusual source, such as a workstation rather than a management host, is one of the strongest AD-recon signals available. Because it is plaintext by default, an unencrypted LDAP simple bind also exposes the querying account's credentials on the wire.
Where you see it
Legitimately: domain-joined clients and servers querying Active Directory for authentication, group policy, and directory lookups, plus CLDAP LDAP ping traffic from the DC Locator service during logon or domain join. Anomalously/maliciously: bulk or automated directory enumeration from a workstation rather than a management server, plaintext LDAP simple binds exposing credentials, or reconnaissance queries targeting privileged groups and delegation or trust attributes.
What to look for
| Signal | What it means |
|---|---|
| Query volume and source host role | A sudden high volume of LDAP searches from a standard workstation rather than a management or monitoring server is the classic BloodHound/AdFind-style enumeration signal. |
| Search filters targeting privileged attributes | Filters querying admin group membership, servicePrincipalName (Kerberoasting setup), userAccountControl flags, or delegation attributes indicate targeted AD reconnaissance rather than routine lookups. |
Related ports
- 636/tcp: LDAPS (LDAP over TLS/SSL)
- 3268/tcp: Global Catalog LDAP (Microsoft Active Directory)
- 3269/tcp: Global Catalog LDAP over TLS/SSL
- 88/tcp/udp: Kerberos
- 464/tcp/udp: Kerberos Change/Set Password (kpasswd)
- 53/tcp/udp: DNS (Domain Name System)