OSINT Jet field notes · Search skills

Google Dorks: a practical guide to advanced search

Google dorking means combining search terms with operators to find a more specific set of indexed pages. For OSINT, the useful outcome is an original document or a checkable source, followed by a careful evidence note. You do not need an exploit or a secret database to practise it.

Published 7 September 2026 · By OSINT Jet Editorial Team · Three browser queries checked on the publication date.

Start with a small set of operators

These examples target public documentation. Replace the subject to answer your own research question. Keep the operator attached to its value, and use ordinary straight quotation marks. The syntax below follows Google’s search help.

On a small screen, scroll the table sideways.

For terms in a title or URL, use the “terms appearing” control in Google Advanced Search. You may also encounter intitle: and inurl: in dork lists; do not assume every copied recipe remains reliable. The form is a useful way to express the intended restriction explicitly.

A tested example: find the source, then inspect the query

We ran the following three searches in a desktop Google browser session on 7 September 2026. This is a small, dated observation, not a ranking benchmark or a promise that every reader will see the same results.

1. Find the primary explanation

site:iana.org "Example Domains"

The results included IANA’s Example Domains page. Reading that page establishes the intended documentation use of example.org. A search snippet alone would be an incomplete evidence record: save the source URL and read the page before summarizing it.

2. Notice when the requested match was not found

site:iana.org filetype:pdf "annual report"

In our check, Google said it had no results for the exact query and displayed broader results without the quoted phrase. Some were PDFs. Recording those as exact “annual report” matches would have been a mistake. The absence of an exact match did not establish that IANA had never published such a document.

3. Relax one assumption and inspect the candidates

site:iana.org/reports/ filetype:pdf

This returned PDF candidates under the reports path, including survey documents. We changed the search task from “find this exact phrase” to “discover documents in this area.” Keep that change in the notes. A candidate still needs review: identify its title, publisher, coverage period and relevant passage.

Turn a result into a reproducible evidence note

Question: What is example.org intended for?
Query: site:iana.org "Example Domains"
Source: https://www.iana.org/help/example-domains
Retrieved: 2026-09-07; record your own UTC time when repeating
Observation: IANA describes documentation use.
Supported conclusion: it is an IANA documentation domain.
Not established: ownership or trustworthiness of another site.
Next step: inspect the original record required by the question.

When a page matters, preserve the relevant text or a permitted copy with its retrieval time. Keep a quotation separate from your own summary. The evidence-hash exercise helps you detect later changes to a saved text; it does not certify its accuracy.

What a Google dork cannot establish

• A complete inventory. Google explains that site: results are not exhaustive. No result is not proof that a page or fact does not exist.
• The date of an event. A search date filter is a retrieval aid. Check the document’s issue date, revision date and the period it discusses separately.
• Independent confirmation. Two mirrors of one report are not two independent reports. Follow attribution back to the origin.
• Identity or permission. A matching name is a lead, and search visibility does not grant permission to enter an account or redistribute personal information.

A quick troubleshooting order

1. Check spelling, ordinary quotation marks and spaces after operators.
2. Check the intended domain and path: a narrow path can exclude the document you need.
3. Remove one restriction at a time; record the revised query.
4. Look for a message about omitted terms or broader results.
5. Use the publisher’s own archive or navigation if search remains inconclusive.

Build the next part of the investigation

For choosing a resource, follow the OSINT Framework walkthrough. For interpreting records rather than search results, try the worked domain case. The OSINT learning path combines these skills with source evaluation.

Method: three manual browser searches; official documentation checked; no exhaustive operator benchmark. Request a correction.