DorkingDB
1.0.0
Operator ""
According to Google's translation: "Contains the following complete keywords". According to personal limited research it can return results which include only a subset of the specified strings. The spaces between strings can be replaced with anything. The sequence is not always preserved.
Try googling baiding "aaa bbb ccc" or smth similar. The operator might work better for Chinese queries.
Operator |
Logical OR. Eg (foo | bar).
Operator -
Used for exclusion. Eg -site:www.dont-open-me-i-might-be-dangerous.com to exclude from results.
Operator ()
Used for grouping.
Operator site:
It has the same purpose as in most other engines. The official page does not include a space between this operator and searched str, though it seems to work fine with space(s). The * seems to produce slightly different results. Subdomains are also returned if no * is provided.
Operator title:
It is like intitle in Google. The official page does include a space between operator and the searched title. It also places the title between round brackets. It seems to work fine without space(s) and without braces.
Operator inurl:
The official page includes a space between operator and the searched url. It also places the url between round brackets. It seems to work fine without space(s) and without braces.
Operator filetype:
Searches for the specified file extensions. Currently supported: pdf, doc, xls, ppt, rtf, all. Others seem to be unreliable. There must be no space between operator and extension.
Operator filetype:
The official site states that it supports only these extensions: pdf, doc(x), xls(x), ppt(x), html.
The personal research has shown that it can also return results for other file types (eg txt, zip).
It looks like if it does not find anything relevant, it tries to return smth similar. For instance if you are looking for txt, the engine might send you some json results.
General info:
Operator site:
Searches in subdomains even if only 2nd level domain and TLD are provided.
The space between colon and host name plays a role:
The * wildcard is supported:
Operator filetype:
Returns results based on content rather than file extension.
If it does not find anything relevant it might suggest you smth similar:
site:2ndld.tld filetype:pps => Showing results for site:2ndld.tld filetype:ppt
Operator ext:
Returns results based on extension rather than file content.
If it does not find anything relevant it might suggest you smth similar:
site:2ndld.tld ext:xlsm => Showing results for site:2ndld.tld ext:xlsx
It looks like it not only tries to find a similar extension, but also uses the operator itself to find "similar" results:
site:2ndld.tld ext:action => Showing results for site:2ndld.tld extraction
Operator intitle:
Put compound strings into quotes for better results (eg intitle:"some good title" instead of intitle:some good title).
General info:
Operator site:
Does not accept * wildcard (neither in subdomains nor in path). Searches in subdomains: Eg site:google.com would return www.google.com, support.google.com, etc.
Operator filetype:
Returns results for at least some extensions (eg pdf, txt, zip). It either does not recognize or blocks requests for some extensions (eg csv).
Operator intitle:
Put compound strings into quotes for better results (eg intitle:"some good title" instead of intitle:some good title). Seems to search for related strings (eg can add/replace delimeters). Sometimes returns unrelated results.
Operator site:
Does not accept * wildcard in subdomains. If added in path, then used as is. Searches in subdomains: Eg site:google.com would return account.google.com, support.google.com, etc.
Operator filetype:
Unreliable in general. Returns results for at least some extensions (eg txt, pdf). It either does not recognize or blocks requests for some extensions (eg csv). It looks like it checks the content rather than file extension.
MIT ©️
