Skip to main content

DACLhound

DACLhound collects and analyzes Active Directory permissions over LDAP or native ADWS. Review DACLs and effective permission paths in an interactive graph, or triage saved data from the command line.

Unlike BloodHound CE's modeled graph edges, DACLhound preserves the collected DACL details and exposes individual Write-Property rights by attribute (for example, WriteLogonHours or WriteUserAccountControl). This helps inspect the specific property and ACE behind a relationship.

DACLhound graph example

https://github.com/user-attachments/assets/d691098f-426c-4c34-ae8d-40e148de3154

Install

Python 3.10 or newer is required.

pipx install DACLhound

Upgrade with pipx upgrade DACLhound.

Collect

daclhound collect --host DC01.lab.local -d lab.local -u 'user' -p 'password' --dc-ip 192.168.2.1

By default, collection tries LDAP and falls back to ADWS if LDAP is unavailable. Choose --transport ldap or --transport adws to select one explicitly. ADWS uses TCP port 9389; --secure applies to LDAP only. Use the domain controller FQDN for Kerberos authentication.

The collector is read-only. It collects users, groups, computers, OUs, containers, GPOs, the domain, trusts, sites, Foreign Security Principals, and ADCS data. Limit directory object types with --types, or skip ADCS with --no-adcs:

daclhound collect --host DC01.lab.local -d lab.local -u 'user' -p 'password' --types users,groups --no-adcs

Output is saved as lab.local.json in the current directory; if that name exists, a numbered filename is chosen. Set a path with --output, replace an existing file with --overwrite, or retain raw collector entries with --raw-output.

Optional host checks

Add --host-checks to check SMB signing policy and whether the WebClient service's DAV RPC Service pipe is available over SMB on collected computers. The checks require authentication to each computer; they do not perform HTTP/WebDAV requests. Use --host-check-timeout to set the per-host timeout and --dns-server to select a DNS resolver.

daclhound collect --host DC01.lab.local -d lab.local -u 'user' -p 'password' --host-checks --host-check-timeout 5

Analyze

Get a prioritized terminal overview of permissions, membership, Kerberos exposure, delegation, ADCS, trusts, and GPO links:

daclhound analyze lab.local.json
daclhound analyze lab.local.json other-domain.json --from-user 'alice@lab.local'

Multiple input files are combined, with duplicate objects and relationships merged. Use --color never to disable colored output.

Open the graph

Run the viewer in the foreground and stop it with Ctrl+C:

daclhound graph --input lab.local.json

Or manage the viewer as a background service:

  • Start the viewer without preloading a graph: daclhound graph start.
  • Start the viewer and load a graph immediately: daclhound graph start --input lab.local.json.
  • Check whether the background viewer is running: daclhound graph status.
  • Stop the background viewer: daclhound graph stop.

The server listens on 127.0.0.1:8765 by default. Uploaded JSON files stay in memory while the server is running and are discarded when it stops. Use --bind and --port to change the listener. Run daclhound collect --help or daclhound graph --help for all options.

Authentication

NTLM password

daclhound collect --host DC01.lab.local -d lab.local -u 'user' -p 'password' --dc-ip 192.168.2.1

NTLM pass-the-hash

Pass the NT hash directly, or use LMHASH:NTHASH when you have both hashes:

daclhound collect --host DC01.lab.local -d lab.local -u 'user' -hashes '613a519b5b0ef57c07bc6395aa1aff14' --dc-ip 192.168.2.1

Kerberos

Kerberos supports a password, pass-the-hash, or an existing ccache. When using a ccache, -u is optional; the identity is taken from the ticket. -no-pass is an explicit flag for ccache authentication.

Password:

daclhound collect --host DC01.lab.local -d lab.local -u 'user' -p 'password' -k --dc-ip 192.168.2.1

Pass-the-hash (NT hash used as the Kerberos RC4 key):

daclhound collect --host DC01.lab.local -d lab.local -u 'user' -hashes '613a519b5b0ef57c07bc6395aa1aff14' -k --dc-ip 192.168.2.1

If both hashes are available, use -hashes '<LMHASH>:<NTHASH>'.

Existing ccache:

# Use the current KRB5CCNAME
daclhound collect --host DC01.lab.local -d lab.local -k -no-pass --dc-ip 192.168.2.1

# Or provide a ccache file directly
daclhound collect --host DC01.lab.local -d lab.local -k user.ccache -no-pass --dc-ip 192.168.2.1

An AES key enables Kerberos automatically: use -aesKey '<AESKEY>' (with -u). Add -s to use LDAPS.

License

MIT. See LICENSE.

Metadata

Release files for DACLhound 0.1.31

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for DACLhound 0.1.31
File Size Uploaded Provenance Actions
daclhound-0.1.31.tar.gz 171.4 kB Without provenance Details for daclhound-0.1.31.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for DACLhound 0.1.31
File Interpreter ABI Platform Actions
daclhound-0.1.31-py3-none-any.whl Python 3 none any Details for daclhound-0.1.31-py3-none-any.whl

Total release size: 354.3 kB

Release files / daclhound-0.1.31.tar.gz

Download URL daclhound-0.1.31.tar.gz
Size 171.4 kB
Tags Source
SHA-256 checksum
How to use checksums
2c28acbf7f1d57aba5520bb310786cef761fd5d648563e96b17fda0dddd8bcc2
BLAKE2b-256 checksum
How to use checksums
56a60289901c90c7f77aed7b69d647c788d0389a8edbddb9517a8f321e7a975b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.13

Release files / daclhound-0.1.31-py3-none-any.whl

Download URL daclhound-0.1.31-py3-none-any.whl
Size 182.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
0021d1a5849ed30adbeac4b3c3dbc53a4d90790eda1abda7f6a98c7108276aa8
BLAKE2b-256 checksum
How to use checksums
35d5b8bb82ef1d7d13fc7381a63b316b544ae830c7858eeb82c94c839d35febe
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.13

Security for DACLhound 0.1.31

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.31 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page