Tutorial — SpiderFoot recon overview
Last updated: October 21, 2026
Skill: osint-automation-frameworks
Time: ~60 minutes setup + first run
Goal
Automate passive footprinting of a domain or entity inside a controlled environment.
Steps
- Install SpiderFoot locally or on an org VM — never against personal targets without policy.
- Create a new scan; choose passive modules first.
- Seed with domain name or company name from public records.
- Review findings as leads; manually verify high-impact items.
- Export JSON/CSV for your evidence log.
- Purge scan data per retention policy.
What SpiderFoot is
SpiderFoot is an open-source OSINT automation tool, written in Python 3 and MIT-licensed, that runs from a web interface or the command line and has been actively developed since 2012. It ships with more than 200 modules; most need no API key, and many of those that do have a free tier. Each module queries one kind of source — passive DNS databases, certificate data and reputation services, breach data. Results are stored in a SQLite back end you can query directly, and export as CSV, JSON or GEXF, the last of which opens in Gephi for the network-mapping tutorial. A YAML-configurable correlation engine ships with 37 predefined rules that flag patterns across findings — treat each flag as a lead under step 4, like any other finding.
Passive first, and know what “passive” means
Not every module is passive. SpiderFoot can call other tools, including Nmap, DNSTwist, WhatWeb and CMSeeK, and its module list includes web application firewall detection. A port scan or a fingerprint of a website touches the target’s own systems, which is why the active modules need the legal review named under Pitfalls. A second, quieter disclosure applies to passive modules too: each third-party API module sends your seed to that service, telling it whom you are researching. Before step 2, read the module list, switch off anything that contacts the target directly, and decide which outside services you are willing to inform.
SpiderFoot also has a TOR integration for dark-web searches. Leave it off unless your policy covers that use.
Pitfalls
- Active modules can touch targets — legal review first.
- False positives from shared infrastructure.
Next steps
- Tutorial — DNS and WHOIS basics for manual confirmation
Sources
- SpiderFoot, project repository and module list.
Expanded with AI research and drafting assistance from the primary sources cited; editorial review pending.
