Google Dorking for Investigators: Advanced Search Operators

Google dorking is the practice of using advanced search operators to retrieve specific, targeted information from Google’s index that a standard keyword search would never surface — including cached pages, exposed files, specific file types, site-restricted results, and information buried in documents that aren’t linked from any visible page.

Quick Answer: Google dorking uses operators like site:, filetype:, intitle:, inurl:, and "exact phrase" to filter Google’s index with surgical precision. For investigators, it surfaces court documents, cached profiles, leaked spreadsheets, historical page versions, and people-search results that standard searches miss entirely. The most powerful technique is combining multiple operators in a single query — each additional operator narrows results to exactly what you’re looking for.

Dorking in one sentence: Google has indexed far more than what appears in a standard search — operators are the keys that unlock the rest of it.

Google dorking requires no tools, no accounts, no subscriptions, and no technical background. It works in any browser, on any device, using only Google’s own search interface. The only requirement is knowing which operators exist and how to combine them.

⚠️ Legal Notice: Google dorking searches publicly indexed information only. Accessing systems, files, or data that requires authentication — even if you discover the URL through a dork — may violate the Computer Fraud and Abuse Act (18 U.S.C. § 1030). This guide covers lawful research using publicly available indexed information only and does not constitute legal advice.


On This Page

Why This Guide Is Reliable

inet-investigation.com publishes research-based guides built on primary government sources, investigative practice, and public records law. This article is part of the OSINT series and connects directly to Phase 3 (initial search) and Phase 4 (pivoting) of the 8-Phase OSINT Investigation Framework.


Where This Guide Fits

This article covers a specific technique within the broader OSINT workflow. For context on where dorking sits in a complete investigation:

  • Phase 3 — Initial Search: Dorking is the most powerful free tool in the initial search phase — a well-constructed dork can surface more relevant results in one query than ten standard searches.
  • Phase 4 — Pivoting: Every result a dork returns becomes a new identifier to pivot from — a name, an email, an address, a case number.

→ For the complete investigation framework: [OSINT Workflow: The 8-Phase Investigation Framework — inet-investigation.com] → For what to do with what dorking finds: [OSINT Pivoting: How to Follow Data Connections — inet-investigation.com]


Why Standard Search Misses So Much

Google’s standard search is designed to return what most people want most of the time — popular pages, recently updated content, heavily linked results. That design systematically buries:

Specific file types. PDFs, spreadsheets, Word documents, and PowerPoint presentations are indexed but rarely surface in standard keyword searches, even when they contain exactly what you’re looking for.

Deep archive pages. Pages with few or no inbound links — internal organization directories, old staff pages, archived meeting minutes — are indexed but rank so low they’re effectively invisible.

Site-specific content. A standard search for a person’s name might return their LinkedIn profile and a news article. A site-specific dork of a court portal, a government database, or a specific organization’s website returns only that site’s indexed content.

Exact string matches. Standard search applies stemming, synonym expansion, and relevance modeling that disperses results. Quoted exact-phrase searches force Google to return only pages containing that precise string.

Cached and historical versions. The live version of a page may have been edited or deleted. Google’s cache often preserves an earlier version.

Dorking bypasses all of these limitations by telling Google’s index exactly what to retrieve, from where, in what format.


The Core Operators

" " — Exact Phrase

Forces Google to return only pages containing that exact string in that exact order.

"John Smith" "Phoenix Arizona"
"[email protected]"
"123 Main Street" "Austin Texas"

Investigative use: Locks down results to a specific person, address, or contact detail. Without quotes, Google expands the search and returns millions of loosely related results. With quotes, results contain exactly that string.

Combined use: Quotation marks are the foundation of almost every useful dork. Every other operator works better when combined with exact-phrase strings.


site: — Restrict to a Specific Domain

Returns only results from the specified domain or subdomain.

site:linkedin.com "John Smith" "Phoenix"
site:pacer.gov "Marcus Webb"
site:sec.gov "Apex Financial Group"
site:courts.state.tx.us "David Torres"

Investigative use: Searches a specific record system, social platform, or government portal directly through Google rather than through that site’s own (often limited) search interface. Particularly useful for sites with poor internal search — government portals, court systems, and organization directories often have better Google coverage than their own search boxes.

Important: site: does not search the site’s database — it searches what Google has indexed from that site. Pages behind login walls, dynamically generated records, and unlinked pages may not be indexed.


filetype: — Restrict to a Specific File Format

Returns only results in the specified file format.

filetype:pdf "John Smith" "Texas"
filetype:xlsx "employee roster" site:gov
filetype:doc "Marcus Webb" "Apex Financial"
filetype:csv "donor list"

Investigative use: Surfaces documents that would never appear in a standard search. Court filings, corporate reports, nonprofit disclosures, meeting minutes, and salary schedules are frequently published as PDFs. Spreadsheets and CSV files sometimes contain employee lists, vendor databases, or financial records. Word documents often contain draft reports, internal directories, and organizational charts.

Most useful file types for investigators:

Formatfiletype: valueWhat it typically contains
PDFpdfCourt filings, reports, meeting minutes, nonprofit disclosures
Excelxlsx or xlsSpreadsheets, rosters, financial data
Worddoc or docxReports, directories, contracts
PowerPointppt or pptxPresentations, org charts
CSVcsvData exports, donor lists, employee records
TexttxtPlain text files, configuration files

intitle: — Search Within Page Titles

Returns pages where the search term appears in the HTML title tag.

intitle:"John Smith" site:linkedin.com
intitle:"annual report" site:nonprofit.org
intitle:"staff directory" site:cityofaustin.org

Investigative use: Page titles are usually the most descriptive element of a page — they’re what appears in browser tabs and search result headlines. Filtering by title reduces noise significantly. A result with the subject’s name in the title is almost always more relevant than one where the name appears in passing in body text.

allintitle: — requires all terms to appear in the title:

allintitle:John Smith attorney Austin

inurl: — Search Within Page URLs

Returns pages where the search term appears in the URL itself.

inurl:court "John Smith"
inurl:resume "Marcus Webb"
inurl:profile "john.smith"

Investigative use: URLs often reveal the structure and purpose of a page before you visit it. A URL containing /court/, /filing/, /employee/, or /profile/ signals the type of page the result links to. Particularly useful for finding profile pages, directory listings, and document repositories.

allinurl: — requires all terms to appear in the URL:

allinurl:gov tax lien search

intext: — Search Within Page Body Text

Returns pages where the search term appears in the body text (as opposed to the title or URL).

intext:"[email protected]"
intext:"512-555-0187" Texas
intext:"4821 Shoal Creek" site:gov

Investigative use: Finds pages where a specific contact detail, address, or identifier appears in the body of a document — even if it doesn’t appear in the title or URL. Particularly useful for finding phone numbers and email addresses embedded in documents, court filings, and organizational pages.


cache: — View Google’s Cached Version

Returns Google’s stored snapshot of a page.

cache:linkedin.com/in/john-smith-phoenix
cache:website.com/staff-directory

Investigative use: If a page has been edited, taken down, or redirected, Google’s cache sometimes preserves an earlier version. Profiles that have been deleted, staff pages that have been updated, and contact directories that have been removed may still be visible in cache.

Limitation: Cache versions are typically only a few days to a few weeks old. For older historical versions, use the Wayback Machine (web.archive.org) instead.


related: — Find Similar Sites

Returns sites Google considers similar to the specified domain.

related:truepeoplesearch.com
related:pacer.gov
related:sec.gov

Investigative use: Quickly identifies alternative tools, competing databases, and similar platforms to the one you’re already using. Useful when a primary tool returns no results — finding related sites often surfaces alternative sources covering the same record type.


- — Exclude Terms

Removes results containing a specific term.

"John Smith" "Phoenix" -linkedin -facebook
"Marcus Webb" attorney -"Marcus Webb Jr"

Investigative use: Eliminates noise from results. If a search returns hundreds of results from one platform that aren’t useful, excluding that platform focuses the remaining results. Also useful for distinguishing between two people with similar names.


OR — Either/Or Search

Returns results containing either term.

"John Smith" OR "John M. Smith" "Phoenix"
"Apex Financial" OR "Apex Financial Group" Texas

Investigative use: Searches name variations and entity name variations simultaneously. A subject who goes by both “John Smith” and “John M. Smith” in different records can be caught in a single query rather than two separate searches.


* — Wildcard

Substitutes for any word or phrase.

"John * Smith" Phoenix
"Apex * Group" Texas SEC

Investigative use: Catches results where an unknown middle name, initial, or word appears between known terms. Useful when you know part of a name or phrase but not the complete string.


.. — Number Range

Returns results containing numbers within the specified range.

"John Smith" 2018..2022 lawsuit
"Apex Financial" $1000000..$5000000

Investigative use: Filters results by year range (to find records from a specific period) or by dollar amount (to filter financial disclosures within a range).


before: and after: — Date Filters

Returns results published before or after a specific date.

"John Smith" "Phoenix" after:2020-01-01
"Apex Financial Group" before:2019-12-31
"Marcus Webb" site:courts.tx.gov after:2018-01-01

Investigative use: Focuses results on a specific time period. Useful when investigating activity during a known window — a legal dispute, a business relationship, a period of employment — or when filtering out old results that predate relevant events.


Combining Operators: Where the Power Is

Individual operators are useful. Combined operators are transformative. Each additional operator narrows the result set toward exactly what you’re looking for.

The combination formula:

[exact phrase] [site:] [filetype:] [date filter] [-exclusions]

Not every query uses all elements — use as many as the search needs to produce a focused result set.


Investigative Dork Recipes

The following are complete, ready-to-use dork patterns for common investigative tasks. Replace bracketed terms with your actual search targets.


Person Research

Find someone across all indexed pages:

"[Full Name]" "[City, State]"

Find a specific person on LinkedIn:

site:linkedin.com/in "[Full Name]" "[City]"

Find someone’s contact information in documents:

"[Full Name]" filetype:pdf "[employer name]"

Find mentions of a person in government documents:

"[Full Name]" site:gov

Find a person in court records:

"[Full Name]" site:courts.[state].gov OR site:pacer.gov

Find a person’s email address:

"[Full Name]" "@" "[employer domain]"
"[Full Name]" intext:"@gmail.com" OR intext:"@yahoo.com"

Find a person across news archives:

"[Full Name]" "[City]" site:nytimes.com OR site:wsj.com OR site:reuters.com

Find cached or archived profiles:

cache:linkedin.com/in/[username]

Business and Entity Research

Find all indexed content from a specific organization:

site:[organization domain]

Find documents published by a government agency about a company:

"[Company Name]" site:sec.gov
"[Company Name]" site:ftc.gov
"[Company Name]" site:justice.gov

Find corporate filings and reports:

"[Company Name]" filetype:pdf "annual report"
"[Company Name]" filetype:pdf "10-K"

Find employee directories:

site:[company domain] intitle:"staff" OR intitle:"team" OR intitle:"directory"

Find a company in court records:

"[Company Name]" site:pacer.gov
"[Company Name]" "plaintiff" OR "defendant" filetype:pdf

Find press releases and news mentions:

"[Company Name]" intitle:"press release" after:[date]

Document and File Discovery

Find PDFs containing a specific person:

filetype:pdf "[Full Name]"

Find spreadsheets containing a person or organization:

filetype:xlsx "[Full Name]" OR filetype:csv "[Full Name]"

Find government documents about a subject:

filetype:pdf "[Full Name]" site:gov

Find court filings as PDFs:

filetype:pdf "[Full Name]" "plaintiff" OR "defendant"

Find nonprofit disclosures:

site:990finder.foundationcenter.org "[Organization Name]"
filetype:pdf "[Organization Name]" "Form 990"

Contact and Identifier Research

Find where a phone number appears:

"[phone number]" -site:yellowpages.com -site:whitepages.com

Find where an email address appears:

"[email address]"
intext:"[email address]" -site:emailfinder.com

Find where an address appears:

"[street address]" "[city, state]"
"[street address]" site:gov

Find domain registration information:

site:whois.domaintools.com "[domain name]"
"[domain name]" whois registrant

Historical and Cached Research

Find archived versions of a page:

site:web.archive.org "[target URL or domain]"

Find cached version of a specific page:

cache:[full URL]

Find old versions of a social media profile:

site:web.archive.org "linkedin.com/in/[username]"

Find content from a specific time period:

"[subject]" after:2015-01-01 before:2018-12-31

Social Media Research

Find profiles on a specific platform:

site:linkedin.com "[Full Name]" "[City]"
site:twitter.com "[Full Name]" "[employer]"
site:facebook.com "[Full Name]" "[City]"

Find posts mentioning a specific person:

site:reddit.com "[Full Name]"
site:twitter.com "[Full Name]" "[specific event or topic]"

Find a username across platforms:

inurl:[username] site:linkedin.com OR site:github.com OR site:twitter.com

Advanced Combinations for Complex Investigations

Find a person in multiple record systems simultaneously

"[Full Name]" "[City, State]" (site:gov OR site:courts OR filetype:pdf)

Find financial disclosures related to a subject

"[Full Name]" (filetype:pdf OR filetype:xlsx) ("financial disclosure" OR "Form 990" OR "annual report")

Find a subject mentioned in news within a specific time period

"[Full Name]" "[Company]" after:2019-01-01 before:2022-12-31 -site:linkedin.com

Surface all PDFs from a government site related to a subject

site:sec.gov filetype:pdf "[Company Name]" "[Full Name]"

Find a person’s court history across state and federal systems

"[Full Name]" "[City]" ("plaintiff" OR "defendant" OR "respondent") (site:gov OR filetype:pdf)

Find contact details across all indexed sources, excluding directories

"[Full Name]" (intext:"@" OR intext:"phone" OR intext:"contact") -site:whitepages.com -site:spokeo.com -site:beenverified.com

Find leaked or exposed documents containing a subject

"[Full Name]" filetype:pdf OR filetype:xlsx OR filetype:csv -site:[company domain]

Reading and Using Dork Results

A well-constructed dork returns a focused result set — but the results still require judgment to interpret.

Assess the source tier before clicking. A PDF result from site:sec.gov is a Tier 1 government source. The same information from site:spokeo.com is Tier 3. The search operator doesn’t change the source tier — it just surfaces it more efficiently.

Check the URL before you click. The URL often reveals what type of page or document you’re about to open. /filing/, /case/, /document/, /staff/, /report/ in the URL signals the nature of the result.

Use the cached version for deleted pages. If a result shows a page that now returns a 404 error, try cache:[URL] or run the URL through web.archive.org before concluding the page is gone.

Every identifier in the result is a pivot opportunity. A PDF result containing the subject’s name may also contain an address, a co-signer, an employer, or a case number — each of which becomes a new search input. Dork results feed directly into Phase 4 of the framework.

Document everything found. Record the query used, the URL, the retrieval date, and the key information found. A finding from a Google dork is only as defensible as the documentation that shows how it was reached.

→ Related guide: OSINT Pivoting: How to Follow Data Connections — [inet-investigation.com] → Related guide: How to Verify Information Using OSINT — [inet-investigation.com]


What Dorking Cannot Do

It cannot search behind login walls. Pages that require authentication — court portals that require account login, subscription databases, private social media profiles — are not indexed by Google and cannot be reached by any dork.

It cannot search dynamically generated content. Many government databases generate results on the fly rather than serving static pages. PACER case records, for example, are mostly not indexed by Google — search those databases directly.

It cannot guarantee results are current. Google’s index has a crawl delay — pages may have been updated or deleted since Google last indexed them. Always check retrieval dates and verify against live sources.

It cannot substitute for direct database search. Dorking surfaces what Google has indexed. Many valuable records — county property records, state court filings, UCC databases — are searchable directly through their source systems and may not be fully represented in Google’s index. Use dorking alongside direct database search, not instead of it.


Operational Security While Dorking

Every search you conduct is logged — by Google and by your own device. In sensitive investigations:

Use a clean browser session. A private/incognito window prevents your regular browsing history, cookies, and logged-in accounts from being associated with your investigation searches. It does not hide your IP address.

Consider a VPN. If investigation anonymity matters, a VPN masks your IP address from Google’s logs. This prevents your searches from being associated with your real location.

Don’t be logged into Google. Conducting investigation searches while logged into a Google account associates those searches with your identity and may affect your search results through personalization.

Don’t click suspicious results directly. If a dork returns a result that appears to be a sensitive or potentially malicious page, check the cached version or archive.ph snapshot rather than visiting the live page.

Document your queries. Record the exact dork used for each significant finding — this documents how the finding was reached and protects the integrity of the investigation.


Common Mistakes

Using too many operators at once on the first try. Start with two or three operators. If results are too narrow, remove one. If results are too broad, add one. Building the query incrementally produces better results than over-specifying from the start.

Forgetting that Google limits complex dorks. Very complex dork strings sometimes return fewer results than simpler ones because Google’s system may not execute every operator faithfully. If a complex dork returns zero results, simplify and rebuild.

Treating dork results as verified facts. A result surfaced by a dork is a lead. The source tier, the context, and corroboration with independent sources determine whether it becomes a finding. Apply the verification framework to everything a dork returns.

Assuming no results means no information exists. A dork returning zero results means Google hasn’t indexed what you’re looking for — not that the information doesn’t exist. Search the primary source directly.

Not documenting the query. The dork used to find a result is part of the provenance of that result. Always record the exact query string alongside the finding.


A Complete Dorking Workflow

Objective: Investigate a contractor named Brian Holloway, Austin Texas.

Step 1 — Broad baseline:

"Brian Holloway" "Austin Texas"

Returns general mentions, LinkedIn, news. Note every new identifier.

Step 2 — Government sources:

"Brian Holloway" "Austin" site:gov
"Brian Holloway" site:tx.gov

Surfaces any Texas state government records mentioning this name.

Step 3 — Court records:

"Brian Holloway" "Austin" ("plaintiff" OR "defendant") filetype:pdf
"Brian Holloway" site:search.txcourts.gov

Surfaces civil and criminal case filings.

Step 4 — Business records:

"Brian Holloway" site:sos.state.tx.us
"Torres Home Services" OR "Holloway" site:sos.state.tx.us

Searches Texas Secretary of State for business registrations.

Step 5 — Documents:

"Brian Holloway" filetype:pdf "Austin"
"Brian Holloway" filetype:xlsx OR filetype:csv

Surfaces PDFs and spreadsheets containing the name.

Step 6 — Contact detail pivots:

"Brian Holloway" intext:"@" "Austin"
"512-555" "Brian Holloway"

Finds email addresses and phone numbers associated with the name.

Step 7 — Historical:

"Brian Holloway" "Austin" after:2015-01-01 before:2020-12-31
site:web.archive.org "brianhollowayconstruction.com"

Focuses on a specific time period and surfaces archived pages.

Each step returns new identifiers. Each new identifier becomes a new dork input — and a pivot target in the broader investigation.


Frequently Asked Questions

Is Google dorking legal? Yes — dorking searches publicly indexed information using Google’s own interface. It does not involve accessing any system without authorization, bypassing any access control, or retrieving any data that isn’t publicly available. The legal issue arises if you use a dork to discover a URL and then access a page or file that requires authentication or bypasses access controls — that would potentially violate the CFAA regardless of how you found the URL.

Why do some dorks return no results? Several reasons: the information may not be indexed by Google, the page may be behind a login wall, the query may be over-specified and too narrow, or Google may not be executing all operators in a complex string. Simplify the query and search the primary source directly.

How is dorking different from just searching Google normally? Standard Google search applies relevance modeling, stemming, synonym expansion, and personalization. Operators override these — forcing exact matches, restricting to specific domains or file types, and filtering by date. The same information might exist in Google’s index but never surface without the right operator.

Can websites see when they’re being searched via dork? A Google dork search is just a Google search — the target website only sees traffic if you click through to their page. The search itself is invisible to the target.

Do dorks work on Bing and DuckDuckGo? Most operators work on Bing as well. DuckDuckGo supports some operators but fewer. Google typically has the most comprehensive index for these purposes.

How often does Google update its index? Major sites are crawled frequently — sometimes within hours of new content being published. Smaller sites and documents may take days or weeks. Cached versions of pages are typically a few days to a few weeks old.


Final Thoughts

Google dorking is the closest thing in OSINT to a force multiplier — a small number of operators, applied correctly, can surface more relevant information faster than hours of manual searching across individual tools.

The operators themselves are simple. The skill is in combining them — knowing which operators to pair, in what order, with which exact strings — and in knowing how to read and use what the results return.

Every dork result is raw material. The source tier determines its reliability. The verification process determines whether it becomes a finding. The pivot framework determines what it unlocks next.

Dorking doesn’t replace the investigation process — it accelerates it.


Where to Go Next

For the complete investigation process dorking feeds into: OSINT Workflow: The 8-Phase Investigation Framework — dorking sits in Phase 3 (initial search) and generates pivot inputs for Phase 4.

For what to do with what dorking surfaces: OSINT Pivoting: How to Follow Data Connections Across Systems — every identifier a dork returns is a new pivot entry point.

For how to verify what dorking finds: How to Verify Information Using OSINT — source hierarchy, cross-referencing, and confidence scoring applied to dork results.

For how to document it: How to Build an OSINT Report — documentation standards for dork-based findings.


Related Guides


Disclaimer: This article is for informational purposes only and does not constitute legal advice. Google dorking uses publicly available indexed information only. Accessing systems or files that require authentication, even when discovered through a dork, may violate applicable law. Use these techniques for lawful research purposes only.

3 thoughts on “Google Dorking for Investigators: Advanced Search Operators”

Comments are closed.