| name | staging-subdomain-hunt |
| description | Hunt staging via crt.sh when production is WAF-hardened. |
| version | 1.1.0 |
| revision_date | "2026-07-25T00:00:00.000Z" |
| license | MIT |
| platforms | ["linux"] |
| compatibility | Requires curl, nmap, python3, masscan, subfinder, httpx, nuclei |
| tags | ["recon","subdomain","staging","takeover","wordpress"] |
| category | recon |
| related_skills | ["wp-mass-recon","deep-invade","subdomain-enumeration","wordpress-plugin-hunt","js-secrets-extraction","source-leak-hunt","phpinfo-to-rce"] |
Staging & Subdomain Hunt Skill
Discover staging, development, and internal subdomains through certificate transparency (crt.sh), DNS brute force, and web probing. Exploit the staging security gap — staging environments consistently have weaker security than production (no WAF, debug enabled, install pages accessible). Proven on 7 US targets where staging subdomains exposed phpinfo, WordPress install pages, and internal APIs not visible on production.
When to Use
- Running
deep-invade Phase 5 on a high-value target.
- Production target is well-secured (WAF, no leaks) — pivot to staging.
- Target has a large attack surface (e-commerce, SaaS, franchise model).
- You need additional entry points when the main site is hardened.
- After
subdomain-enumeration produces a list of subdomains.
Prerequisites
terminal with curl, httpx, jq.
- Target domain (e.g.,
example.com).
- For DNS brute force: wordlist at
./tools/subdomains.txt.
How to Run
DOMAIN="example.com"
curl --max-time 30 --connect-timeout 10 -sk "https://crt.sh/?q=%25.$DOMAIN&output=json" | jq -r '.[].name_value' | sed 's/\*\.//g' | sort -u > subs.txt
httpx -silent -l subs.txt -threads 50 -status-code -tech-detect -o alive_subs.txt
grep -iE 'staging|stage|dev|test|uat|beta' alive_subs.txt
Quick Reference
| Indicator | What It Means | Action |
|---|
/wp-admin/install.php returns 200 | Fresh WordPress — no site configured | Install takeover |
/wp-admin/upgrade.php returns 200 | WP needs DB upgrade | DB info disclosure |
info.php / phpinfo.php on staging | Debug enabled | PHPInfo analysis (see phpinfo-to-rce) |
|