OSINT & Attack-Surface Search Engines, Mapped

Attackers start by searching the internet for your exposed servers, certificates, code and leaked credentials. The same 24 engines let you find them first. Here they are, grouped by the question each one answers.

24search engines
7questions they answer
1routine: check yourself monthly
0packets you need to send to your target

Ordinary search engines index web pages. These index everything else: every server answering on every port, every TLS certificate ever issued, years of DNS records, public code, and what threat-intelligence systems have seen. An attacker can map an organisation’s external footprint without touching it. That is why these tools belong to defenders first: your attack surface is whatever these engines can see, and they will show it to anyone who asks.

1 · Twenty-Four Engines, Seven Questions

QuestionEnginesWhat you learn
What is exposed?Shodan, Censys, FOFA, ZoomEye, Netlas, Criminal IP, ONYPHEInternet-facing hosts, open ports, service banners, product versions, industrial and IoT devices
What is leaking?LeakIXMisconfigured services and exposed data stores found on scan
What certificates and names exist?crt.sh, SecurityTrails, DNSDumpsterEvery certificate logged for your domains (Certificate Transparency), historical DNS, forgotten sub-domains
Is this bad?VirusTotal, urlscan.io, AlienVault OTX, GreyNoiseReputation of files, URLs, domains and IPs; whether an IP is a mass scanner or a targeted attacker
What is in public code?GitHub code search, grep.app, PublicWWWLeaked keys and internal hostnames in repositories; pages and scripts that embed a given snippet
Who and what runs it?BuiltWith, Hunter.io, WiGLE, Intelligence XWebsite technology stacks; staff email formats; Wi-Fi network locations; historical and leaked data archives
Is it vulnerable?Vulners, Google (advanced operators)CVEs and exploits for a product version; indexed documents, login pages and directory listings that should not be public

Most offer free searches with limits and paid tiers for bulk queries, history and APIs. Coverage differs — the same host can look different in Shodan, Censys and FOFA, so defenders usually check more than one.

2 · A Monthly Self-Check for Defenders

One hour a month finds most of what an attacker’s first hour would. Run it against your own domains and IP ranges:

  1. Certificates: search crt.sh for your domains. Every unfamiliar sub-domain is either an unlisted asset or someone else’s certificate for your name.
  2. Exposed services: search Shodan and Censys for your IP ranges and organisation name. Flag remote-desktop, database, admin-panel and VPN ports, and versions with known exploited vulnerabilities.
  3. DNS history: check SecurityTrails or DNSDumpster for records pointing at servers you no longer own — the raw material of sub-domain takeover.
  4. Code leaks: search GitHub and grep.app for your domains, internal hostnames and key prefixes. Rotate anything found, then remove it.
  5. Search-engine exposure: use Google operators (site:, filetype:, intitle:) on your own domains for documents and login pages that should not be indexed.
  6. Reputation: look up your mail servers and public IPs in VirusTotal and OTX. A flagged address hurts email delivery and can signal a compromise.
  7. Record it: new findings feed the “unknown internet-facing assets” and “critical services exposed” risk indicators in Cybersecurity KRIs.

3 · The Legal Line

ActivityGenerally
Searching these engines’ existing indexesPassive research — you read data the engine already collected
Checking your own organisation’s exposureExpected good practice
Logging in to an exposed panel, database or device you foundUnauthorised access — sections 43 and 66 of India’s IT Act, 2000, whatever the default password was
Scanning or exploiting systems you do not ownOnly with written authorisation, such as a signed engagement or a bug-bounty scope
Collecting staff names and emailsPersonal data — processing it can bring obligations under the DPDP Act; keep it to authorised work

This is general information, not legal advice. See Cyber Crime & Law in India.

Bottom line

  • Your attack surface is what these engines can see — and anyone can ask them.
  • Seven questions: exposed, leaking, certificates and names, reputation, code, people and tech, vulnerabilities.
  • Certificates and DNS history find the assets nobody listed.
  • Check monthly, and feed what you find into your risk indicators.
  • Searching is passive; logging in is not — stay on your own side of the line.

Sources & method. Engine capabilities from each service’s public documentation as of November 2026; features and free limits change often. Grouping by question and the self-check routine are the author’s analysis. Legal notes are general information on the Information Technology Act, 2000 and the Digital Personal Data Protection Act, 2023, not legal advice. Original analysis; no third-party graphics or text reproduced.

← Back to Cyber security