Recon for Bug Bounty Hunters
Recon in bug bounty is the stage of discovering what a target actually exposes before testing it. It involves finding subdomains, live hosts, open ports, endpoints, parameters and technologies, then automating the repetitive parts with scripts. Wider, well-organised asset discovery finds forgotten applications that fewer hunters have tested.
Stage: Reconnaissance · Part of the Bug Bounty Hunter roadmap · Last reviewed 19 November 2026
What to learn in Recon
- Enumerate subdomains with passive sources and resolve the live ones
- Probe hosts for open ports and web technologies
- Collect endpoints and parameters from archives and JavaScript files
- Chain tools in a shell script and store results in organised files
- Schedule recon to detect newly appearing assets
Recon interview questions
Why is subdomain enumeration valuable in bug bounty?
Companies run many subdomains, and older or internal-facing ones are often forgotten, less hardened and less tested. Finding them expands the attack surface you can legally test within scope and raises the chance of a unique, non-duplicate finding.
What is the difference between passive and active recon?
Passive recon gathers information without touching the target, using certificate logs, search engines and public archives. Active recon sends traffic to the target, such as port scans or brute-forced names. Active methods must respect program rate limits and rules.
Where Recon fits in the Bug Bounty Hunter roadmap
Recon belongs to the Reconnaissance stage (intermediate level). Find the attack surface.
Back to the full Bug Bounty Hunter roadmap