PAGES
← all tools
◆ Reconnaissance & OSINT

reconspider

1.0.2 open-source

ReconSpider is an OSINTOSINTOpen-source intelligence, collecting and analyzing information from publicly available sources. Investigators use it to learn about people, infrastructure or threats. framework that scans IP addresses, emails, websites, and organizations to find information from different sources.

Summary

reconspider is an open-source OSINT framework, run from the command line, that gathers information on IP addresses, emails, websites and organizations from public sources and pulls the results into a single dashboard for review. It is aimed at infosec researchers, penetration testers, bug hunters and cybercrime investigators who need to profile a target rather than scan infrastructure they already own. Its README describes it as combining the capabilities of Wave, Photon and Recon Dog into one enumeration workflow, so it sits alongside those projects rather than replacing a full attack-surface management platform. Commands cover IP lookups, domain enumeration, honeypot detection and breached-email checks. The project dates to 2018 and has had four releases in the tracked window, but there have been no commits in the past year, so treat it as dormant before relying on it.

ReconSpider is an OSINT framework that scans IP addresses, emails, websites, and organizations to find information from different sources.

How reconspider helps

What can I find out about a target IP address before I engage with it?

looks up the address across public sources and returns what it can gather in one pass, pulled into the dashboard for review

Is this IP address actually a honeypot before I probe it further?

checks the address against honeypot indicators and reports back so a researcher does not walk into a monitored decoy

Has this email address turned up in a known breach?

runs the address against breach-check sources and reports what surfaces, giving an investigator a starting point on a target's exposure

What subdomains and structure does this organization's website expose?

enumerates the domain the way Photon does, crawling it to surface pages and endpoints tied to the target

Where do all these separate lookups leave me when I'm profiling a target?

aggregates the results from the IP, email, and domain checks into a single dashboard instead of leaving a researcher to stitch together separate tool outputs

all 3 features, with the evidence for each →

Languages

Not documented

Features

3 capabilities

Built from reconspider's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

  • reconspider covers 1 of the 13 network discovery and scanning capabilities we track.

What reconspider offers you

  • Command-line interface
All capabilities 3 capabilities
Open-source intelligence gathering shipped Scans IP addresses, emails, websites, and organizations to gather intelligence from multiple public sources. 3 releases · 1 other source · first seen Dec 2018

Shared capability: Attack surface inventory

release

  • Mind Map (v1) feature for visualizing reconnaissance data 1.0.2 · Dec 2018 · source · release history
  • Integrates Shodan, Clearbit, and FullContact APIs as input sources 1.0.2 · Dec 2018 · source · release history
  • Adds Termux support allowing the tool to run directly on Android phones 1.0.2 · Dec 2018 · source · release history

docs

  • OSINT framework that scans IP addresses, emails, websites, and organizations to gather intelligence from multiple public sources.
Honeypot detection shipped Checks if a target IP address is configured as a honeypot. 1 other source

example

  • Check if an IP is a honeypot ReconSpider >> 7
IP address information enumeration shipped Enumerates detailed information from a target IP address. 1 other source

Shared capability: Attack surface inventory

example

  • Enumerate information from an IP address ReconSpider >> 1

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for reconspider, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail reconspider puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

1 entry

  1. December 20181

    1 entry

    Project health

    Issue, contributor and maintainer activity in bhavsec/reconspider, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 0 ±0 vs prior 12 months
    2. Maintainers 0 +0 joined · −0 left, last 12 months
    3. Bus factor 0 committers behind half the commits
    4. Community-filed 100% of issues opened, last 12 months
    5. Median time to close not measured issues closed, last 12 months
    6. Open backlog 19 of 48 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 19
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars 2,813
    Issue themes, last 12 months
    • other 100%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Libraries its release ships

    What its latest release locks, checked against known advisories.

    None of its release's images build from a lockfile we can read.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →