Google Dorks Cheatsheet

Contents
Contents
TL;DR
- Google operators like
site:,inurl:,filetype:,intitle:,intext:,before:/after:andAROUND(x)still work in October 2026, though Google shows fewer raw results and now mixes AI Overviews into the page. - The Google Hacking Database (GHDB) at exploit-db.com is still the go-to collection of dorks for finding exposed services and files.
- Bing, DuckDuckGo, Yahoo and Yandex honor similar operators, so don’t stop at one engine.
- Finding exposed data on servers you don’t own without permission is illegal. Practice in your own lab and report what you find responsibly.
Introduction
This post was originally published in October 2020 and updated in October 2026.
You can download the cheatsheet as a PDF: dorks cheatsheet!
Searching in Google has become something as normal as drinking water and sometimes we desperately search some information but we can’t find it, neither in other languages. Doing advanced searches with the use of Google Operators nowadays is a must to be able to extend and improve our findings. From searching for a specific filetype such a pdf or a png image, to use it for hacking and bug bounty!
A quick honesty note for this update: Google has tightened how many results it shows and now merges AI Overviews into the results page, so a query that used to return pages of hits may now give you a short list plus a summary. I haven’t re-tested every operator below for this update, so treat them as tools that Google keeps reshaping, not a stable API. And if Google comes up short, Bing, DuckDuckGo, Yahoo and Yandex honor similar operators, so try the same dork there.
Operators
Mixing these operators will let us customize our search to the point of having neat results. In any case, it’s best to try them yourself so that you learn them and get comfortable using them in a normal basis. Believe me, a good search will save you lots of time!
I’ve found some more but the result is nearly the same as a normal search, so I decided not to include them. In any case, if you know some that really makes a difference contact me and I’ll add them!
Two doors have closed since the original post: info: was retired years ago, imagesize: no longer filters results as documented, and Google removed its cached pages feature in 2024, so cache: is gone from the table too instead of pretending they still work. If you want exact-size images, search normally and use the image search tools instead.
Restrict Search
| Operators | Example | Meaning |
|---|---|---|
| " " | “Tres tristes tigres” | Search will only show results that exactly match “Tres tristes tigres” |
| OR | trump OR biden | Shows pages that either contains “trump” or contains “biden” |
| AND | trump AND biden | Shows pages that contains “trump” and “biden”. Not much difference with a normal search |
| () | (razer OR logitech) mouse | Groups multiple operators for a better search |
| - | elon musk -twitter.com | Will search Elon Musk but Twitter pages won’t appear |
| * | index of * | Acts as a wildcard, matching anything |
| #..# | 2006..2008 | Will search the range [2006, 2007, 2008] |
| AROUND(x) | index of AROUND(3) cgi-bin | Will match pages that has 3 words at max of distance between “index of” and “cgi-bin” (read: as of the update, it doesn’t always filter as strictly as it used to) |
| site: | site:twitter.com | Search results are restricted to Twitter.com page |
| filetype: | filetype:pdf | Search results will only include pdf files |
| intitle: | intitle:cibersecurity | Pages that include “cibersecurity” in the title |
| allintitle: | allintitle: OSCP guide | Pages with “OSCP” and “guide” in the title |
| inurl: | inurl:deer | Pages that contain “deer” in the URL |
| allinurl: | allinurl:code python | Pages that contain “code” and “python” in the URL |
| intext: | intext:deer | Pages that contain “deer” in the text |
| allintext: | allintext:code python | Pages that contain “code” and “python” in the text |
| before: | cors before:2024-01-01 | Pages published before the given date |
| after: | cors after:2026-01-01 | Pages published after the given date |
| related: | related:aliexpress.com | Pages that are similar to Aliexpress (read: Google sunset related: results around 2023, so treat this one as unreliable now) |
Common
| Operators | Example | Meaning |
|---|---|---|
| stocks: | stocks:amz | Show the stock value of Amazon |
| define: | define:book | Searches definitions of “book” |
| movie: | movie: patria | Searches info. about “Patria” serie’s |
Maths
| Operators | Usage | Result |
|---|---|---|
| + | 5 + 10 | 15 |
| – | 5 - 10 | -5 |
| * | 5 * 10 | 50 |
| / | 5 / 10 | 0.5 |
% of | 10% of 300 | 30 |
| ^ | 5^2 | 25 |
| ** | 5**2 | 25 |
Use of dorks for hacking
I found some pages full of examples in which they mix operators with default service/application behaviour so it ends up with an insecure open service that could be exploited. This is very very useful in bug bounties!
The GHDB at exploit-db.com is still alive and kicking six years later, and it remains the best single place to browse community-submitted dorks by category. Some trivia worth knowing from its own about page: “Google Hacking” was popularized by Johnny Long around the year 2000, he passed the database to OffSec in 2010, and it has been curated there ever since. Today it indexes queries for other engines too, like Bing. The categories map neatly onto what you actually meet on a pentest, from Footholds and Sensitive Directories to Pages Containing Login Portals and the eternal Various Online Devices (a personal favorite, if only for the name). One heads-up from 2026: there’s also a whole separate ecosystem for finding open devices and services, the Shodan-style tools that index ports and banners directly instead of web pages. They complement dorks without replacing them, since each sees a different slice of the internet.
Caution: running dorks and finding exposed data on servers that aren’t yours is not a game. Accessing someone else’s systems or data without authorization is illegal in most countries, no matter how easy the dork made it. If you stumble on something exposed, don’t poke further; report it to the owner through responsible disclosure (their security.txt, a bug bounty program, or a direct contact). Want to practice safely? Spin up your own lab: a local VM or a deliberately vulnerable machine you own, with the same services exposed on purpose.
My advice after six years is the same as it ever was: learn the operators by heart, mix them constantly, and practice on your own machines first. The cheatsheet pdf is a great companion to keep nearby, and the GHDB will keep you stocked with fresh dork ideas. Got a favorite dork I should add to the list? Reach out and I’ll add it!