opsdisk/pagodo

pagodo (Passive Google Dork) - Automate Google Hacking Database scraping and searching

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 47 minutes ago
Added to GitGenius on September 20th, 2026
Created on August 19th, 2016
Open Issues & Pull Requests: 5 (+0)
GitHub issues: Enabled
Number of forks: 555
Total Stargazers: 3,397 (+0)
Total Subscribers: 86 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 88 days
Stale 30+ days: 2
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

pagodo is a command-line tool that automates Google dork searches to identify potentially vulnerable web pages and applications. It consists of two main components: ghdb_scraper.py, which retrieves the latest Google dorks from the Google Hacking Database maintained by Offensive Security, and pagodo.py, which performs the actual searches using those dorks.

The tool solves the problem of manually executing Google dork queries through a web browser by automating the search process at scale. It uses the yagooglesearch library to perform flexible Google searches and supports both HTTP(S) and SOCKS5 proxies natively, allowing users to specify multiple proxies in round-robin fashion without requiring external tools like proxychains4. The ghdb_scraper component maintains a local cache of dorks organized by category, which can be refreshed to ensure searches use the latest available dorks.

Developers conducting security research, bug bounty hunting, or reconnaissance should consider this tool if they need to systematically search for exposed or misconfigured web applications. The tool is designed for Python 3.6 and later and can be used either as a command-line script or imported as a module for integration into larger workflows. The project explicitly notes that scraping Google Search results may violate Google's Terms of Service and recommends using Google's official API as the preferred method.

The project maintains an active codebase with regular updates to keep pace with changes to the Google Hacking Database. Development includes ongoing refinement of the proxy support implementation and migration to the more flexible yagooglesearch library. The tool includes comprehensive documentation for both script and module usage patterns, supporting multiple ways of interacting with the dork data and search functionality.