google-dorks-catalog

Google dorking finds exposed environment files by running curated search queries targeting specific file extensions like .env and .git. This skill provides validated search patterns to locate sensitive configuration files and infrastructure metadata indexed by search engines.

You can search for leaked API keys in public GitHub repositories using optimized API patterns. This skill provides specific GitHub code search patterns designed to locate exposed service account tokens and database credentials.

Reconnaissance dorking is the process of using advanced search engine queries to identify sensitive information leaks. You need it during the passive reconnaissance phase of a security assessment to quickly find misconfigured assets without active scanning.

You need GitHub API authentication to effectively execute the provided search patterns for GitHub code analysis. Alternatively, standard web browser access is sufficient to run the curated Google search queries for finding exposed configuration files.

You can locate exposed infrastructure metadata including private keys, cloud bucket configurations, and environment variables. The search queries specifically target sensitive configuration files and service-specific credentials inadvertently indexed by search engines.

A limitation of search engine dorking is that it only finds information already indexed by search engines, missing recently exposed or unindexed files. It targets specific file extensions and service-specific credentials but cannot detect actively hidden infrastructure secrets.