Study guide
2.2 Footprinting Sources & Techniques
EC-Council Certified Ethical Hacker CEH
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 CEH Exam Format, Cost & Eligibility 1.2 The Five Phases of Ethical Hacking 1.3 Information Security Fundamentals 1.4 Ethical Hacking Concepts, Scope & Legal Framework 1.5 The CEH Domains & Your Study Priority Map
2 Reconnaissance, Footprinting, Scanning & Enumeration
2.1 Footprinting & Reconnaissance Concepts 2.2 Footprinting Sources & Techniques 2.3 Network Scanning Concepts 2.4 Banner Grabbing, OS Fingerprinting & Scanning Beyond IDS/Firewall 2.5 Enumeration 2.6 Vulnerability Scanning & Countermeasures
3 Vulnerability Analysis & System Hacking Phases
3.1 Vulnerability Analysis Concepts 3.2 System Hacking Methodology Overview 3.3 Gaining Access: Password Attack Concepts 3.4 Privilege Escalation Concepts 3.5 Maintaining Access: Backdoors, Rootkits & Persistence 3.6 Covering Tracks, Anti-Forensics & Blue-Team Detection
4 Malware Threats, Sniffing & Social Engineering
4.1 Malware Concepts and Taxonomy 4.2 Malware Analysis and Detection 4.3 Sniffing Concepts and Layer 2 Attacks 4.4 Sniffing Countermeasures and Detection 4.5 Social Engineering Types and Human Psychology 4.6 Social Engineering and Insider Threat Defenses
5 Network & Perimeter Hacking
5.1 Denial of Service and DDoS Attacks 5.2 Session Hijacking 5.3 Evading IDS and IPS (Defensive Focus) 5.4 Evading Firewalls 5.5 Evading Honeypots and Defensive Deception 5.6 Network Security Controls and Architecture 5.7 Packet Analysis and Secure Protocols for Defenders
6 Web Server & Web Application Hacking
6.1 Web Server Attacks & Hardening 6.2 OWASP Top 10 Overview 6.3 Injection: SQL Injection & Command Injection 6.4 Cross-Site Scripting (XSS) & CSRF 6.5 Authentication, Session & Access-Control Flaws 6.6 API & Web App Security Testing Concepts
7 Wireless Network Hacking
7.1 Wireless Concepts and Standards 7.2 Wireless Encryption 7.3 Wireless Threats and Attack Concepts 7.4 Wireless Security Countermeasures
8 Mobile Platform, IoT & OT Hacking
8.1 Mobile Platform Threats & Security Models 8.2 Mobile Attack Vectors & Risks 8.3 Mobile Device Management & Enterprise Defense 8.4 IoT Hacking Concepts & Defense 8.5 OT, ICS & SCADA Security
9 Cloud Computing & Cryptography
9.1 Cloud Computing Concepts 9.2 Cloud Threats & Attack Surfaces 9.3 Cloud Security Controls 9.4 Cryptography Fundamentals 9.5 PKI & Cryptographic Applications 9.6 Cryptanalysis, Crypto Attacks & Best Practices
2.2 Footprinting Sources & Techniques
Key Takeaways Explain This Topic AI
Google hacking (dorking) uses operators like site:, filetype:, inurl:, intitle:, and cache: to surface exposed directories, login portals, and documents the organisation never meant to publish
WHOIS reveals registrant, registrar, and contact data plus name servers; DNS footprinting maps A, AAAA, MX, NS, CNAME, TXT, and SOA records to discover hosts and mail/name servers
An unrestricted DNS zone transfer (AXFR) can dump the entire zone — every internal hostname and IP — and is one of the highest-impact footprinting misconfigurations
Network-range footprinting uses Regional Internet Registry (RIR) and routing data (traceroute, BGP) to identify the public IP blocks an organisation owns
Countermeasures include registrar privacy, restricting AXFR to authorised secondaries, split-horizon DNS, stripping document metadata, and sanitising email headers and server banners
Last updated: June 2026
Search Engines and Google Hacking
Search engines are the first footprinting source. Google hacking (or Google dorking ) uses advanced search operators to find content that organisations indexed without realising. The operators CEH tests:
- Operator What it finds Example
- site: Pages limited to one domain site:target.com
- filetype: (or ext: ) Documents of a type site:target.com filetype:pdf
- inurl: A string in the URL inurl:admin login
- intitle: A string in the page title intitle:"index of"
- cache: Google's cached copy cache:target.com
- link: / related: Linking / similar sites related:target.com
The Google Hacking Database (GHDB) , maintained by Exploit-DB, catalogues thousands of pre-built dorks for exposed cameras, login portals, configuration files, and error messages that leak versions. Operators combine with boolean logic and exclusion ( - ) to refine results, and the same techniques work on Bing ( ip: ), DuckDuckGo, and specialised engines. txt` is a hint, not a control — never rely on it to hide secrets, since it actually advertises the paths you want hidden), require authentication, remove directory listing, and request removal of already-indexed sensitive URLs through search-console tools.
WHOIS, DNS, and Network-Range Footprinting
WHOIS is a query/response protocol (TCP port 43 ) for registration databases held by registrars and Regional Internet Registries. A WHOIS lookup returns the registrant and contact details, registrar , creation/expiry dates, and the domain's name servers — a direct pivot into DNS.
DNS footprinting enumerates a domain's resource records with tools like nslookup , dig , host , and dnsenum . The records that matter:
- Record Reveals
- A / AAAA IPv4 / IPv6 address of a host
- MX Mail servers (and their priority)
- NS Authoritative name servers
- CNAME Aliases (often expose cloud providers)
- TXT SPF/DKIM, ownership-verification tokens
- SOA Zone serial, primary NS, admin email
- PTR Reverse DNS (IP → hostname)
- DNS zone transfer (AXFR)
A zone transfer replicates the full zone from a primary name server to a secondary. If a server allows AXFR to any requester, an attacker dumps every record in the zone — internal hostnames, IPs, and the whole network map — in one query ( dig axfr @ns1.target.com target.com ). This is one of the highest-value footprinting wins.
Network-range footprinting identifies the public IP blocks an organisation owns by querying the Regional Internet Registries (RIRs) — ARIN (North America), RIPE NCC (Europe), APNIC, LACNIC, AFRINIC — and by tracing routes ( traceroute / tracert ) and BGP/ASN data.
Two refinements the exam likes. First, traceroute maps the hops between you and the target and can reveal the perimeter device and the upstream provider; it works over ICMP (Windows tracert ), UDP, or TCP, and a filtered hop shows as * * * . Second, certificate transparency (CT) logs (crt.sh) and reverse-IP/passive-DNS services expand a single seed domain into dozens of subdomains and shared-hosting neighbours without ever touching the target — a powerful passive technique for discovering forgotten dev/staging hosts.
Website, Email, and Social-Media Footprinting
Website footprinting examines a target's web presence without exploiting it: HTTP response headers and banners ( Server: Apache/2.4.x , X-Powered-By: PHP/8.x ), HTML comments, robots.txt, sitemap.xml, hidden form fields and parameters, and the Wayback Machine (archive.org) for content the site has since removed. Tools like theHarvester (emails, subdomains, hosts from public sources), Maltego (graphs relationships among domains, IPs, people, and emails), Recon-ng , and Shodan / Censys (search engines for internet-connected devices, returning open ports and banners) automate much of this.
com`) — the single most useful input for password-spraying and phishing — and, via email headers (Received, Return-Path, X-Originating-IP) and tracking, the mail-server path and sometimes internal IPs. Web bugs / tracking pixels embedded in an email can further confirm when and where a message was opened, and the SPF, DKIM, and DMARC TXT records expose which servers are authorised to send for the domain (and whether spoofing protection is weak). Social-media footprinting harvests employee names, roles, locations, and technology mentions for pretexting; out-of-office auto-replies and conference talks are classic over-shares.
Competitive intelligence gathering rounds out website/email footprinting — public filings, press releases, acquisition news, and job boards reveal business direction, new technology rollouts, and staffing gaps that an attacker times campaigns around. None of this requires touching the target, which is why it is so hard to detect and why minimisation, not monitoring, is the control.
Countermeasures Summary
- Source Countermeasure
- WHOIS Registrar privacy / proxy registration
- DNS / AXFR Restrict zone transfers to authorised secondaries; split-horizon (internal vs. external) DNS
- Google dorking Authentication on sensitive paths; remove directory listing; do not rely on robots.txt to hide
- Website banners Suppress/anonymise Server and X-Powered-By headers
- Documents Strip metadata before publishing
- Email Sanitise headers at the gateway; avoid predictable address conventions where feasible
- Social media Employee OSINT-awareness training; public-content review policy
The defensive through-line: assume everything public will be aggregated, and minimise what is exposed.