google-dorks-catalog

Identify exposed configuration files and credentials using pre-validated Google dork queries.

1.1k|191|Updated Jun 24, 2026
One-click install
npx skills add https://github.com/uphiago/recon-skills --skill google-dorks-catalog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: google-dorks-catalog
Source: https://github.com/uphiago/recon-skills/tree/main/meta/google-dorks-catalog
Command: npx skills add https://github.com/uphiago/recon-skills --skill google-dorks-catalog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually crafting effective Google dorks to locate exposed sensitive data like credentials, configuration files, and secrets is time-consuming and often yields low-quality results, especially during the critical passive reconnaissance phase of security assessments.

Core Features & Use Cases

  • Validated High-Precision Dorks: 100+ real-world tested queries for exposed files, service-specific secrets (AWS, Firebase, Supabase, etc.), and configuration leaks confirmed against 100+ real targets.
  • GitHub Code Search Patterns: Pre-built API queries to find leaked credentials in public GitHub repositories, with filters to reduce false positives from example code.
  • Use Case: For example, during the initial passive recon phase of a penetration test, use this skill to quickly identify exposed .env files, API keys, and private keys for a target domain without triggering active scanning alerts.

Quick Start

Use the google-dorks-catalog skill to run the validated exposed config dorks for your target domain to identify any publicly leaked sensitive files and credentials.

Frequently Asked Questions about google-dorks-catalog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find exposed secrets and config files during passive reconnaissance?

Use validated Google dorks to locate exposed secrets and configuration files for target domains during passive reconnaissance. This approach applies 100+ pre-tested queries to identify leaked credentials without triggering active scanning alerts.

Can I use GitHub code search patterns to hunt for leaked API keys?

Yes, you can use pre-built GitHub code search patterns to hunt for leaked API keys. These API queries include specific filters to reduce false positives from example code and locate hardcoded credentials in public repositories.

What is the best way to discover exposed AWS or Firebase credentials for a target domain?

The best way to discover exposed AWS or Firebase credentials is using high-precision Google dorks validated against real targets. These queries specifically target service-specific secrets and sensitive configuration leaks to reduce attack surface.

Does passive reconnaissance with Google dorks work for red teaming assessments?

Passive reconnaissance with Google dorks works effectively for red teaming assessments. It provides early detection of leaked data and identifies high-value targets without sending direct requests to the target infrastructure.

How do I extract certificate SANs to automate the discovery of exposed assets?

Extract certificate SANs using provided command-line commands to automate the discovery of exposed assets. This maps the target's attack surface by enumerating subdomains and associated infrastructure from certificate transparency logs.