> For the complete documentation index, see [llms.txt](https://osintverse.gitbook.io/otinstaller/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://osintverse.gitbook.io/otinstaller/tools/spiderfoot.md).

# Spiderfoot

SpiderFoot automates OSINT for threat intelligence and mapping your attack surface.

## Source

* Repository: <https://github.com/smicallef/spiderfoot>
* License: MIT

## Install

```bash
otinstaller install spiderfoot
```

otinstaller clones `https://github.com/smicallef/spiderfoot.git` at ref `0f815a203afebf05c98b605dba5cf0475a0ee5fd` into a dedicated virtualenv, then installs the dependencies listed in `requirements.txt`.

## Credentials

No API keys needed.

## Input types

| Input        | Typed input     | Tool arguments   |
| ------------ | --------------- | ---------------- |
| domain (`d`) | `d:example.com` | `-s example.com` |

otinstaller always adds these arguments first: `-u passive`.

## Example output

Illustrative output showing the general shape of a run. Real output depends on the tool version and the target.

```
example output for spiderfoot:
------------------------------------------------------------
[+] SpiderFoot HPC - Scan ID: scan-20240115-123456
[+] Target: example.com
[+] Modules: 150+ modules enabled
[+] Scan started: 2024-01-15 10:30:00 UTC

[*] Found 156 findings across 15 modules:

[*] DNS Records (sfp_dns)
    A: example.com -> 93.184.216.34
    MX: example.com -> mail.example.com
    NS: example.com -> ns1.example.com, ns2.example.com
    TXT: example.com -> "v=spf1 include:_spf.example.com ~all"
    CAA: example.com -> 0 issue "letsencrypt.org"

[*] Whois (sfp_whois)
    Registrar: Example Registrar, Inc.
    Creation: 1995-08-14
    Expiry: 2025-08-13
    Registrant: Example Organization
    Email: admin@example.com

[*] SSL Certificate (sfp_sslcert)
    Issuer: Let's Encrypt
    Subject: example.com
    Valid: 2024-01-01 to 2024-04-01
    SANs: example.com, www.example.com

[*] Subdomain Enumeration (sfp_dnsbrute, sfp_ctfr, sfp_sublist3r)
    www.example.com -> 93.184.216.34
    mail.example.com -> 93.184.216.34
    ftp.example.com -> 93.184.216.34
    dev.example.com -> 192.0.2.10
    staging.example.com -> 192.0.2.20
    api.example.com -> 192.0.2.30
    admin.example.com -> 192.0.2.40

[*] Email Addresses (sfp_email)
    admin@example.com
    support@example.com
    security@example.com
    abuse@example.com
    webmaster@example.com

[*] Social Media Profiles (sfp_social)
    Twitter: https://twitter.com/examplecom
    LinkedIn: https://linkedin.com/company/examplecom
    GitHub: https://github.com/examplecom

[*] Technologies (sfp_builtwith, sfp_wappalyzer)
    Web Server: nginx/1.20.0
    CMS: WordPress 6.2
    Language: PHP 8.1
    Framework: Laravel 10
    CDN: Cloudflare

[*] Vulnerabilities (sfp_vulners, sfp_nvd)
    CVE-2023-1234: WordPress < 6.2.1 - Medium (CVSS 6.1)
    CVE-2022-9876: nginx < 1.22.0 - Low (CVSS 3.7)

------------------------------------------------------------
(Example truncated - real output contains 156+ findings across 15+ modules)
```

## Run

Plain arguments after `--` are passed to the tool unchanged:

```bash
otinstaller run spiderfoot -- -u passive -s example.com
```

Typed inputs are mapped to this tool's flags:

```bash
otinstaller run spiderfoot d:example.com
```

Results are saved to `./results/spiderfoot/<target>/`.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://osintverse.gitbook.io/otinstaller/tools/spiderfoot.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.