Hello again! In this post, I’m going to go over an extremely
useful technique security experts often use to gather
information and uncover unintentionally exposed resources
by leveraging the power of Google.
This technique is known as Google Dorking. A Google Dork is
a search query that uses Google’s advanced query syntax to
boost the effectiveness of a normal search.
Even if you’re not security-oriented, these techniques can be
extremely useful in your daily Googling life. So, let’s get
Before we get into some juicy examples, let’s make sense
of some of the most useful query strings. I’m only going
to go over some common ones, but you can take a look
at this article
for information on all 42 of them.
The basic syntax of an advanced Google query is as follows:
search term [query-parameter]:[value]
You can chain as many query parameters as you want together
to make for some complex search results.
In addition to this, Google allows you to chain search results by the
For example, if I wanted to look up the results of pages that included
information about both dogs and cats I could search for:
dogs AND cats
And these queries can be chained together and mixed intermittently
offering flexibility and power.
If you want to limit your searches to exact matches, you can optionally
add double quotes to your query.
For example, If I wanted to pull pages that contained the phrase,
Squirtle is cool exactly, I could search:
"Squirtle is cool"
It is also important to remember that query parameters are delimited by
spaces. So, if you wanted to search for pages titled “Index of,” you would
have to search
The former would search for pages that had “Index” in their title
and matches for “of.”
Now, let’s get into some important parameters that could make for some
pretty powerful search results.
site parameter limits results to a specific domain. So,
if I wanted to limit my searches to facebook.com, I would type:
This can be used to find possible vulnerabilities in a specific company,
or limit results about a target to social media sites.
inurl is pretty self-explanatory: it pulls matches based on
what is in the url of the result. If I wanted to pull up admin
pages that might be publicly available, I could search:
This is useful for providing URL matches rather than matches in the
This parameter is used to restrict results based on filetype. For
example, if I wanted to search for pdf files, I could search:
This is an especially powerful parameter as log files as well as
configuration files can be scraped using this parameter.
intext allows you to specify matches in the body of a page.
The body of the page is anything rendered between HTML tags. For
example, if I wanted to search for blog articles that were about
pokemon, I could search:
These are only some of the key query parameters allowed by Google, but
as you could imagine, they could be combined in clever ways that can
yield powerful results.
Now it’s time for some juicy examples! There are tons of common Google Dorks
out there that expose common info and of course, you can combine them with
your own custom Dork to find some interesting things. You’d be surprised by
what people can leave exposed to the internet. So, let’s get to the examples!
intext:"index of" ".sql"
This Dork string can be used to find SQL database files in directories
that are traversable. This can potentially expose a number of database
files that you can download and look through on your own machine.
No bueno for people that have this exposed as it can contain user information
or other private information.
This Dork can be used to connect to online devices, such as live-streaming webcams. Many webcams are intentionally made to be public, but some might not be.
If you’re a creep, this can be perfect for you!
Using this Dork, you can find default login portals. Oftentimes, login portals
that are unintentionally exposed will be using default credentials. So, this Dork
can be used to find potentially vulnerable sites. Use at your own discretion!
These are only a few of the many powerful Dorks out there. Exploit DB’s
Google Hacking Database
has loads of other examples, so I encourage you to experiment with these and
combine them with your own Dorks.
Obviously, it goes without saying that you can stumble upon private information
and vulnerabilities. So, look don’t touch! It’s best to contact site owners
to make them aware of this information. But DO NOT do anything illegal
(it’s only illegal if you get caught *wink-wink*).
Anyways, that’s it for this security tutorial. More coming soon!