Google Hacking, also known as Google Dorking, is a powerful reconnaissance strategy that involves using advanced search operators within the Google search engine to identify sensitive information or vulnerabilities that are inadvertently exposed on the public internet. By utilizing specific syntax—such as site:, filetype:, intitle:, and inurl:—an attacker or an ethical hacker can filter search results to find "low-hanging fruit" that would be impossible to locate with a standard query.

Common targets of Google Hacking include exposed database configuration files (which might contain passwords), server logs that reveal internal IP addresses, and "Index of" directories that provide a raw view of a server's file structure. For example, a search like filetype:env "DB_PASSWORD" could potentially reveal environment variables for web applications. This is an essential attack vector to mitigate because it requires no specialized hacking software; it simply exploits the fact that Google's crawlers have indexed files that administrators forgot to protect or hide via robots.txt.

Managing this vector involves "Self-Dorking"—regularly searching one's own domain using these advanced techniques to see what information is visible to the public. Mitigation strategies include proper server configuration, ensuring that sensitive files are not stored in the webroot, and using authentication for all administrative interfaces. From a penetration testing perspective, Google Hacking is part of the "Passive Reconnaissance" phase, allowing a tester to gather intelligence about a target's infrastructure without ever sending a single packet directly to the target's servers. This highlights how easily information leakage can lead to a full system compromise if not actively monitored.