Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Passive reconnaissance gathers information about a target without touching it; active reconnaissance interacts directly with its systems. The distinction shapes both testing and detection.

What Are Passive and Active Reconnaissance?
Reconnaissance splits neatly along one line: did you touch the target, or did you not. Passive reconnaissance collects information from third parties and public records, leaving nothing in the target’s logs. Active reconnaissance sends packets or requests to systems the target owns, which produces results you cannot get any other way and, inevitably, evidence that someone was looking.
Every real intrusion and every authorised test begins here. MITRE ATT&CK gives the stage its own pre-attack tactic, Reconnaissance (TA0043), because so much of what follows depends on how well it was done.
Passive work draws on records that other people keep. Domain registration data, historical WHOIS, DNS records held by public resolvers, and passive DNS archives build a picture of infrastructure. Certificate Transparency logs are particularly generous: every publicly trusted TLS certificate is logged, so a search of crt.sh for an organisation’s domain routinely exposes internal naming conventions and staging hostnames that were never meant to be advertised.
Beyond infrastructure, there is the human layer. Job adverts name the exact versions of firewalls, EDR agents, and ERP systems a company runs. Conference talks describe architecture. Professional networking profiles yield a staff list, which becomes an email address list once the naming format is known. Public code repositories leak credentials and internal URLs in commit history. Breach compilations supply passwords that employees may have reused.
Internet-wide scanning services such as Shodan and Censys occupy an interesting middle ground. The scanning was active, but somebody else did it, so querying their results leaves no trace on the target.
Active reconnaissance means interaction. Port scanning with Nmap, grabbing service banners, fingerprinting TLS stacks, attempting DNS zone transfers, enumerating subdomains by resolving candidates against the target’s own nameservers, brute-forcing directories on a web server, and probing SMB shares all fall into this category.
| Question | Passive | Active |
|---|---|---|
| Traces in target logs | None | Connection, DNS, and web logs |
| Accuracy | Possibly stale | Current |
| Depth | What others have published | Live service versions and configurations |
| Legal position | Generally lawful | Needs written authorisation |
That last row matters in the UK. Unauthorised access to a computer system is an offence under the Computer Misuse Act 1990, and there is no research exemption. Scanning somebody else’s infrastructure without permission is a risk no professional should take, which is why the rules of engagement for a test define the active phase in precise terms.
Sensible engagements run passive work first and use it to aim the active work. Certificate logs and passive DNS produce a candidate list of hostnames; active resolution and port scanning confirm which of them are live and what they run. A red team may stay passive for weeks, because the point of the exercise is to see whether the blue team notices anything, and noisy scanning ends that question early.
Time-boxed tests make the opposite trade. With five days to cover a large estate, testers accept the noise and scan hard, since finding the flaw matters more than staying quiet.
You cannot stop passive reconnaissance, but you can shrink what it returns. Monitor Certificate Transparency logs for your own domains so you learn about new hostnames at the same time an attacker would. Scan your public repositories for secrets. Review what job adverts disclose about internal tooling. Keep DNS tidy and remove records pointing at decommissioned services, which also closes off subdomain takeover.
Active reconnaissance is detectable, and the detections are worth building. Alerts for sequential connection attempts across many ports, bursts of 404 responses consistent with directory brute-forcing, failed zone transfer attempts, and requests carrying obvious scanner user agents all give early warning. A honeypot host on an unused subnet produces a high-confidence alert, because nothing legitimate should ever connect to it.
Our Penetration Test Services start with the same footprinting an attacker would perform, so you see your external exposure before somebody else does.
Reading public records, certificate logs, published code repositories, and search engine results is lawful in the UK, because you are not accessing the target’s systems. Care is still needed with personal data, since compiling profiles of named employees engages UK GDPR. Authorised testers handle anything gathered under the engagement contract and delete it when the work finishes.
Rarely, and only indirectly. Because the queries go to third parties, nothing reaches your infrastructure. Some organisations watch for secondary signals, such as sudden interest in their Certificate Transparency entries or scraping of their careers pages, but these are weak indicators. The practical response is to reduce what public sources reveal rather than to try to detect the lookups.
Passive work typically uses Amass in passive mode, theHarvester, SpiderFoot, Shodan, Censys, and Certificate Transparency search. Active work uses Nmap, masscan, DNS brute-forcing tools, directory fuzzers such as ffuf or gobuster, and web crawlers. Several frameworks do both, so testers must understand which mode they are actually running before they begin.
It depends on the engagement. A one-week external test might spend a day on reconnaissance. A red team operation simulating a determined adversary can spend several weeks on passive collection alone, because stealth is part of what is being tested. In both cases, time spent here usually reduces time wasted later on targets that were never exploitable.
You May Be Interested In These
Cybersecurity Terms
17 November 2026
What Is Physical-Cyber Convergence in Critical Infrastructure?
Read More
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.