assetfinder
open-sourceThe section your link pointed to isn't on assetfinder's page any more, so we've brought you to the top.
Find domains and subdomains related to a given domain - tomnomnom/assetfinder
Summary
assetfinder is an open-source command-line tool that finds domains and subdomains related to a given target by querying passive sources such as crt.sh, certspotter, hackertarget, threatcrowd, the Wayback Machine, and optionally Facebook, VirusTotal, and Spyse via API keys. It is free to use, installed with go get or a prebuilt release binary, and run directly from a terminal, with a --subs-only flag to limit output to subdomains. It suits penetration testers and bug bounty hunters doing early reconnaissance who want a quick, scriptable way to enumerate attack surfaceattack surfaceThe exposed systems, interfaces and access points an attacker could try to use. It includes internet-facing services as well as identities, software and other reachable resources. before deeper scanning. It sits in the subdomain enumeration space alongside other passive recon utilities, doing one narrow job rather than bundling discovery with scanning. First committed in 2019 with four contributors and three tracked releases, but there have been no commits in the past year, so it looks stalled.
Find domains and subdomains related to a given domain - tomnomnom/assetfinder
How assetfinder helps
Which subdomains exist for a target domain that I have not discovered yet?
queries crt.sh, certspotter, hackertarget, threatcrowd, the Wayback Machine and other passive sources in one pass and prints every hostname they return, without touching the target directly
Have any of my domains got forgotten hosts sitting in certificate logs?
pulls historical certificate records from crt.sh and certspotter, surfacing names that were issued a certificate at some point even if they are no longer linked from anywhere live
What did a domain's DNS footprint look like in the past, not just now?
draws on the Wayback Machine's archived records, so a name that has since been taken down or repointed can still turn up
Can I narrow the output to just the subdomains before feeding it to another tool?
a single flag drops the base domain and any unrelated result, leaving a plain list of subdomains suited to piping straight into a scanner
Will adding my own API keys turn up names the default sources miss?
setting environment variables for Facebook, VirusTotal or Spyse enables those sources for the same run, adding whatever additional names they hold beyond the always-on sources
Languages
Command line
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for assetfinder, 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 → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
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 assetfinder 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…
Releases
Nothing shipped since we started watching. Releases and docs updates land here as they happen.
Project health
Issue, contributor and maintainer activity in tomnomnom/assetfinder, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 0 ±0 vs prior 12 months
- Maintainers 0 +0 joined · −0 left, last 12 months
- Bus factor 0 committers behind half the commits
- Community-filed 100% of issues opened, last 12 months
- Median time to close < 1 day first maintainer reply 0 hours
- Open backlog 27 of 41 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 27
- Contributors / month 0
- Commits / month 0
- Stars 3,684
- 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.We can only check tools that publish GitHub releases.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.
Choose a badge style and copy the code →