Subdomain Takeover Checker
v1.0.0Check subdomains for potential takeover vulnerabilities. Detects dangling DNS records pointing to unclaimed services (GitHub Pages, Heroku, AWS, etc.)
⭐ 0· 127·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (subdomain takeover checking) align with the provided script: it uses dig to resolve records and (optionally) curl to verify HTTP responses. The tool requires only standard CLI utilities to perform DNS and HTTP checks, which is proportional to the stated purpose.
Instruction Scope
SKILL.md instructs the agent to run the included bash script against a list or single subdomain and documents options (passive, json, timeout, output). The script performs DNS resolution and optional HTTP requests only against the user-supplied domains. It does not read unrelated files, environment variables, or exfiltrate results to external endpoints. Note: the script uses curl for HTTP checks but curl is not declared in the skill metadata as a required binary.
Install Mechanism
There is no install spec and the skill ships as a small local bash script plus SKILL.md. No network downloads or archive extraction are performed during installation, which is low risk.
Credentials
The skill requests no environment variables, no credentials, and no config paths. The script does not read secrets or external configs. This is proportionate to the tool's purpose.
Persistence & Privilege
The skill is not set to always:true and does not attempt to modify other skills or system-wide settings. It runs on-demand and exits with an appropriate code indicating findings.
Assessment
This skill is coherent with its stated purpose, but check these before installing: (1) The script uses curl for HTTP verification but curl is not declared in the metadata—ensure curl is available on the host. (2) The tool performs network scans of domains you supply; avoid scanning domains you don't have permission to test (legal/ethical risk). (3) Expect false positives because the script uses simple substring matching of CNAMEs and treats HTTP timeouts/404s as potentially claimable. (4) If you will run this in an automated agent, run it in an environment with controlled network access and review output files before sharing. If you need stronger verification, consider enhancing the script to use provider-specific claim checks or safer heuristics.Like a lobster shell, security has layers — review code before you run it.
latestvk97926kv6d73ha0w66pnaxhv7983tdmb
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🏴 Clawdis
Binsbash, dig