Recon for Penetration Testers
Recon, short for reconnaissance, is the information gathering phase where a tester learns about the target before touching it. Passive methods use public sources such as WHOIS, DNS records, certificate transparency and search engines, while active methods query the target directly. Good recon reveals subdomains, technologies and people.
Stage: Engagement Basics · Part of the Penetration Tester roadmap · Last reviewed 19 November 2026
What to learn in Recon
- Enumerate subdomains using certificate logs and DNS brute forcing
- Query WHOIS and DNS records to map a target's infrastructure
- Use search operators to find exposed files and login pages
- Identify web technologies and versions from headers and fingerprints
- Separate passive reconnaissance from active reconnaissance and record the source
Recon interview questions
What is the difference between passive and active reconnaissance?
Passive recon collects information from public sources without sending traffic to the target, so it is hard to detect. Active recon, such as port scanning or probing a web server, interacts with the target directly and can show up in its logs.
Why are certificate transparency logs useful in recon?
Public TLS certificates are recorded in open logs, and each lists the domain names it covers. Searching them can reveal subdomains and internal-looking hostnames that never appeared in DNS lists or search engines.
Where Recon fits in the Penetration Tester roadmap
Recon belongs to the Engagement Basics stage (intermediate level), which takes about 38 hours. Plan the test.
Other units in this stage
Back to the full Penetration Tester roadmap