google-dorks-catalog – Other skill for AI agents

Google Dorks Catalog -- Exposed Configs & Secrets

When to Use

• During passive reconnaissance (Phase 1) on every target
• After crt.sh subdomain enumeration
• Before any active scanning
• Validated against 100+ real targets

High-Precision Dorks

Critical Exposed Files

site:$target "APP_KEY"
site:$target "DB_PASSWORD"
site:$target "-----BEGIN RSA PRIVATE KEY-----"
site:$target filetype:env
site:$target inurl:git/config
site:$target intitle:"index of" ".env"
site:$target "api_key" OR "apikey" OR "secret_key"
site:$target "firebase" "apiKey"
site:$target "supabase" "anon" "key"
site:$target inurl:"/.env" "DB_PASSWORD"
site:$target "client_secret" "redirect_uris" extension:json
site:$target "private_key" "client_email" extension:json

Exposed Configuration Files (ALL Extensions)

site:$target ext:log | ext:txt | ext:conf | ext:cnf | ext:ini | ext:env | ext:sh | ext:bak | ext:backup | ext:swp | ext:old | ext:~ | ext:git | ext:svn | ext:htpasswd | ext:htaccess | ext:json

This covers:

• logs -- tokens, SQL queries, emails in plain text
• txt/conf/cnf/ini -- server configurations, DB hosts
• env -- environment variables with credentials
• sh -- scripts with hardcoded passwords
• bak/backup/swp/old/~ -- backup files with old versions
• git/svn -- exposed versioned repositories
• htpasswd/htaccess -- access control with hashes
• json -- service accounts, Firebase configs, Supabase configs

Service-Specific Dorks

Supabase

site:$target "supabase.co" "anon_key" OR "SUPABASE_ANON_KEY"

Firebase

site:$target "firebase-adminsdk" "private_key_id" extension:json

AWS

site:$target "AKIA" filetype:env NOT example NOT test

SendGrid

site:$target "SG." filetype:env NOT example

MongoDB

site:$target "mongodb+srv://" "password"

PostgreSQL

site:$target "postgresql://" "password" ext:env

JWT Secrets

site:$target "JWT_SECRET" OR "jwt_secret" filetype:env

OpenAI API Keys

site:$target "sk-" filetype:env OR filetype:txt

GitHub Tokens

site:$target "ghp_" OR "gho_" OR "ghu_"

GitHub Code Search Patterns

With GitHub personal token (much better results):

headers = {"Authorization": "token GH_TOKEN"}
base = "https://api.github.com/search/code"

# SA Keys (Firebase/GCP) -- ~1 in 30 is valid
params = {"q": '"type": "service_account" "private_key" "project_id"'}

# .env with real credentials
params = {"q": 'DB_PASSWORD+DB_HOST+APP_KEY+filename:.env+NOT+example+NOT+your+NOT+test'}

# Supabase URLs + keys
params = {"q": 'supabase.co+SUPABASE_URL+SUPABASE_ANON_KEY+NOT+example+NOT+your'}

# AWS Keys
params = {"q": 'AKIA+filename:.env+NOT+example+NOT+your'}

# SendGrid keys
params = {"q": 'SG.+filename:.env+NOT+example'}

# MongoDB connection strings
params = {"q": 'mongodb+srv://+password+filename:.env'}

Certificate SAN Discovery

# Extract SANs directly from the certificate
openssl s_client -connect $TARGET:443 -servername $TARGET </dev/null 2>/dev/null | \
  openssl x509 -noout -ext subjectAltName | grep -Eo 'DNS:[^,]+' | cut -d: -f2 | sort -u

Real-World Cases

Real-world case (redacted): SSO certificate revealed ORG_DOMAIN_1, ORG_DOMAIN_2, ORG_DOMAIN_3 that didn't appear in conventional CT searches.

Pitfalls

| Issue | Solution |

|-------|----------|

| Google rate limits | Space out searches, use incognito, rotate IP |

| GitHub API limits | Use personal token (5000 req/hr) |

| False positives from example repos | Append NOT example NOT test NOT your |

Verification

# Test dork results manually
curl --max-time 30 --connect-timeout 10 -sk "https://$TARGET/.env" | head -5
# Verify GitHub found secrets
python3 -c "import json; print(json.loads(open('result.json').read()))"