A roadmap for learning OSINT by doing careful research, checking sources, and writing conclusions that can survive scrutiny.
The roadmap follows the investigation process rather than a list of favorite tools.
Question
↓
Scope
↓
Discovery
↓
Verification
↓
Correlation
↓
Assessment
↓
Reporting
↓
Specialization
The order matters. Learn how to think about evidence first. Expand the toolset as your questions become more specific.
A completed investigation should make four things clear:
| Question | What a good answer looks like |
|---|---|
| What were you trying to find out? | A focused research question |
| Where did the information come from? | Traceable public sources |
| How did you test it? | Independent corroboration and context checks |
| What can you conclude? | A confidence-calibrated assessment |
Important
A tool can give you a lead. It cannot remove the need to verify the source behind the lead.
Open Source Intelligence is the structured collection, verification, analysis, and reporting of information available from public sources.
The structure matters. Searching without a question creates noise. Collecting without verification creates false confidence.
Public sources can include websites, archives, public records, public social media content, maps, imagery, company records, academic publications, public datasets, and domain or certificate information.
OSINT is not a form of unauthorized access. This project stays within lawful public-source research.
Choose one clue and work through it from the first search to the final report.
| Starting clue | First step |
|---|---|
| Domain | Domain playbook |
| Username | Username playbook |
| Email or phone | Identity and attribution workflow |
| Image | Image playbook |
| Video | Video playbook |
| Company | Company playbook |
| IP address | IP playbook |
| Public document | Document playbook |
| News claim | News-claim playbook |
| Location claim | Location playbook |
Do not try to memorize the whole OSINT ecosystem before you can complete a small investigation well.
Start with the habits that prevent weak conclusions:
- research-question design;
- scope and stopping conditions;
- provenance and source dependency;
- independent corroboration;
- timeline handling;
- entity resolution;
- confidence and uncertainty;
- evidence tables and source logs;
- researcher OPSEC.
Research methods
Skill Matrix
Quick Reference
Learn deliberate search rather than random searching:
- exact phrases and Boolean operators;
- site, file type, title, and date filters;
- archive reconstruction;
- multilingual search and transliteration;
- tracing claims towards their earliest public source.
Work with public clues such as usernames, aliases, public email addresses, public phone numbers, stable identifiers, self-declared links, and archived profile history.
A username match alone is weak attribution evidence.
Practice:
- legal-entity resolution;
- public registries and filings;
- ownership and relationship research;
- procurement and regulatory records;
- corporate timelines.
Resolve the entity before making claims about it.
Study reverse image search, earliest public appearance, provenance and repost chains, frame extraction, visual clues, temporal consistency, and cautious metadata interpretation.
Browser Extensions and Web Tools
A useful workflow is:
- find the earliest source you can identify;
- locate primary documents or first-hand statements;
- compare genuinely independent reporting;
- check corrections and later updates;
- use archives when they add useful context.
Start broad and narrow the candidate set with evidence.
Country or region
↓
City or area
↓
Road, landmark, or terrain
↓
Specific location, only when justified
After important observations are verified, connect them carefully.
Learn:
- entity resolution;
- relationship mapping;
- timeline analysis;
- geographic correlation;
- competing hypotheses;
- confidence calibration;
- missing-data analysis.
The goal is not the largest graph. It is the strongest explanation the evidence can support.
A professional note should make the research reproducible.
Question
Scope
Method
Sources
Findings
Analysis
Confidence
Limitations
Conclusion
Choose a track when the core workflow is comfortable.
| Track | Focus |
|---|---|
| Cyber Threat Intelligence | PIRs, public indicators, infrastructure relationships, ATT&CK, timelines, attribution |
| Digital Footprint Investigation | public traces, attribution, archives, privacy-aware research |
| Company Investigation | entity resolution, filings, ownership, corporate timelines |
| Advanced GEOINT | geolocation, chronolocation, imagery, candidate rejection |
| Journalism and Fact Checking | source tracing, media provenance, claim verification |
| Public Web Infrastructure | domains, DNS, certificates, passive infrastructure research |
The repository keeps a curated collection of tools and public-source resources rather than trying to list everything.
Each entry is intended to make four things clear:
What input does it need?
What is it useful for?
What are its limits?
How should the result be verified?
Tool Library
Investigator Tool Stack
Verified Open-Source Tools
The project uses an artifact-based learning model.
Learn
↓
Practice
↓
Produce
↓
Defend
↓
Review
A useful artifact can be a timeline, source assessment, claim-verification report, geolocation exercise, attribution assessment, or short intelligence note.
Practice Labs
Skill Matrix
Case Studies
AI can help with search-query variants, language support, organization, entity extraction, and alternative hypotheses.
It should not be treated as a substitute for sources.
AI suggests
↓
You inspect
↓
You verify
↓
You document
This project is limited to lawful public-source research.
It does not cover unauthorized access, credential attacks, account takeover, access-control bypass, deceptive social engineering, stalking, harassment, doxxing, or intrusive scanning without authorization.
Practical rule:
If the next step requires intrusion,
deception, private access,
or bypassing a security control,
stop.
OSINT resources change. Ownership, pricing, permissions, coverage, interfaces, and terms can all change.
A working URL does not prove that a resource description is still current.
OSINT Tool Radar
Updates Archive
The repository separates link health from content freshness and runs automated checks for both.
Good contributions are specific and verifiable.
Examples include correcting a source, replacing an outdated resource, improving a translation, adding a safe practice lab, documenting a better verification method, or explaining a tool limitation more accurately.
MIT License © Imed Kablavi