National Cyber Warfare Foundation (NCWF)login

One-Liner-OSINT for fast public-source intelligence queries


0 user ratings
2026-11-11 11:26:02
milo
Red Team (CNA)
"One-Liner-OSINT

One-Liner-OSINT is a curated cheatsheet of single-line commands and search dorks that speeds up open-source intelligence gathering for authorized assessments and defensive research.








Toolyogsec/One-Liner-OSINT — a collection of one-liner commands and search-engine dorks for open-source intelligence gathering
CategoryOSINT reference / command cheatsheet
Primary UseAccelerating passive reconnaissance during authorized engagements — pivoting from site: dorks to tools like subfinder, theHarvester, Amass, and exiftool
Safe UseEducational reference for authorized penetration tests, bug bounty programs with defined scope, and defensive research on an organization's own exposure
Telemetry NoteThe dorks themselves are passive search-engine queries and leave no trace on targets; the referenced tools (theHarvester, Amass, sherlock) generate observable network lookups and scrape activity visible to platform operators

yogsec/One-Liner-OSINT sits in the category of repository that every operator eventually builds for themselves: a dense, copy-paste cheatsheet of search-engine dorks and single-line tool invocations aimed at open-source intelligence work. Rather than shipping an executable, the project distributes knowledge — each entry pairs a plain-language goal, such as finding a person's email address or locating exposed database files, with a one-line query you can drop into a search box or terminal. With around 218 stars, an MIT license, and topic tags spanning osint, bug-bounty, and osint-reconnaissance, it is positioned squarely as a working reference for bug bounty hunters, security researchers, and ethical hackers operating inside authorized scope.


The bulk of the repository is organized around Google-style operators: site:, filetype:, intitle:, inurl:, intext:, and ext:. What the README does well is group these into mission-oriented clusters instead of a raw dump. The personal-intelligence section, for example, chains operators to surface email addresses ("John Doe" "@gmail.com"), enumerate social profiles across linkedin.com, facebook.com, twitter.com, and instagram.com, and hunt for resumes via filetype:pdf | filetype:doc "resume". The value is not any single dork — most are well known — but the taxonomy that lets you move methodically through a person's or organization's public footprint during a scoped engagement.


The organizational-reconnaissance section is arguably the most practically useful for bug bounty work. Queries like site:*.targetcompany.com -www for subdomain enumeration via the search index, intitle:"index of" site:targetcompany.com for open directories, and site:targetcompany.com ext:pdf | ext:doc | ext:ppt "confidential" for inadvertently published documents map directly onto the reconnaissance phase of an authorized assessment. The README also covers infrastructure exposure checks — open FTP servers, login portals via inurl:admin | inurl:dashboard | inurl:login, and job postings that leak technology-stack details through "hiring" and "we are looking for" phrasing.


A significant share of the collection addresses exposure that defenders should care about as much as attackers do. Dorks for unprotected MongoDB instances (inurl:27017 "_id"), open Elasticsearch nodes (inurl:9200 "_search"), public Firebase storage, exposed AWS S3 buckets (site:s3.amazonaws.com), and leaked API keys in GitHub repositories (site:github.com "api_key" "secret") describe misconfiguration classes that blue teams routinely hunt with the exact same queries. That duality is the honest framing for this repo: every offensive-flavored query here is equally a defensive audit checklist for an organization's own assets.


Beyond pure dorks, the README curates a short catalog of established OSINT tooling with sample invocations, including subfinder -d target.com for subdomain discovery, theHarvester -d target.com -b all for email and subdomain harvesting, amass enum -d target.com for network mapping, metagoofil for document metadata extraction, and sherlock username for cross-platform social account enumeration. There are also pointers to commercial and hosted resources such as hunter.io for email-pattern inference, haveibeenpwned.com for breach-notification lookups, Maltego for link analysis, and reverse-image services like TinEye and Google Images. Nothing here is novel tooling; the curation is the product.


The geolocation section is thin but interesting: it combines exiftool image.jpg for stripping GPS coordinates out of image EXIF metadata with a Twitter geocode query pattern (geocode:40.7128,-74.0060,5km) and archive-based lookups through site:web.archive.org. The cached-and-deleted-content cluster — Google cache: lookups, Wayback Machine searches, and site:gov OR site:mil filetype:pdf "confidential" style document hunts — rounds out a workflow for reconstructing information that a target believes has been removed from the live web but persists in indexes and archives.


From an editorial standpoint, there are things to watch. Some entries in the README mix | and OR operators inconsistently, and search engines treat them differently — | and OR both work in Google, but piped alternation inside quoted phrases does not, so a few dorks as written will return noisy or empty results. A handful of referenced services, such as throwbin.io and darksearch.io, have unstable availability, and queries aimed at breach forums or paste sites skirt close to consuming stolen data. Professionals should treat those entries as documentation of technique, not a workflow to reproduce, and rely on legitimate breach-notification services like haveibeenpwned.com instead.


The person-search section deserves an explicit caution. Dorks for locating individuals' phone numbers, addresses, Amazon wishlists, and location-tagged social posts are powerful, and using them against people who have not consented — or outside a documented investigative mandate — crosses from OSINT into harassment and potential legal exposure. In an authorized context this material fits investigations, due-diligence work, and threat-actor research, where the subject is a genuine adversarial actor or the in-scope personnel of an engaged client. The repo's own framing targets security research and ethical hacking, and that boundary should be respected operationally.


Where One-Liner-OSINT earns its place is as a memory prosthesis and coverage checklist. A junior operator can walk its sections top to bottom during reconnaissance and be reasonably confident they have touched the standard surface: search-index enumeration, metadata, cloud exposure, credential-leak signals, social footprint, and archived content. An experienced operator will already know most entries but will still appreciate having the alternation-heavy combined queries pre-built. Since there is nothing to install — git clone https://github.com/yogsec/One-Liner-OSINT gets you the whole toolkit — the barrier to adoption is effectively zero.


The telemetry and detection angle is worth stating plainly for defenders. Passive dorking against search engines leaves no footprint on your own infrastructure, which means an adversary using this repo against your organization is largely invisible until they pivot to active tooling like Amass, subfinder, or theHarvester, all of which generate observable DNS resolution patterns, certificate-transparency lookups, and scraping traffic. The defensive takeaway is to monitor for that second stage, and to proactively run the exposure dorks — open directories, leaked documents, exposed S3 and Firebase endpoints, API keys in public repositories — against your own domains before someone else does. Used that way, this cheatsheet is as much a hardening guide as an attack aid.



Official project repository for yogsec/One-Liner-OSINT.

Download Tool

Educational analysis for authorized security professionals. Use only in controlled, authorized environments.






Source: OffensiveSec
Source Link: https://www.offsecblog.com/2026/11/one-liner-osint-for-fast-public-source.html


Comments
new comment
Nobody has commented yet. Will you be the first?
 
Forum
Red Team (CNA)



Copyright 2012 through 2026 - National Cyber Warfare Foundation - All rights reserved worldwide.