🔍 Google Dorking: Hacking with Google

"Google is your best friend... if you know how to ask."

📖 What is Google Dorking?

Google Dorking (or Google Hacking) is an advanced technique used to refine Google searches using specific operators to uncover hidden or sensitive information exposed on the web. This method is widely used in:

Penetration Testing
Security Auditing
Open Source Intelligence (OSINT)
Bug Bounty Programs

It allows researchers to identify misconfigured servers, inadvertently shared documents, exposed credentials, and more — all indexed by Google's powerful search engine.

🧠 How Does It Work?

Google supports a series of search operators that can be used in combination to uncover very specific results. These advanced queries go beyond normal searches to extract deeply buried content.

🔍 Common Search Operators

Operator	Description	Example
`site:`	Limits search results to a specific domain	`site:example.com`
`filetype:`	Finds specific file types	`filetype:pdf`
`intitle:`	Looks for keywords in the page title	`intitle:"index of"`
`inurl:`	Searches for keywords in the URL	`inurl:admin`
`cache:`	Displays Google’s cached version of a page	`cache:example.com`
`ext:`	Alias for `filetype:`	`ext:xls`
`intext:`	Finds text within the page body	`intext:"password"`
`allintitle:`	Finds all terms in the title	`allintitle:login page`
`allinurl:`	Finds all terms in the URL	`allinurl:dashboard admin`
`AROUND(X)`	Searches terms within X words of each other	`"login" AROUND(5) "admin"`

🧪 Practical Examples

⚠️ Warning: These examples are for educational use only. Do not attempt unauthorized scanning or access.

🔐 Admin Login Panels

intitle:"admin login"
inurl:adminlogin
site:example.com inurl:admin

🗂️ Exposed Directories

intitle:"index of /" site:example.com
intitle:"index of" "parent directory"
intitle:"index of" passwd

📄 Publicly Available Documents

filetype:pdf site:gov confidential
filetype:xls intext:"ssn"
filetype:doc "internal use only"
filetype:log password

🔑 Credential Leaks

intext:"DB_PASSWORD" filetype:env
filetype:config intext:"password"
ext:ini intext:"root"

📷 Live Webcams

inurl:"MultiCameraFrame?Mode=Motion"

VB Viewer inurl:/viewer/live/ja/live.html

inurl:control/camerainfo

intitle:"webcamXP 5" -download

inurl:"/view/view.shtml?id="

inurl:/view/viewer_index.shtml

intext:"powered by webcamXP 5"

intitle:"webcam 7" inurl:"8080" -intext:"8080"

intitle:"Live View /- AXIS" |inurl:view/view.shtml OR inurl:view/indexFrame.shtml |intitle:"MJPG Live Demo" |intext:"Select preset position"

🧾 Log Files and Backups

filetype:log inurl:"/logs/"
intitle:"index of" backup
ext:bak | ext:old | ext:backup

🔍 SQL Dumps

filetype:sql "insert into"
filetype:sql password

🎯 Use Cases

🔎 OSINT Investigations: Collect public-facing data about targets.
🔐 Pentesting: Identify common security misconfigurations and leaks.
🧰 DevSecOps: Detect exposed files before they become vulnerabilities.
📢 Bug Bounties: Locate asset exposures for responsible disclosure.

🔒 Defensive Measures

✅ Best Practices

Implement robots.txt

User-agent: *
Disallow: /admin/
Disallow: /config/
Disallow: /private/

Restrict File Indexing
- Disable auto-indexing on web servers (Options -Indexes in Apache).
- Use .htaccess rules for directory protection.
Authentication and Authorization
- Protect sensitive areas with login prompts and role-based access.
Remove Sensitive Metadata
- Strip metadata from files before uploading them to the web.
Monitor and Audit
- Regularly search your own domains using dorks.
- Set up Google Alerts to watch for unusual mentions.
Use Web Application Firewalls
- Tools like Cloudflare or ModSecurity can block suspicious bot access.

🧰 Recommended Tools & Resources

📘 Google Hacking Database (GHDB)
🌐 Shodan
📡 Censys
🕵️ Recon-ng
🧠 theHarvester
⚠️ FOCA - Metadata analysis tool

📌 Real-World Incidents

Google Dorking has been involved in notable data exposure cases including:

Government documents made searchable by misconfigured CMS platforms.
Exposed credentials on development subdomains.
Backup files containing API keys accidentally stored in web root folders.

These incidents underline the importance of regular asset auditing and secure development practices.

🧑‍🏫 Educational Purpose Only

This repository and its content are intended for educational and ethical cybersecurity research only.

Never use Google Dorking for unauthorized access, data theft, or malicious activities. Violating privacy or security laws may result in criminal prosecution.

Always obtain explicit permission before scanning or analyzing any system not owned by you.

🤝 Contributing

Do you have more useful dorks, techniques, or tools? Open an issue or submit a pull request. Contributions are welcome from the community!

📚 License

This project is licensed under the MIT License. See the LICENSE file for more information.

michele-tn/Google Dorking: Hacking with Google.md