Google Dorks & AI Recon Tool | OSINT & Ethical Hacking | A7 Security Hunters
Bug Bounty Reconnaissance

Google Dorks & AI Recon

Complete toolkit for passive target reconnaissance — from automated Google dork scanning to AI-powered attack surface discovery. Every tool, every parameter, every command explained for bug bounty hunting.

21
Tools
50+
Dork Templates
4
Workflows
🔍

Google Dorking Tools

These tools automate Google dork searches against your target. They help you discover exposed files, admin panels, database dumps, config files, and sensitive directories that are indexed by Google but shouldn't be. Always use proxies to avoid IP bans.

① Pagodo — Passive Google Dork (Python) CLI

The most mature Google dork automation tool. It scrapes the latest dorks from the Exploit-DB Google Hacking Database (GHDB) and then runs targeted searches against your domain. Supports round-robin proxy rotation, custom delay intervals, and JSON output.

⚙ Installation & Setup
BASH
# Clone and install
git clone https://github.com/opsdisk/pagodo.git
cd pagodo
pip install -r requirements.txt

# Always scrape the latest GHDB dorks before scanning
python ghdb_scraper.py -s -j -i
⚙ Full Parameter Reference
FlagDescriptionExample
-g, --google_dorks_filePath to dork file (1 dork per line). Required.-g dorks/sensitive_files.dorks
-d, --domainTarget domain to scope all dork searches.-d target.com
-m, --max-search-urlsMax results per dork (default: 100). Higher = more results but slower.-m 500
-i, --minimum-delayMin delay in seconds between dork searches (default: 37). Lower = faster but more bans.-i 12
-x, --maximum-delayMax delay in seconds between dork searches (default: 60). Random value chosen between -i and -x each time.-x 20
-p, --proxiesComma-separated proxy list. Supports HTTP(S) and SOCKS5. Round-robin rotation.-p socks5h://127.0.0.1:9050,http://proxy:8080
-o, --save-jsonSave results to JSON file (auto-generated name or custom path).-o results.json
-s, --save-urlsSave discovered URLs to a plain text file.-s urls.txt
-l, --disable-ssl-verificationDisable SSL/TLS validation (needed for self-signed proxy certs).-l
-v, --verbosityLogging verbosity level (1-5, higher = more output).-v 5
-z, --logCustom log filename (default: pagodo.py.log).-z scan.log
🚀 Bug Bounty Usage Examples
BASH
# Quick scan — error messages dork category + SOCKS5 proxy
python3 pagodo.py -d target.com -g dorks/error_messages.dorks -i 12 -x 20 -p socks5h://127.0.0.1:9050 -o results.json -s urls.txt

# Deep scan — all dorks, multiple rotating proxies
python3 pagodo.py -d target.com -g dorks/all.dorks -m 300 -p socks5h://127.0.0.1:9050,http://10.0.0.1:8080 -i 8 -x 15 -l

# Focused scan — only 'files containing passwords' category
python3 pagodo.py -d target.com -g dorks/files_containing_passwords.dorks -m 200 -o passwords_crawl.json
② go-dork — Fastest Dork Scanner (Golang) CLI

The fastest Google dork scanner written in Go. Supports 6 search engines (Google, Shodan, Bing, DuckDuckGo, Yahoo, Ask). Minimal dependencies — single binary. Perfect for quick targeted searches when you need results immediately without the overhead of Python dependency management.

⚙ Installation
BASH
go install github.com/dwisiswant0/go-dork@latest
⚙ Full Parameter Reference
FlagDescriptionExample
-q, --querySearch query / dork string. Required.-q "site:target.com inurl:admin"
-e, --engineSearch engine: Google, Shodan, Bing, Duck, Yahoo, Ask (default: Google).-e shodan
-p, --pageNumber of search result pages to scrape (default: 1).-p 10
-H, --headerCustom HTTP header (use multiple times for multiple headers).-H "Cookie: ..." -H "User-Agent: ..."
-x, --proxyProxy URL for requests.-x socks5://127.0.0.1:9050
-s, --silentSilent mode — prints only results, no banner or status messages.-s
🚀 Bug Bounty Usage Examples
BASH
③ GooFuzz — Google Dork Fuzzing (Bash) CLI

Bash-based Google dork fuzzer that enumerates files, directories, subdomains, and parameters without leaving evidence on the target server. Uses Google searches passively — the target never sees you. Colored output makes findings easy to spot.

⚙ Full Parameter Reference
FlagDescriptionExample
-t <TARGET>Target domain or IP. Required.-t target.com
-e <EXTENSION>File extensions to hunt for (comma-separated or path to wordlist).-e pdf,doc,bak,sql,env or -e extlist.txt
-w <DICTIONARY>Custom dictionary of paths, files, or keywords to fuzz.-w wordlist.txt
-p <PAGES>Number of Google result pages to scrape (default: 1).-p 10
-x <EXCLUSIONS>Exclude targets containing these keywords from results.-x "wordpress,blog"
-d <DELAY>Delay in seconds between requests to avoid rate-limiting.-d 5
-sSubdomain enumeration mode — discovers subdomains of target via Google.-s
-c <TEXT>Filter results by relevant content keywords (comma-separated).-c "password,admin,dashboard"
-o <FILENAME>Export discovered results to a file.-o GooFuzz-results.txt
-r <PROXY>Route requests through [protocol://]host[:port] proxy.-r socks5://127.0.0.1:9050
-hDisplay help message.-h
🚀 Bug Bounty Usage Examples
BASH
④ DorkScout — Automated Google Dork Scanner (Golang) CLI

Golang-based scanner that automates Google dork scans against specific targets or the entire internet. Has a built-in dork installer that pulls the latest dorks from Exploit-DB. Outputs results as HTML reports. Runs in Docker for air-gapped environments.

⚙ Full Parameter Reference
Command / FlagDescriptionExample
dorkscout installDownloads the latest Google dorks from exploit-db.com.dorkscout install
dorkscout scanRun a scan against targets using downloaded dorks.dorkscout scan -d=dorksfile -H=out.html
dorkscout deleteDeletes all .dorkscout files inside a given directory.dorkscout delete ./
-d=<FILE>Path to .dorkscout file containing dorks to use.-d="/dorkscout/Sensitive Info.dorkscout"
-H=<FILE>Output HTML report file path.-H="/dorkscout/report.html"
-x <PROXY>Proxy URL for requests.-x socks5://127.0.0.1:9050
🚀 Bug Bounty Usage Examples
BASH
⑤ Fast Google Dorks Scan (FGDS) — One-Shot Bash Script CLI

Dead-simple bash script that runs all common dork combinations against a single domain in one shot. Tests for admin panels, common file types, path traversal, and exposed directories. Perfect for the first 5 minutes of recon when you just landed on a target.

🚀 Usage
BASH
⑥ Web-Based Dork Resources — Interactive + AI-Assisted WEB
ToolWhat It DoesWhy Use It
Exploit-DB GHDB
exploit-db.com/google-hacking-database
The original Google Hacking Database. 7,000+ categorized dorks maintained by OffSec. Filter by category: Footholds, Sensitive Directories, Files Containing Passwords, Vulnerable Servers, etc.Most comprehensive, continuously updated. Filter by category to focus on what matters for your bug bounty target. Copy-paste dorks directly.
DorkGPT
dorkgpt.com
AI-powered dork generator. Type "find exposed .env files on target.com" in plain English — returns precise Google dorks instantly. Categorized dork libraries with export.Zero dork syntax memorization. Describe what you want to find, get the dork. Great for junior bug bounty hunters or when you need an obscure dork fast.
DorkSearch
dorksearch.com
Online searchable dork repository. Browse thousands of dorks by vulnerability type, file type, or target platform. Copy-paste ready queries.Fast way to find dorks for specific technologies (Jira, GitLab, Jenkins, phpMyAdmin, etc.).
Advangle
advangle.com
Visual drag-and-drop advanced search query builder for Google, Bing, and Yahoo. No syntax memorization — build complex queries visually.Best for constructing multi-operator dorks (AND/OR/NOT logic) when targeting complex scenarios.
📝

Bug Bounty Dork Library

Ready-to-use Google dork templates organized by bug bounty target type. Replace target.com with your target domain. These dorks discover exposed sensitive files, admin panels, debug endpoints, and more — all passively via Google.

📁 Sensitive Files & Configurations

.env Files (Laravel / PHP environment variables)
site:target.com ext:env "DB_PASSWORD" OR "APP_KEY" OR "AWS_SECRET"
Exposes database credentials, API keys, and application secrets. Critical severity if found.
WordPress wp-config.php
site:target.com ext:php intext:"DB_PASSWORD" intext:"wp-config" -intext:"example"
MySQL credentials, auth keys, and salts for WordPress installations.
Backup / SQL Dump Files
site:target.com ext:sql | ext:sql.gz | ext:bak | ext:backup "CREATE TABLE" OR "INSERT INTO"
Full database dumps with user tables, password hashes, and PII. Goldmine for bug bounty.
JSON Config / Credential Files
site:target.com ext:json "password" | "secret" | "api_key" | "token"
Application config files often left in web root exposing credentials and API tokens.
Docker / Docker-Compose Files
site:target.com ext:yml | ext:yaml "docker-compose" "environment:" "POSTGRES_PASSWORD"
Container orchestration configs often contain database passwords, volume mounts, and network config.

🔑 Admin Panels & Login Portals

Generic Admin Panels
site:target.com inurl:admin | inurl:login | inurl:dashboard | inurl:panel intitle:"admin"
Admin interfaces often exposed without proper IP restrictions. Test default credentials.
phpMyAdmin Exposed
site:target.com inurl:phpmyadmin intitle:"phpMyAdmin"
Direct database admin panel. Even without creds, version disclosure leads to CVE exploitation.
Jenkins CI/CD
site:target.com intitle:"Dashboard [Jenkins]" OR inurl:":8080/jenkins"
Jenkins instances often expose build logs with credentials, tokens, and internal URLs.
GitLab Instances
site:target.com intitle:"GitLab" inurl:"users/sign_in" OR inurl:"explore"
Self-hosted GitLab may expose private repos, CI/CD variables, and issue trackers.
Jira / Confluence
site:target.com inurl:"/browse/" intitle:"Jira" OR intitle:"Confluence"
Issue trackers and wikis often contain internal hostnames, credentials in comments, and API endpoints.

🔧 API Endpoints & Debug Information

Swagger / OpenAPI Specs
site:target.com inurl:swagger | inurl:api-docs | inurl:openapi.json | intitle:"Swagger UI"
Complete API documentation exposing endpoints, parameters, and auth mechanisms.
GraphQL Endpoints
site:target.com inurl:graphql | inurl:graphiql intitle:"GraphiQL" OR "query"
Interactive GraphQL consoles enable schema introspection and sensitive data queries.
PHP Info / Debug Pages
site:target.com intitle:"phpinfo()" OR inurl:phpinfo.php OR inurl:debug
Full server config disclosure — paths, modules, environment variables, loaded extensions.
Error Messages Leaking Info
site:target.com intext:"SQL syntax" | intext:"stack trace" | intext:"Fatal error" | intext:"Warning:"
SQL errors reveal database structure. Stack traces expose file paths, library versions, and logic.

📤 File Upload & Storage Discovery

Open Directory Listings
site:target.com intitle:"index of" OR intitle:"Index of /"
Directory listing enabled — browse server files directly. Look for backup archives and configs.
S3 Buckets in Source / HTML
site:target.com intext:"s3.amazonaws.com" OR intext:"s3://" OR intext:"blob.core.windows.net"
Cloud storage URLs embedded in pages. Test for misconfigured public access.
Uploaded Files / User Content
site:target.com inurl:uploads | inurl:upload | inurl:files | inurl:attachments
User upload directories — may contain PII, ID documents, or executable content.

🌐 Subdomain & Asset Discovery

Subdomains via Google
site:*.target.com -www -blog -shop -support -shopify
Discover unknown subdomains by excluding known ones. Repeat to progressively reveal more.
Dev / Staging / Test Environments
site:target.com inurl:dev | inurl:staging | inurl:test | inurl:uat | inurl:beta
Non-production environments with weaker security controls — easier targets for testing.
Internal Hostnames Leaked
site:target.com intext:"internal" OR intext:"intranet" OR intext:"localhost" OR intext:"192.168."
Pages referencing internal IPs and hostnames — useful for mapping internal infrastructure.

⚙ Technology-Specific Dorks

Kibana / Elasticsearch
site:target.com intitle:"Kibana" OR inurl:".kibana" OR inurl:"app/kibana"
Log visualization dashboards — may expose application logs, errors, and PII.
Firebase / Firestore
site:target.com intext:"firebaseio.com" OR intext:"firestore.googleapis.com"
Real-time database URLs in client-side code. Test for missing authentication rules.
Apache Tomcat
site:target.com intitle:"Apache Tomcat" inurl:"/manager/html"
Tomcat Manager — deploy WAR files for RCE if default credentials are unchanged.
Laravel Debug Mode
site:target.com intext:"Whoops! There was an error." OR "APP_DEBUG=true"
Laravel debug mode exposes stack traces, environment variables, and application secrets.
🤖

AI-Powered Reconnaissance Tools

These tools use large language models and machine learning to automate and enhance reconnaissance. They reason about target architecture, plan attack chains, analyze screenshots with computer vision, and correlate findings — doing in minutes what would take a human hours.

① IVRE — Build Your Own Shodan/Censys Alternative FRAMEWORK

Self-hosted network reconnaissance framework that integrates Nmap, Masscan, Zeek, Nuclei, ZGrab2, and ProjectDiscovery tools. Stores results in MongoDB and provides a web UI for analysis. Think of it as your private Shodan that you control — perfect for tracking target infrastructure changes over time during long-term bug bounty engagements.

⚙ Key Tools Integrated
CategoryToolsPurpose
Active ScanningNmap, Masscan, ZGrab2, ZDNSPort scanning, banner grabbing, TLS inspection
Passive MonitoringZeek, p0f, Argus, NfdumpNetwork flow analysis, OS fingerprinting
Web/App ScanningNuclei, httpx, dnsx, tlsxVulnerability scanning, HTTP probing, subdomain enum
🚀 Bug Bounty Usage
BASH
② Eyeballer — AI Screenshot Triage (Bishop Fox) AI

Convolutional neural network that automatically analyzes webpage screenshots to identify login pages, admin dashboards, error pages, and other interesting content. During external perimeter assessments, Eyeballer can triage thousands of screenshots and flag the interesting ones — eliminating hours of manual visual review. Trained on real pentest data from Bishop Fox.

🚀 Bug Bounty Workflow
BASH
③ Nebula — AI Pentest Assistant (Beryllium) AI

LLM-powered assistant that augments every stage of the penetration testing workflow: reconnaissance, vulnerability analysis, exploitation guidance, and report generation. It doesn't replace testers — it reasons about application behavior, suggests attack paths based on findings, and drafts findings in real-time during engagements.

🚀 Bug Bounty Usage
BASH
④ HexStrike AI — Multi-Agent Attack Orchestration AI

Advanced AI-powered pentesting framework with 150+ integrated security tools and 12+ autonomous AI agents. Uses Gemini CLI (MCP server) for natural language attack orchestration. Agents can independently run tools, analyze output, and decide the next step — think "AI red team operator."

⑤ Zen AI Pentest — 72+ Tools, Autonomous Agents AI

Professional AI-powered pentesting framework with autonomous agents, 72+ integrated security tools (Nmap, BloodHound, Subfinder, Amass, Nuclei, CrackMapExec), real-time tool execution via REST API. Built for security professionals, bug bounty hunters, and enterprise teams. 100% open source with Swagger docs.

🚀 Quick Start
BASH
⑦ PentestGPT — LLM-Guided Interactive Testing AI

One of the first and most popular LLM-powered pentesting frameworks. Interactive — you describe what you see, PentestGPT reasons about the next step, suggests tools, and interprets output. Particularly strong for web application testing and CTF-style challenges. Uses GPT-4's reasoning to navigate complex attack surfaces.

⑧ LuaN1ao (鸾鸟) — Top-Ranked Autonomous Pentest AI AI

Winner of multiple 2025 AI pentesting benchmarks. Highly sophisticated — intelligently designs attack chains against real-world systems rather than following pre-scripted paths. Excels at discovering non-obvious vulnerability chains that human testers and other tools miss.

⑨ Pentest Copilot — Browser-Based AI Hacking Interface AI

Runs entirely in the browser. Describe your testing objective in natural language — "find XSS on this login form" or "test this API endpoint for IDOR" — and the AI assistant guides you with specific tool commands, methodology suggestions, and result interpretation. Great for learning or quick testing sessions.

⑩ Reconmap — AI-Assisted Pentest Management OPENSOURCE

Full pentest lifecycle management platform — planning, execution, finding documentation, and AI-assisted report delivery. Think "project management for pentests." Tracks your bug bounty targets, organizes findings, and generates client-ready reports with AI assistance.

🚀

Bug Bounty Reconnaissance Workflows

Four battle-tested workflows for bug bounty recon — from rapid first-pass to deep automated pipelines. Mix and match tools based on your engagement scope.

Workflow 1: Quick First Pass (~5 min)

When you just got a new target and want to see what's immediately exposed. Passive only — target never sees you.

BASH
Workflow 2: Deep Dork Crawl (~30-60 min)

Comprehensive Google dork scan using all GHDB categories. Rotates proxies to avoid bans. Best for long-term engagements where you want to leave no stone unturned.

BASH
Workflow 3: AI-Assisted Recon (~Ongoing)

Use AI tools to accelerate the recon phase — let LLMs reason about target architecture, suggest attack paths, and interpret complex output while you focus on exploitation.

BASH
Workflow 4: Continuous Asset Monitoring (~Cron / Scheduled)

Set up recurring scans to detect new subdomains, exposed files, and configuration changes on a target over time. Bug bounties are long games — weekly monitoring catches what one-time scans miss.

BASH
Copied to clipboard

A7 Security Hunters provides cybersecurity training, ethical hacking courses, penetration testing education, digital forensics training, AI security learning, and professional cybersecurity certifications for students and professionals across India.

Address: Mata Darwaja, Gau Karan Rd, Near SD School, landmark Gau Karn Traffic Police Choki, Plot 736a Baba Laxman Puri Colony, Makhane or, Library Wali Gali, Rohtak124001, Haryana (India) | Official Email Address- [email protected] | [email protected] | Official Phone Numbers – +91 – 7988-28-5508 | +91 – 818181-6323

© 2026 A7 Security Hunters. Cybersecurity Training, Ethical Hacking Courses & Professional Certifications.