Google Dorking Explained — How to Search Like a Security Pro (With Tons of Examples)

Google Dorking Explained — How to Search Like a Security Pro (With Tons of Examples)

Derrk SamuelSeptember 12, 202612 min read
Google dorking turns ordinary Google searches into precision queries that cut through millions of irrelevant results. Learn what it is, every operator that matters, and dozens of copy-paste examples you can use today.

What Is Google Dorking?

Google dorking (also called Google hacking) is the practice of using Google's advanced search operators to find very specific information that a normal search would bury under millions of irrelevant results.

A "dork" is just a search query that uses special operators — like site:, filetype:, or intitle: — to tell Google exactly what you want, where you want it, and in what form. Google then filters its entire index down to results that match every condition you set.

The technique became famous in the security world when Johnny Long cataloged thousands of these queries into the Google Hacking Database (GHDB), showing that search engines had quietly indexed login portals, exposed documents, and even camera control panels that nobody meant to make public.

The core idea in one sentence: instead of asking Google "what pages mention X," you ask Google "show me only pages that contain X, in the title, on this specific site, in this file type, excluding everything else."

“The core idea in one sentence: instead of asking Google "what pages mention X," you ask Google "show me only pages that contain X, in the title, on this specific site, in this file type, excluding everything else."”

Share on X

Yes — searching is legal. You are only querying Google's public index, not breaking into anything. What matters is what you do with what you find:

  • ✅ Fine: dorking your own sites, researching publicly available info, OSINT investigations, authorized security assessments
  • ❌ Not fine: accessing files or systems you're not authorized to access, harvesting personal data, attacking endpoints you find

Finding an exposed door is not a crime. Walking through it is. If you discover a real security issue on someone else's site, the ethical move is to report it to the owner — not exploit it.


The Operators You Need to Know

Think of these as filters. Each one narrows the results, and they stack — the more you use, the sharper the result set.

site: — Restrict to One Domain

Only show results from a specific website.

site:web3tech.site docker

Finds every page on web3tech.site that mentions Docker. Use it without keywords to enumerate what Google has indexed for a domain:

site:web3tech.site

You can also exclude a subdomain by putting a minus in front:

site:web3tech.site -site:blog.web3tech.site

filetype: — Only One File Type

Returns results of a specific file format. This is one of the most powerful dorking operators.

filetype:pdf blockchain security

Common types: pdf, xlsx, docx, pptx, csv, txt, sql, log, conf, bak, env

intitle: — Keyword in the Page Title

Only pages whose title contains the keyword.

intitle:"admin login"

allintitle: requires every following word to appear in the title:

allintitle: install docker ubuntu

inurl: — Keyword in the URL

Only pages whose URL contains the keyword. Great for finding specific scripts, portals, or parameter-driven pages.

inurl:admin

intext: — Keyword in the Body Text

Only pages whose body content contains the keyword. This is roughly the default for normal searches, but it becomes powerful when combined with the others:

intext:"password reset" filetype:pdf

Pages that are linked to with the keyword as anchor text.

inanchor:"click here" site:example.com

cache: — Google's Cached Copy

Shows the last version of a page Google stored — useful when a page is down or has been changed.

cache:web3tech.site

Shows sites Google considers similar to the given one.

related:reddit.com

The Basic Search Tricks That Do the Heavy Lifting

You use these in every single dork, often without thinking of them as "operators."

Exact Phrase — Quotes

Quotes force Google to match the phrase word-for-word:

"the quick brown fox"

Exclude a Word — Minus

Removes results containing a term. Invaluable for killing noise:

jaguar -car -automobile

Logical OR — Uppercase OR

Matches either term (OR must be uppercase):

docker OR podman tutorial

Wildcard — Asterisk

Matches any word or words in a phrase:

"how to * a smart contract"

Range — Two Dots

Works on numbers, prices, and years:

laptop $500..$1000
ethereum 2023..2025

Time Filters — before: and after:

Limits results to pages published before/after a date:

kaspa miner review after:2026-01-01
windows 11 update issues before:2026-06-01

Copy-Paste Examples That Actually Work

This is the part you came for. Every query below is a building block — swap in your own domain, keyword, or file type.

Finding Login Portals and Admin Panels

intitle:"admin login" site:example.com
inurl:admin/login
inurl:wp-admin site:example.com
intitle:"index of" admin

Finding Exposed Documents

site:example.com filetype:pdf
site:example.com filetype:xlsx
site:example.com (filetype:docx OR filetype:doc)
site:example.com filetype:csv

Finding Exposed Config and Backup Files (Audit Your Own Site!)

These are the classic dorks security teams run against their own infrastructure:

site:example.com filetype:env
site:example.com filetype:log
site:example.com filetype:sql
site:example.com filetype:bak
site:example.com filetype:conf
site:example.com inurl:backup

If any of these return results on YOUR domain, that's a finding worth fixing. Exposed .env files usually contain database credentials and API keys — they should never be served by your web server.

“If any of these return results on YOUR domain, that's a finding worth fixing. Exposed .env files usually contain database credentials and API keys — they should never be served by your web server.”

Share on X

Finding Directory Listings

When a web server has no index page, it shows a raw file listing titled "Index of /":

intitle:"index of" site:example.com
intitle:"index of" backup
intitle:"index of" /wallet

Research and OSINT on a Person or Company

"John Smith" ("resume" OR "CV") filetype:pdf
site:linkedin.com/in "software engineer" "blockchain"
"Acme Corp" (email OR contact) filetype:pdf

Finding Presentations and Slides

filetype:pptx "security audit"
site:slideshare.net intitle:ethereum

Finding Error and Log Text Leaked on Pages

intext:"sql syntax error" site:example.com
intext:"warning: mysql_connect" -site:stackoverflow.com

Finding Old or Forgotten Subdomains

site:*.example.com -site:www.example.com
site:example.com -www

Narrowing by Date and Type Together

site:example.com filetype:pdf after:2025-01-01
"zero day" site:thehackernews.com after:2026-08-01

Combining Operators — How Real Dorks Are Built

Single operators are toys. Power comes from stacking. The mental model:

  1. Where? — site:
  2. What form? — filetype:, inurl:, intitle:
  3. What content? — intext:, quoted phrases
  4. What noise? — minus terms

Build it one filter at a time, checking results between steps.

Example: find confidential PDFs on your own company site that shouldn't be public

site:example.com filetype:pdf (confidential OR internal OR private)

Example: find staging/test environments exposed to the index

site:example.com (inurl:staging OR inurl:dev OR inurl:test)

Example: find open FTP-style directory indexes serving video files

intitle:"index of" (mp4 OR mkv) -site:youtube.com

Example: research a competitor's public documentation

site:competitor.com filetype:pdf (api OR integration OR guide)

The Google Hacking Database (GHDB)

You don't have to invent dorks from scratch. The Google Hacking Database at exploit-db.com/google-hacking-database catalogs thousands of categorized, working dorks — from finding exposed printers and cameras to specific software misconfigurations.

Browse it by category, test the queries against your own assets, and treat every hit as a to-do item for your security team.


How to Defend Against Dorking (The Other Side)

If you run a website, assume people are dorking your domain right now. Here's the defensive checklist:

RiskDefense
Exposed config/backup filesNever serve .env, .sql, .bak files; block them in your web server config
Directory listingsDisable autoindexing (Options -Indexes in Apache, autoindex off in Nginx)
Sensitive pages in the indexUse robots.txt plus authentication — robots.txt alone just advertises the URL
Stale indexed contentUse the Google Search Console removal tool and return proper 404/410 status codes
Login portals easily foundDon't name your admin path /admin; restrict by IP or VPN
Documents you forgot aboutPeriodically run the dorks in this guide against your own domain

robots.txt is not security. It's a polite request that also acts as a roadmap for anyone curious. Anything genuinely sensitive needs authentication — not obscurity.

“robots.txt is not security. It's a polite request that also acts as a roadmap for anyone curious. Anything genuinely sensitive needs authentication — not obscurity.”

Share on X

Quick Reference Cheat Sheet

GoalDork
One site onlysite:example.com
One file typefiletype:pdf
Keyword in titleintitle:login
All words in titleallintitle: install docker ubuntu
Keyword in URLinurl:admin
Keyword in bodyintext:password
Anchor textinanchor:click here
Google's cached copycache:example.com
Similar sitesrelated:example.com
Exact phrase"exact words"
Exclude a word-car
Either/ordocker OR podman
Any word in a phrase"how to * linux"
Number/price range$500..$1000
After a dateafter:2026-01-01
Before a datebefore:2026-06-01

The Bottom Line

Google dorking isn't hacking — it's searching with intent. The same index that serves recipe blogs also holds exposed login portals, forgotten config files, and directory listings that organizations never meant to publish. Operators like site:, filetype:, inurl:, and intitle: are simply how you ask Google for exactly that.

Learn the operators, stack them one filter at a time, run them against your own domains before someone else does — and if you find something that shouldn't be public on a site you don't own, do the right thing and report it.

Also featured on TechDerks Insights

I write more takes like this one on my second blog — blockchain deep dives, security breakdowns, and builder tools.

Read more on TechDerks Insights
D

Derrk Samuel

Web3, crypto, and Linux PC insights — practical guides, security tips, mining setups, blockchain tools, and decentralized tech strategies for techs.

Discussion

Leave a comment

No comments yet. Be the first to start the discussion!