Jump to: 🔥 Challenge News ⚡ Intel 🔬 Research Labs 📡 All News →

OSINT Masterclass

Open Source Intelligence from fundamentals to expert — people intelligence, infrastructure analysis, social media OSINT, geolocation, dark web monitoring, and investigator OPSEC. Global curriculum. Every tool free.

7
Phases
21
Modules
210
Days
100%
Free Tools
Phase 1 · Foundations
The OSINT Mindset, Legal Framework & Tooling Setup
OSINT is not just using Google. It is a systematic discipline with methodology, ethics, and legal constraints. Before touching a single tool you must understand what you are legally allowed to do, how to protect yourself while investigating, and how to think like a professional investigator.
📅 25 days 🎯 Complete beginner 🛠 OSINT Framework · Maltego CE · Tor Browser · ProtonVPN
MOD 01 What OSINT Is — Methodology, Ethics & Legal Boundaries Days 1-8
Tutor Explanation

Open Source Intelligence is intelligence derived from publicly available sources — information that anyone could access without hacking, without breaking any laws, and without requiring special authorisation. The word "open" does not mean "easy to find" — it means "not secret." Court documents, company registrations, satellite imagery, forum posts, and domain registration records are all open source. A skilled OSINT analyst finds in hours what a casual searcher cannot find in weeks.

The critical distinction is between collection and misuse. Finding information that is publicly available is generally legal. What you do with it, and who you target, determines legality. Stalking an individual using OSINT is illegal in every jurisdiction regardless of how the information was obtained. Using OSINT to investigate your own organisation's threat exposure is standard security practice. The same techniques — different legal status depending on purpose and target.

The OSINT Investigation Process — Always Follow This
Step 1 — Define scope and objective: What question are you trying to answer? Who or what are you investigating? What is the legal basis for this investigation? Write this down before starting. Scope creep is the enemy — an undefined investigation goes on forever and collects far more data than needed.

Step 2 — Identify sources: Which sources could contain information relevant to your objective? Map your sources before querying them. This prevents repetitive, inefficient searching and ensures systematic coverage.

Step 3 — Collect with OPSEC: Use investigative infrastructure (VPN, burner accounts, isolated browser profile) so your target cannot detect that they are being researched. Your investigation should be invisible.

Step 4 — Verify and cross-reference: Never trust a single source. Every significant finding must be corroborated by at least two independent sources before it appears in your report. Source reliability assessment is essential.

Step 5 — Analyse and contextualise: Raw data is not intelligence. What does this finding mean in context? What does it tell you about your objective? How confident are you in this conclusion?

Step 6 — Document and report: Document every source for every finding with timestamps. Your documentation must be sufficient to allow someone else to verify your findings independently.
Never create fake accounts on social media platforms to conduct OSINT investigations. Most platform ToS explicitly prohibit this and in some jurisdictions it creates criminal liability. Never access information that requires logging into an account you do not own. "Publicly available" means accessible without authentication.
Daily Tasks — Week 1
Browse the OSINT Framework (osintframework.com) for 30 minutes. Do not use any tools — just read the categories and understand the breadth of information sources available. Write a list of 10 categories you did not expect.
Easy
Research the legal framework for OSINT in your country. Find the specific laws that govern: (a) accessing public information, (b) processing personal data, (c) investigating individuals for security purposes. Write a one-page legal summary.
Medium
Google yourself thoroughly. Spend 1 hour finding everything publicly available about yourself. Document every source. This gives you both a personal exposure baseline and a visceral understanding of what OSINT can reveal.
Easy
Scenario ethics exercise: You are asked to conduct OSINT on a business partner before signing a contract. Write out: what you are legally allowed to collect, what you should not collect, and where the ethical line is between due diligence and invasion of privacy.
Hard
MOD 02 Investigative Infrastructure — Your Anonymous Research Environment Days 9-18
Tutor Explanation

Every website you visit logs your IP address. Every Google search is associated with your account and browser fingerprint. When you investigate a target using your personal browser and home IP, the target's server logs show that someone at your ISP's IP range was looking at their website — and if they are security-aware, they may be able to identify your employer or location. Professional OSINT requires an isolated investigation environment that cannot be traced back to you or your organisation.

This is not about doing anything illegal — it is about maintaining professional integrity and preventing your target from detecting that they are under investigation. A threat actor who knows they are being investigated will change their infrastructure, delete accounts, and disappear. A corporate espionage target who detects due diligence research may tip off their co-conspirators. Investigation integrity requires investigator invisibility.

The Investigative Infrastructure Stack
Layer 1 — Network anonymisation: A VPN (ProtonVPN free tier, Mullvad, or Tor) masks your real IP address. For investigations: use a VPN exit node geographically distant from your real location, or in the same country as your target (to blend with expected visitor sources). Tor provides stronger anonymity but is slower and may be blocked by some sites.

Layer 2 — Isolated browser profile: Create a dedicated browser profile (Firefox) used exclusively for OSINT. No personal accounts, no saved passwords, no browser history, no extensions that could leak identity. Use Firefox with uBlock Origin and Privacy Badger. Disable WebRTC (leaks real IP even with VPN).

Layer 3 — Sock puppet accounts: For investigations requiring social media access, create purpose-built accounts (sock puppets) with no connection to your real identity. Use ProtonMail for email, a VoIP number (Google Voice, TextNow) for SMS verification, and a profile photo generated by thispersondoesnotexist.com. Manage sock puppet accounts only from your investigation VM, never from your personal device.

Layer 4 — Dedicated VM: Run all OSINT tools from a dedicated virtual machine (Kali Linux or a custom Ubuntu install with OSINT tools). Snapshots allow you to restore a clean state after each investigation. Tails OS (boots from USB, leaves no trace on the host) for the most sensitive investigations.

Layer 5 — Separate investigation workspace: Never mix personal and investigation activities on the same device, the same browser, or the same network session. One investigation = one isolated workspace.
Browser Fingerprinting — The Invisible Identifier
Even with a VPN and a clean browser, websites can identify you through browser fingerprinting — combining: screen resolution, installed fonts, browser plugins, timezone, language settings, hardware acceleration capabilities, and canvas rendering. This combination is often unique to your specific device. Test yourself at coveryourtracks.eff.org.

Mitigation: use a standard resolution (1920x1080 or 1366x768), disable custom fonts, use a common browser version, and consider Firefox with the arkenfox user.js configuration which standardises many fingerprinting vectors.
Hands-On Lab
Lab 2.1 — Build Your Investigation Environment
1Create a dedicated Firefox profile: firefox.exe -P → Create new profile → Name it "OSINT". Open this profile. Go to about:config. Set: media.peerconnection.enabled = false (disables WebRTC IP leak), privacy.resistFingerprinting = true.
2Install uBlock Origin, Privacy Badger, and User-Agent Switcher. Set User-Agent to a common Chrome on Windows string to blend with the majority of web traffic.
3Test your anonymisation. With VPN active and OSINT browser profile, go to: ipleak.net (check IP and WebRTC leak), coveryourtracks.eff.org (fingerprint test), browserleaks.com (comprehensive leak test). Document findings.
4Create a ProtonMail account (free) using only your OSINT browser profile over VPN. This is your investigation email. Never access it from your personal browser.
5Optional — Kali Linux VM with OSINT tools: Install VirtualBox (free), download Kali Linux, install it as a VM. Install the OSINT tools metapackage: sudo apt install kali-tools-information-gathering
Daily Tasks — Week 2
Build your full investigation environment: dedicated Firefox profile, VPN configured, WebRTC disabled. Test for leaks. Document your configuration so you can rebuild it if needed.
Easy
Visit the same website first with your regular browser (no VPN, personal profile) and then with your investigation browser (VPN, clean profile). Use Wireshark to capture both sessions. Compare what information the website received in each case. What data did your investigation profile hide?
Hard
MOD 03 Google Dorking & Advanced Search Operators Days 19-25
Tutor Explanation

Google indexes far more than you see on the first page of a normal search. Search operators — special commands that modify how Google processes your query — allow you to surgically extract specific types of information from the entire indexed web. A single well-crafted dork can find exposed configuration files, credentials in repositories, publicly accessible login pages, and sensitive documents that were indexed accidentally.

Google dorking (also called Google hacking) is entirely legal — you are querying publicly accessible information through Google's normal search functionality. The ethical line is what you do with what you find: reporting an exposed credential file to the affected organisation is responsible disclosure; using it to access systems is a crime.

Essential Google Operators
site: Restricts results to a specific domain. site:targetcompany.com filetype:pdf — find all PDFs on a domain.

filetype: / ext: Find specific file types. filetype:xlsx site:gov.in budget — find Excel files from Indian government sites about budget.

inurl: Search within URLs. inurl:admin inurl:login site:targetcompany.com — find admin login pages.

intitle: Search page titles. intitle:"index of" site:targetcompany.com — find open directory listings.

intext: Search page body text. intext:"confidential" intext:"do not distribute" filetype:pdf — find accidentally indexed confidential documents.

cache: View Google's cached version of a page — even if the live page has been taken down. cache:targetsite.com/removed-page

link: Find pages that link to a specific URL — useful for mapping a site's external references and finding related content.

before: / after: Date range filtering. site:targetcompany.com before:2020-01-01 — find older indexed content.

Combinations (dorks):
site:targetcompany.com ext:env | ext:cfg | ext:conf | ext:ini — find config files
site:github.com "targetcompany" password | apikey | secret | token — find credential leaks
intitle:"index of" "parent directory" site:targetcompany.com — open directories
site:pastebin.com targetcompany.com email password — credential dumps on pastebin
Hands-On Lab
Lab 3.1 — Systematic Google Dorking for Target Research
1Choose a target organisation (use your own employer for legal clarity, or a large public company that has consented to security research). Document your legal basis.
2Run these dork categories systematically and document findings:
Config files: site:target.com ext:env OR ext:cfg OR ext:xml OR ext:json
Exposed directories: site:target.com intitle:"index of"
Login pages: site:target.com inurl:login OR inurl:admin OR inurl:portal
Documents: site:target.com filetype:pdf OR filetype:xlsx OR filetype:docx
Subdomains: site:*.target.com -www
3Use the Google Hacking Database (GHDB) at exploit-db.com/google-hacking-database. Browse by category — look for dorks relevant to your target's technology stack.
4Search GitHub for your target's credentials: site:github.com "target.com" password OR apikey OR secret. Also search: site:pastebin.com "target.com" and site:trello.com "target.com".
5Compile all findings into a structured report. Rate each finding by severity: Critical (exposed credentials), High (sensitive internal documents), Medium (technology disclosure), Low (employee names, email format).
Daily Tasks — Week 3
Run a full dorking investigation on your own organisation (with permission). Document every finding. If you find any exposed sensitive information, report it to the appropriate team immediately.
Medium
Build a personal Google dork cheat sheet organised by category: credential exposure, config files, login pages, open directories, document discovery, employee information. You will use this in every future investigation.
Easy
Advanced: use GooFuzz (free Python tool) to automate Google dorking across multiple operators for a target domain. Compare automated results vs manual dorking — what did each method find that the other missed?
Hard