1. Link directory
The OSINT Framework is a categorized directory of resources, not a tool you run — it organizes where to look.
# OSINT Framework: categorized link treeTyporithm · medium
Step 1 of 8 · intro card
Frameworks & Automation
OSINT frameworks organize and automate collection: the OSINT Framework is a categorized directory of resources, Maltego graphs entities and their links, and SpiderFoot and Recon-ng automate footprinting across many sources — turning scattered manual lookups into repeatable investigations. Use only against authorized targets and within the law.
Frameworks exist to organize and automate collection. The OSINT Framework is a categorized link tree — a directory of resources grouped by data type, so an investigator knows where to look rather than how to query.
Maltego graphs entities and their relationships visually, turning a list of facts into a map of who connects to what. SpiderFoot and Recon-ng instead automate footprinting, querying many data sources for a single seed target.
Together these tools turn scattered, one-off manual lookups into repeatable, mapped investigations. They are for authorized, lawful work only: respect each data source's terms of service and the law.
OSINT Framework: a categorized directory of resources.
Maltego: a visual graph of entities and links.
SpiderFoot / Recon-ng: automated multi-source footprinting.
# OSINT Framework: categorized link tree
# Maltego: visual graph link-analysis
spiderfoot -s example.com
recon-ngConnect each part of the code to the concept before you type.
The OSINT Framework is a categorized directory of resources, not a tool you run — it organizes where to look.
# OSINT Framework: categorized link treeMaltego graphs entities and the links between them so relationships are visible at a glance.
# Maltego: visual graph link-analysisSpiderFoot automates footprinting across many data sources for a single seed target.
spiderfoot -s example.comRecon-ng is a modular reconnaissance framework that scripts data gathering from many sources.
recon-ngRead the concept map and follow the code breakdown.
Type the implementation, repair mistakes and work through every recall exercise.
Use the final check without hints; revisit weak concepts in short practice sessions.