This lesson teaches bug bounty hunters how to systematically discover and prioritize all subdomains of a target—a critical recon phase that precedes any vulnerability testing. The article argues that most hunters test only the main domain where bugs are rare and heavily monitored, while unpatched dev, staging, and internal subdomains with weak security are consistently where high-value vulnerabilities live. The lesson provides a complete passive and active recon pipeline using crt.sh, Subfinder, Amass, httpx, and ffuf, then connects findings directly to the Burp Suite testing workflow from an earlier lesson.
- Why subdomains yield more bugs than main domainThe main domain is constantly audited and monitored by security teams and automated scanners, making original vulnerabilities rare. In contrast, subdomains like dev.target.com, staging.target.com, and internal.target.com often run outdated unpatched software, have weak or no authentication, have debug mode enabled, or have been abandoned and forgotten—exposing them to CVE exploitation and configuration bypass attacks that other hunters miss because they never look beyond the homepage.
- Certificate transparency logs reveal historical subdomainscrt.sh indexes public SSL/TLS certificate logs that record every subdomain ever deployed with HTTPS. The article emphasizes running this first because it returns completely passive results with zero target contact and no rate limits. Critically, certificate logs preserve subdomains from years ago—including decommissioned assets that still respond to HTTP but receive zero monitoring, making forgotten subdomains with outdated software a reliable source of high-value findings.
- Multi-source passive aggregation with SubfinderSubfinder queries over 40 passive sources simultaneously—certificate transparency, DNS databases, Shodan, VirusTotal, and search engine indices—returning a deduplicated list of subdomains. The article recommends running it after crt.sh and merging results with cat and sort -u to combine findings; the -v flag shows which source found each subdomain, helping hunters understand tool contribution.
- Amass passive mode expands recon scope systematicallyAmass enum -passive queries passive sources safely, and amass intel -org 'Company Name' reveals related domains owned by the same organization—expanding scope discovery to include ASN ranges and subsidiary domains. The article cautions that active DNS brute-forcing (amass enum -active -brute) must only be used when the programme explicitly permits automated scanning, as it generates target traffic and leaves server logs.
- httpx filters noise to testable priority targets instantlyAfter enumeration, hundreds of raw subdomains are mostly dead or parked. httpx probes each subdomain over HTTP and HTTPS, recording which respond with HTTP status codes (200, 301, 302, 403), page title, and technology stack. The article demonstrates filtering 347 raw subdomains to 7 live hosts, with each live host's tech stack immediately revealing attack priorities—e.g., Apache 2.2 EOL, PHP 7.1 EOL, unauthenticated Django 2.1 dashboard.
- Directory fuzzing discovers hidden endpoints on priority targetsffuf systematically requests common path names (/admin/, /debug/, /api/) against live priority subdomains, filtering by status code and response size to avoid false positives from custom 404 pages. The article demonstrates finding /admin/ [200], /debug/ [200], and /phpinfo.php [200] on dev subdomains, with phpinfo.php exposing PHP version, server config, and environment variables in plaintext—a critical finding that leads directly to credential exposure.
- Scope policy compliance prevents bans and closed reportsThe article emphasizes reading the programme scope on HackerOne or Bugcrowd before running any tool, noting that passive tools like crt.sh and Subfinder passive mode are safe on any in-scope target, but active DNS brute-forcing may be explicitly restricted. Testing out-of-scope targets gets reports closed and may ban the hunter from the programme—three critical questions are: Is active scanning permitted? Are subsidiary domains in scope? What is the responsible disclosure policy?
- Prioritization framework feeds directly into Burp Suite workflowThe lesson organizes findings into P1NOW (EOL software + unauthenticated panels), P2TODAY (403 bypasses, phpinfo.php, backup files like .env and .sql), and P3LATER (main domain, authenticated areas). Each priority target is opened in a Burp-proxied browser to populate HTTP History before testing; P2 includes testing X-Original-URL and X-Forwarded-For headers to bypass 403 Forbidden responses, directly using Burp Repeater techniques from Day 5.
Bottom line: Subdomain enumeration using a passive pipeline (crt.sh → Subfinder → Amass passive → httpx filtering) combined with directory fuzzing (ffuf) reveals forgotten dev, staging, and internal subdomains running unpatched EOL software and lacking authentication—where most hunters never look—then feeds those priority targets into Burp Suite for systematic vulnerability testing. Hunters who map all discoverable subdomains before touching Burp Suite consistently find high-value bugs that other hunters wal
Day 6 / 60 — 10%
✅ D2:Burp Setup
✅ D3:HTTP
✅ D4:OWASP Top 10
✅ D5:Burp Deep Dive
▶ D6:Subdomain Enum
D7:XSS Hunting
D8–60:···
Why Subdomains Are Where Bugs Actually Live
The main domain is the most tested, most monitored, and most hardened part of any programme. Security teams audit it constantly. Automated scanners run on it around the clock. Finding an original, unreported vulnerability there requires deep expertise and patience. Subdomains are a completely different story.
A programme with *.target.com in scope can have 300+ valid subdomains. Most hunters test fewer than 10. The hunter who maps all 300, filters to live hosts, and investigates the unusual ones consistently finds bugs others walk straight past.
uat. · internal. · admin.
api-v2. · beta. · legacy.
corp. · old. · backup.
Debug mode enabled in production
Weak or no authentication
Default credentials not changed
Internal APIs publicly exposed
Forgotten after project ends
No automated scanner coverage
Step 0 — Read Programme Scope Before Running Anything
*.target.com) covers all subdomains. Many programmes explicitly exclude specific assets. Testing out-of-scope gets your report closed and may get you banned from the programme.✅ IN SCOPE: api.target.com # specific subdomain
❌ OUT OF SCOPE: careers.target.com # third-party ATS
❌ OUT OF SCOPE: blog.target.com # hosted on external platform
# Three questions to answer before starting:
Is active DNS brute-forcing / automated scanning permitted?
Are acquired / subsidiary domains in scope?
What is the safe harbour / responsible disclosure policy?
Passive Discovery — crt.sh Certificate Transparency
Certificate transparency logs are public records of every SSL/TLS certificate ever issued for a domain. Every new subdomain deployed with HTTPS gets a certificate logged permanently in these public logs. crt.sh indexes them — completely passive, no rate limits, zero traffic to the target. Run this first on every programme target.
curl -s “https://crt.sh/?q=%.target.com&output=json” \
| jq -r ‘.[].name_value’ \
| sort -u \
| grep -v ‘^\*’ > crt.txt # strip wildcard entries
wc -l crt.txt # count unique subdomains found
# ─── Browser alternative ────────────────────────────────────────
# Visit: https://crt.sh/?q=%.target.com
# Look for dev., staging., internal., admin. patterns immediately
Subfinder — 40+ Passive Sources in One Command
Subfinder by ProjectDiscovery queries over 40 passive sources simultaneously — certificate transparency, DNS databases, Shodan, VirusTotal, search engine indices, and more — returning a clean deduplicated list. The industry-standard passive subdomain enumeration tool for bug bounty hunters. Available from Kali’s package repositories (one install command, shown below).
subfinder -version
sudo apt install subfinder -y # if not installed
# ─── Basic subdomain discovery ──────────────────────────────────
subfinder -d target.com -silent -o subfinder.txt
# ─── Verbose — see which source found each subdomain ────────────
subfinder -d target.com -v # great for learning what each source contributes
# ─── Merge with crt.sh results ──────────────────────────────────
cat crt.txt subfinder.txt | sort -u > combined.txt
Amass — Deep Passive Recon & Org-Wide Intelligence
amass enum -passive -d target.com -o amass.txt
# ─── Amass intel — find related domains owned by same org ───────
amass intel -org “Target Company Name”
# Reveals ASN, IP ranges, and related domains = expanded scope
# ─── Active DNS brute-force (scope-permitted only!) ─────────────
amass enum -active -brute -d target.com \
-w /usr/share/seclists/Discovery/DNS/subdomains-top1million-5000.txt
# ⚠️ Only use -active when programme explicitly permits automated scanning
sudo apt update && sudo apt install -y subfinder amass httpx-toolkit ffuf seclists jq. On Kali the httpx package is called httpx-toolkit and so is the command, because the name httpx belongs to a different Python tool. Wherever this lesson says httpx, type httpx-toolkit on Kali. Amass changes its options between versions; if a flag is rejected, run amass enum -h to see the current ones.httpx — Filter Hundreds of Subdomains to Live Targets Only
After enumeration you have a large raw list — many dead, parked, or no longer resolving. httpx probes each one over HTTP and HTTPS, records which respond, and returns page title, status code, and technology stack for each. Your raw list goes from noise to testable signal in one command.
cat combined.txt | httpx \
-mc 200,301,302,403 \ # match these status codes
-title \ # capture page title
-tech-detect \ # identify web technology stack
-o live.txt # save to file
# ─── Extract priority subdomain patterns immediately ────────────
grep -iE “dev\.|staging\.|admin\.|internal\.|test\.|beta\.” live.txt
ffuf — Directory Fuzz Live Targets to Find Hidden Endpoints
Once you have live priority subdomains, directory fuzzing finds hidden admin panels, API paths, backup files, and forgotten endpoints not publicly linked. Pair ffuf findings with Burp Suite (Day 5 Deep Dive) — browse each discovered path through Burp Proxy to capture the full request-response cycle in HTTP History.
sudo apt install ffuf -y
# ─── Basic directory fuzz on a priority subdomain ───────────────
ffuf -u https://dev.target.com/FUZZ \
-w /usr/share/seclists/Discovery/Web-Content/directory-list-2.3-medium.txt \
-mc 200,301,302,403 \
-t 40 -o dirs.json
# ─── Filter false positives (custom 404 pages) ──────────────────
ffuf -u https://dev.target.com/FUZZ \
-w wordlist.txt -mc 200,301 -fs 1234 # filter by response size
# ─── Hunt high-value extensions alongside directories ───────────
ffuf -u https://dev.target.com/FUZZ \
-w wordlist.txt \
-e .php,.bak,.zip,.sql,.env,.txt \
-mc 200,301
The Complete 7-Command Recon Pipeline
staging.target.com → PHP 7.1 EOL, /phpinfo.php [200] ← server config exposed
internal.target.com → Django 2.1 EOL, /dashboard/ [200] no auth required
admin.target.com → 403 Forbidden → test X-Original-URL / X-Forwarded-For bypass
# 1. Certificate transparency (passive, zero target contact)
curl -s “https://crt.sh/?q=%.target.com&output=json” | jq -r ‘.[].name_value’ | sort -u | grep -v ‘^\*’ > crt.txt
# 2. Subfinder aggregation (passive, 40+ sources)
subfinder -d target.com -silent -o subfinder.txt
# 3. Amass passive
amass enum -passive -d target.com -o amass.txt
# 4. Combine and deduplicate all sources
cat crt.txt subfinder.txt amass.txt | sort -u > all_subs.txt
# 5. Filter to live hosts with tech detection
cat all_subs.txt | httpx -mc 200,301,302,403 -title -tech-detect -o live.txt
# 6. Extract and review priority subdomain patterns
grep -iE “dev\.|staging\.|admin\.|internal\.|test\.” live.txt
# 7. Directory fuzz each priority target
ffuf -u https://PRIORITY_SUBDOMAIN/FUZZ -w /usr/share/seclists/Discovery/Web-Content/directory-list-2.3-medium.txt -mc 200,301,403 -t 40
Prioritisation & Burp Suite Handoff
After the pipeline runs, you have a map. Here is how to prioritise it and hand it directly to your Burp Suite workflow from Day 5.
📋 Subdomain Recon Reference Card
| jq -r ‘.[].name_value’ | sort -u
subfinder -d DOMAIN -silent -o subs.txt
amass enum -passive -d DOMAIN
-mc 200,301,302,403 \
-title -tech-detect -o live.txt
grep -iE “dev\.|staging\.” live.txt
-w directory-list-2.3-medium.txt \
-mc 200,301,403 -t 40
# Add -e .bak,.env,.sql,.php
Burp Proxy ON → capture requests
HTTP History → send to Repeater
Systematic param testing begins
You have the map and the Burp Suite skills from Day 5. Day 7 teaches you to hunt the most consistently findable vulnerability type across those targets — XSS.
Frequently Asked Questions
The highest-paying bug I ever found was on legacy-api.target.com — not listed anywhere public, found via crt.sh in under 10 minutes. No authentication on a user data endpoint. Complete account takeover for any user ID. It had been live for three years. Three years of zero testing because no one looked. Do the recon other hunters skip. Then open those priority subdomains in Burp exactly as you set it up in Day 5 and work through every parameter methodically.


1 Comment