Individual skill

performing-subdomain-enumeration-with-subfinder

Enumerate subdomains of target domains using ProjectDiscovery's Subfinder passive reconnaissance tool to map the attack surface during security assessments.

internal/tools/skills/data/web-application-security/performing-subdomain-enumeration-with-subfinder/SKILL.md

Read pinned source

Source commit d42f381ad34843e71a42658e5c57290c713e85af

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,310
Repository last updated
Nov 7, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Performing Subdomain Enumeration with Subfinder

## When to Use
- During the reconnaissance phase of penetration testing or bug bounty hunting
- When mapping the external attack surface of a target organization
- Before performing vulnerability scanning on discovered subdomains
- When building an asset inventory for continuous security monitoring
- During red team engagements requiring passive information gathering

## Coverage Gaps & Validation

- **Subfinder alone is passive-only** — combine it with active brute-force/permutation tooling or you will miss internal-only and never-logged names. Run `subfinder -all` AND `amass enum -active`, then add brute force: `puredns bruteforce wordlist.txt example.com -r resolvers.txt` and permutations: `gotator -sub subs.txt -perm permutations.txt | puredns resolve`.
- **Wire up API keys** — without Shodan/Censys/VirusTotal/SecurityTrails/Chaos/GitHub keys, passive sources return a fraction of results. An empty `provider-config.yaml` is the #1 cause of false "no subdomains" conclusions.
- **Mine certificate transparency directly** — `curl -s 'https://crt.sh/?q=%25.example.com&output=json' | jq -r '.[].name_value' | sort -u` and the `ctfr`/`tls.bufferover.run` sources catch names CDN-fronted tools miss.