ALLINURL:
If you start a query with [allinurl:], Google will restrict the results to those with all of the query words in the url. For instance, [allinurl: google search] will return only documents that have both "google” and "search” in the url.
Note that [allinurl:] works on words, not url components. In particular, it ignores punctuation. Thus, [allinurl: foo/bar] will restrict the results to page with the words "foo” and "bar” in the url, but won’t require that they be separated by a slash within that url, that they be adjacent, or that they be in that particular word order. There is currently no way to enforce these constraints.
INURL:
If you include [inurl: ] in your query, Google will restrict the results to documents containing that word in the url. For instance, [inurl:google search] will return documents that mention the word "google” in their url, and mention the word "search” anywhere in the document (url or no). Note there can be no space between the "inurl:” and the following word.
Putting "inurl:” in front of every word in your query is equivalent to putting "allinurl:” at the front of your query: [inurl:google inurl:search] is the same as [allinurl: google search].
Let’s find some sites which may vulnerable for sql injections,
inurl:index.php?id=
inurl:trainers.php?id=
inurl:article.php?ID=
inurl:buy.php?category=
phonebook: from this dork u can search any persons phone details google have its own phone database if the ph no is in that database then u can problably find the ph no
|