Skip to main content
SpiderFoot is an open-source OSINT automation tool that security teams use to map an attack surface and gather threat intelligence from hundreds of sources in a single scan. The sfp_pulsedive module adds Pulsedive as one of those sources, so its risk scores and context feed into the same scan as SpiderFoot’s other modules, rather than requiring a separate lookup. The module ships in both the open-source SpiderFoot CE and the commercial SpiderFoot HX, so the same setup applies whichever version you run.

Prerequisites

Before you connect SpiderFoot to Pulsedive, make sure you have:
  • A Pulsedive account and API key. Find your API key on your Pulsedive account page.
  • A SpiderFoot instance (open-source or HX) with permission to configure module settings.

Connecting SpiderFoot to Pulsedive

Follow these steps to configure the Pulsedive module, so it is available to include in a scan:
  1. In SpiderFoot, go to Settings and find Pulsedive in the module list.
  2. Enter your Pulsedive API key in the module’s configuration.
  3. Save the settings.
For the module’s source and any updates, visit the sfp_pulsedive module on GitHub.

Verifying the Connection

Confirm that the module returns data before you rely on it in a full scan.
  1. Start a new scan against a target you know Pulsedive has data on.
  2. Enable only the Pulsedive module.
  3. Confirm that results appear once the scan completes.

Using Pulsedive Data in SpiderFoot

Once configured, include the Pulsedive module in any scan alongside SpiderFoot’s other modules, so its enrichment feeds into the same report. Beyond IOC enrichment, Pulsedive also surfaces contextual data the module pulls in, such as related article summaries, so a SpiderFoot scan can turn up threat context beyond a plain risk score.