python-ldapdomaindump
open-sourceThe section your link pointed to isn't on python-ldapdomaindump's page any more, so we've brought you to the top.
Dumps Active DirectoryActive DirectoryMicrosoft's directory service for Windows networks that centralises authentication and authorisation; cyber tools target or integrate with it because it controls identity and access across most enterprise environments. users, groups, computers, and policies via LDAP and outputs results in HTML, JSON, and greppable formats.
Summary
python-ldapdomaindump is an open-source command-line tool that connects to Active Directory over LDAP and dumps users, groups, computers, domain policy, and trust relationships into HTML, JSON, and greppable output formats. It authenticates with a username and password or an NTLMNTLMA Windows authentication protocol that proves knowledge of a password through a challenge and response. Captured authentication exchanges can be abused in relay attacks when protections are absent. hash, or it can piggyback on an existing LDAP session, which lets it plug into relaying tools like Impacket's ntlmrelayx, and it can convert its output into BloodHound-compatible CSVs. It is built for penetration testers doing internal network recon rather than for ongoing AD monitoring. It sits alongside other LDAP-based domain enumeration recon tools used in this phase of an engagement, without the project naming a specific peer. Started in 2016 with 14 contributors, it has had no commits in the past year and its last release was 504 days ago.
Dumps Active Directory users, groups, computers, and policies via LDAP and outputs results in HTML, JSON, and greppable formats.
How python-ldapdomaindump helps
Which computers are joined to this domain and what are they running?
pulls all computer accounts from LDAP and sorts them by operating system into a dedicated grouped file, so aging or unexpected systems stand out
What password and lockout rules actually apply to this domain?
reads the domain policy over LDAP and writes it out as a readable file covering requirements like password complexity and account lockout thresholds
What trust relationships could let an attacker pivot out of this domain?
enumerates incoming and outgoing domain trusts along with their properties into a dedicated output file
Can I turn a credential I only have relayed access to into a full picture of the domain?
accepts an existing authenticated LDAP session, including one handed off by a relaying tool, so the dump can proceed without ever needing a plaintext password
Can I feed what I find here straight into graph-based attack path analysis?
converts its own JSON output into CSV files formatted for BloodHound, so the same enumeration data can be explored for privilege escalation paths
Languages
Command line
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for python-ldapdomaindump, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail python-ldapdomaindump puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
Nothing shipped since we started watching. Releases and docs updates land here as they happen.
Project health
Issue, contributor and maintainer activity in dirkjanm/ldapdomaindump, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 0 −2 vs prior 12 months
- Maintainers 0 +0 joined · −0 left, last 12 months
- Bus factor 0 committers behind half the commits
- Community-filed 100% of issues opened, last 12 months
- Median time to close 12 days first maintainer reply 12 days
- Open backlog 13 of 52 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 13
- Contributors / month 0
- Commits / month 0
- Stars 1,429
- other 100%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.