Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
aeondave/ldaprelayscanActive Directory and Windows

ldaprelayscan

⁨Assess effective LDAP signing and LDAPS channel-binding enforcement with LdapRelayScan; interpret per-controller results and inconclusive tests.⁩

v2026.11.13-21cd5683 installs+3 in 7 days39 StarsMITsynced 11 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install aeondave/ldaprelayscan

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
VnYJBWvhuF…Q/MEJgAQ==The CLI checks the SHA-256 and the signature before it writes a file.
Package9306789a…cdc88554
9306789aa65b…e1d2cdc885541 file · ⁦1.3 KB⁩
ScanLow1 finding
  • Links to outside domains
See the full scan
Sourcegithub.com/AeonDave/malskill/tree/main/offensive-tools/windows/ldaprelayscan@21cd568

Test directory-service authentication protections. A policy finding is evidence about that endpoint, not proof that an attack chain will succeed.

Setup and checks

Use the upstream repository and its dependency set; do not assume a PyPI package or executable named ldaprelayscan.

bash
git clone https://github.com/zyn3rgy/LdapRelayScan.git
cd LdapRelayScan
python3.11 -m venv .venv
. .venv/bin/activate
python3 -m pip install -r requirements_exact.txt
python3 LdapRelayScan.py -h

# DNS/discovery seed; tests the domain controllers discovered through it
python3 LdapRelayScan.py -method LDAPS -dc-ip 192.0.2.10

# LDAP signing plus LDAPS channel binding; prompts for credentials
python3 LdapRelayScan.py -method BOTH -dc-ip 192.0.2.10 -u audit-user
  • Methods are LDAPS (unauthenticated channel-binding checks) and BOTH (signing and channel binding with credentials); there is no SMB method.
  • -dc-ip seeds DNS and LDAP discovery. The script enumerates DC SRV records and tests discovered controllers; it is not a single-controller target selector.
  • Check DNS resolution and connectivity first. Capture actual discovered/tested controller names, addresses, timestamps, method, tool revision, and raw results.
  • Compare tested controllers with an independent inventory. A discovery failure or an omitted DC leaves a coverage gap; changing the discovery seed does not guarantee a bounded target set.
  • Bind failures, TLS errors, unreachable endpoints, and invalid credentials are inconclusive, not evidence of enforcement.
  • Preserve the distinction between channel binding being absent, conditional, and required. Do not collapse these into a single pass/fail.
  • Tests perform connection and authentication attempts and may produce logs. The tool does not verify SMB signing, HTTP protections, account privileges, or downstream exploitability.

Return a per-controller finding with observed enforcement, failed tests, and the smallest remaining validation step. Recheck after policy changes.

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.11.13-21cd568Nov 13, 202621cd5689306789aSigned–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login