Overview
SpiderFoot is an open-source OSINT automation platform. Instead of running ten tools by hand, you give SpiderFoot one target — a domain, IP, email, username or ASN — and its 200+ modules query threat feeds, search engines, DNS records, breach data and social sources automatically, then correlate everything into a single browsable report.
It runs as a local web app with a command-line option for scripting, and because it is self-hosted your targets never leave your infrastructure. Teams schedule recurring scans to watch their own exposure drift over time; investigators use one-off scans to turn a single identifier into a full entity graph in minutes.
Key features
- 200+ modules: feeds, DNS, breaches, search, social, threat intel
- One target in — correlated graph and browsable report out
- Self-hosted: your targets never leave your infrastructure
- Scheduled and API-driven scans for continuous monitoring
- Built-in visualizations of entity relationships
- Free and open source (MIT)
Install & first run
# Clone and install (Python 3.9+)
git clone https://github.com/smicallef/spiderfoot.git
cd spiderfoot
pip install -r requirements.txt
## Start the web interface
python3 ./sf.py -l 127.0.0.1:5001
# Open http://127.0.0.1:5001, create a new scan,
# enter your target and pick the modules to run.
Real-world example
All you have is a suspicious domain from a phishing email. Create a SpiderFoot scan with that domain as the seed and let its modules work: DNS records, certificate logs, breach data, threat feeds and similar-domain searches run automatically and link into one graph.
Read the graph outward from the seed. A cluster of lookalike domains registered the same week through the same registrar is a campaign, not a coincidence — export the report and hand the indicator list to your blocking and takedown process.
Common questions
Is SpiderFoot fully passive?
Behavior depends on enabled modules and data sources; review module behavior before a run.
How many modules does it have?
Over 200, split into passive (third-party data) and active (direct to target) sets. Passive modules need no API key; the key-based ones add depth.
What is the correlator for?
It cross-links findings from different modules, which is how a domain turns into an organisation, then into contacts. Without it, you just get rows.
Can I run a scan from the CLI?
Yes: sf.py -s example.com -t DOMAIN_NAME -m all -o tab. Useful for scheduled recon; the UI is for exploring results.
Related tools
Maltego
Graph people, domains, emails and organisations, then expand them with transforms that pull live data. Free Community Edition.
Recon-ng
Metasploit-style console for OSINT: workspaces, modules and a database that keeps every finding queryable. Free, open source.
Keep exploring: browse every investigation type in the OSINT Hub.
Use OSINT tools responsibly — only investigate accounts, people or systems you have a legitimate reason to look into.
