Google regex system
Now this may be confusing. And trust me it should be. I’ve reused data from earlier with some minor adjustments to make it completely accurate. The reason I’ve done this is we need to start somewhere. And it’s certainly not going to be at the complete top, so you lose context of how things work. In my experience I’ve been able to utilize the Google Regex in almost every Dork I currently produce, with few exceptions of certain methods of targeting sites.
The Google Regex System is comprising of characters with plenty of use that can change, alter, optimize, randomize and other unique features for Dorks. It’s an important tool to preserve the quality of Dorks that obtain unique results, and it should be used with an understanding of purpose. It’s vital to understand the usage of these in order to get the
best results possible out of them.
Matches any single character (letter, number or symbol)
Usage: 1. Result : 10, 1A
Matches proceeding character 0 or 1 times
Usage: hi? Result: h, his, hi and etc
Matches the preceding character 1 or more times
Usage: 10+ Results: 10, 100
Matches the preceding character 0 or more times
Usage: 1* Results: 1, 10
Creates an OR match Do not use at the end of an expression
E.g: 1|10 Results: 1, 10
Matches the enclosed characters in exact order anywhere in a string Also used to group other expressions
10) matches 10, 101, 1011 any number or lower-case letter
Matches the enclosed characters in any order anywhere in a string
 matches 012, 123, 202, 120, 210
Creates a range of characters within brackets to match anywhere in a string. Or avoids targeting.
[0-9] matches any number 0 through 9
The way we would use GRS is by already including Search Operators or Search Functions.
E.g. Shopping + Cart .php?cartID=
Now, we have our Search Operator +
There are many ways we can edit this Dork to include
GRS.Shopping + Cart .php ?cartID=[0-10]
We’re now targeting a method we will explain further in the book called Numeric Dorks. Fix, just add a random number anywhere in the Dork except the parameter or in search functions to reduce the chance of invalidating the Dork. Enjoy!
All that you need to know about that method is that, almost every single tutorial you have ever seen before was wrong. And I can’t explain it shortly here.
E.g. 2 Shopping + Cart \ purchase .php ?cartID=
In this example I have exited the query stringing from the + operator. This usage has made, Shopping Cart become a target and purchase being a separate string. I’ve also added a space between .php and the parameter. This is to avoid over intense targeting. I’ve also used a backslash before the =, a perfect example of taking the next character literally, this is important because Google has their own Regex for their own parameters for each user, including their images and search data that is referenced the same as any other site using Get. By using the backslash we’ve told Google to use this next character literally instead of a Google Parameter. Patched and I’m mad. Separating each part of the query is completed with a backslash
with a space before it. Meaning you can do anything after that first space backslash ‘ \
This is extremely useful and I use it in almost every Dork.
E.g 2a (“Shopping” + cart) \ ext:php \ inurl:?cartID=
Screwed: You can now separate the importance of each section of the query with backslashes to expand the search query. This was a recent development from the Google Update. This allows for unique results and is extremely useful.
E.g. 2a (patched…)
(“Shopping” + cart) ext:php inurl:?cartID\=
Screwed: You can no longer target specific characters because Google patched it.
E.g. 3 Base Dork
Shoe + Shop .php
Shoe? + Shop .php ?cartID=
This Dork will be used if you’re using a keyword that you KNOW for a FACT can be commonly replaced with that word with an “ed” or “s” on the end. (or any other extension) This will allow you to find those results as well. Expanding your target range.
Advanced Explanation and Usage for GRS
Now a big part of this book is teaching you how these Dorking solutions actually achieve results. Now it’s a reasonable time to explain most of these Regex Options. Now our best place to start is the order I’ve listed them all in.
Wildcards are our way to expand our search results, avoiding our failed Dorks while generating or mistargeting. Human Error is a large concern for Dorking. Whether it’s been from the Dorker (us) or other users of the internet (BOOMERS). So, it’s vital to optimize ourchances of success. In this following section of the book I will be explaining each wildcard and usage.
Our period is a useful tool when targeting a numeric target or a string of characters towards a subject. Whether your target be for a game, event, year. Anything like this can be optimized to assist to randomize that result to be anything.
Zelda Event 201.
This usage of the period will now target results with 201[SOMETHING] Results can give you a year, a number of an item or anything in this usage technique.
Usage of a Question Mark can assist in the reverse searching for context and stringed keywords or something else.
?games events London
In this context, characters before games could be linked to the word, could be strung together in a phrase or simply be in the URL: top-ps4-games
games? events London
In this context, the “s” on the end of game will be non-required when scanning through sites, I’m unsure of the extent this is capable in Google.
The potential uses of this operator are flexible. Being able to complete multiple tasks, either adding a dynamic random character to the end of a specific word or by linking multiple words to be together or as a priority in the search query itself.
How to multithread in C# with 10+ at the same time This usage of the operator will now search for queries of 10 with another character after it, being a number or letter. Either way can assist in searching legal documents or just attempting to expand the search boundaries.
Game + popular events
This use of the operator will result in stringing both queries together, Google has a hidden way of completing this as it’s a rather complex algorithm they’ve developed but it’s a very
useful and commonly used practice by Dorkers.
Usage that follows this operator is similar to the previous but instead of colliding the queries but can also randomize the results, with an increase to the beginning or the end of a numeric query or just randomize the strings in the query.
How to multithread in C# with 10* at the same time
Result is simply just randomizing that next character, also and most commonly used is to put it before and to randomize the figures after that number / query as well.
*Game popular events
This will simply just make all characters following that word be randomized. But with Google sometimes it can do it for the entire query, so please be sure to use some of the operators I
will be explaining further on to solve syntax mistakes.
This operator means, OR, which means it will choose one or the other. This is the same syntax usage of “+”.
Game | popular events
Meaning, “Game OR popular events”
This is not an overly used operator. I won’t spend time explaining this Regex groups are how we can organise our search queries within a query to achieve searching for multiple pieces of information in a singular query. We can also use Wildcards to assist the accuracy of these searches, increase the diversity and improve the results. Now this is what really makes
the advanced Dorkers good at what they do.
Parenthesis are a useful tool to increase priority in searching or link queries together. I personally use these most commonly in searching. It’s a vital component when linking multiple queries together and making them a priority along side your Search Functions and other Regex Usages.
(Gaming Shops Local) ext:php
This usage is linking the entire phrase / query into a priority queue, instead of Google searching for each independent word, instead it will now attempt to find these words strung
together, or close to it. Be aware that once you incorporate Search Operators / Wildcards you will be drastically optimizing your Dorks to complete multiple tasks at the same time. You will be making Google process multiple requests, also improving the accuracy of your search.
Data arrays, for anyone who’s been a developer or participated in the numeration techniques of coding. Will know that arrays are pieces of data of which can be called, and
then find a certain entry to that array and use that data, as a static piece of information. We can use this to randomize our searches with numeric orders or to simply incorporate
random characters into the search. Be aware Google’s array inputs each unique character as a separate entry to the array. No commas to be required and adding them may even
corrupt the search intent.
This operator is used inside of the Data array in the previous explanation. This is just to define the distance between two characters. Like when counting, instead of putting 1, 2,3,etc into the array. Simply putting the starting number followed by this operator and then the finishing number to have it automatically targeted. Can also be used to avoid targets. Such as github.com. But it isn’t much of a concern for us and will waste our space for a query.
Breaking Regex & Syntax
n the event that you will use an operator, function, or regex. You will need to separate it from the remainder of the search or ones prior. The best way to do this and the only way to do this is
to use a backslash. \. This is pretty straight forward. Either use it connected to something you want to target or use it with spaces to separate different parts (strings) of the search. This
singular operator is how to make your Dorks become some of the highest quality you could imagine. It makes targeting so much more precise and controllable and it is my number
one MOST IMPORTANT method to improving Dorks.
That’s all you need to know to be at the top of your Dorking game. No exaggeration, no bullshit,notime wasting. If you understand everything above. YOU CAN OFFICIALLY DORK. And
not only can you Dork. You can understand why things will work.
After recent Screwed it’s also capable by a space on search operators and functions, but it’s still recommended to use backlash in the event of a complex situation.