subfinder
v2.16.0 open-sourceThe section your link pointed to isn't on subfinder's page any more, so we've brought you to the top.
Subfinder is a subdomain discovery tool that finds and returns valid subdomains for websites using passive online sources.
subfinder -d example.com -mr 100 -all
subfinder -d example.com -s scanmalware,crtsh -v
subfinder -ls -oJ
subfinder -d example.com -s shodanct
subfinder -d example.com -sources urlscan
subfinder -d example.com -stats
subfinder -d example.com -s hudsonrock
subfinder -dL targets.txt
# targets.txt example:
# Production targets
example.com
# Staging
staging.example.org
subfinder -d example.com -s facebook
subfinder -d example.com -rls "crtsh=10/s,shodan=1/s"
subfinder -d example.com -src digitorus
package main
import (
"fmt"
subfinder "github.com/projectdiscovery/subfinder/v2/pkg/runner"
)
func main() {
options := subfinder.Options{}
runner, _ := subfinder.NewRunner(&options)
runner.RunEnumerationWithCallback("example.com", func(result string) {
fmt.Println(result)
})
}
subfinder -update
package main
import (
"fmt"
"github.com/projectdiscovery/subfinder/v2/pkg/runner"
)
func main() {
opts := runner.Options{
// ... set options ...
}
r, err := runner.NewRunner(&opts)
if err != nil {
panic(err)
}
// Register a callback function to process results
r.Callback = func(result string) {
fmt.Println("Found:", result)
}
r.RunEnumeration()
}
subfinder -d example.com -source fofa,c99,chinaz -rate-limit 10
subfinder -d example.com -proxy http://127.0.0.1:8080 -b 192.168.1.50
subfinder -d example.com -s sonarsearch
subfinder -d example.com -resolve -r 8.8.8.8,1.1.1.1
subfinder -d example.com -recursive
subfinder -ls
subfinder --version
Summary
Subfinder is an open-source command-line tool that discovers subdomains for a given website using passive online sources rather than active probing, which keeps it fast and stealthy. It runs as a single binary, taking a domain or a list of domains as input and returning results to stdout, a file, or JSON for piping into other tools, and it also ships as a Go library for programmatic use. It's aimed at penetration testers and bug bounty hunters doing reconnaissance rather than continuous monitoring teams, and it sits in the passive subdomain enumeration category, pulling from dozens of curated sources such as certificate transparency logs, Shodan, and URLScan.io. First committed in 2018, it has 137 contributors and a release roughly every couple of weeks, with the most recent 16 days ago.
Subfinder is a subdomain discovery tool that finds and returns valid subdomains for websites using passive online sources.
How subfinder helps
Which subdomains exist for a target domain that certificate logs, Shodan, and other public sources have already recorded?
queries dozens of curated passive sources in one pass and returns the deduplicated list of valid subdomains found, without sending a single probe to the target itself
Which of my recon runs are missing coverage because a source went quiet or was pulled?
tracks per-source request counts in its stats output and flags where a formerly-used source (like a removed provider) is silently contributing nothing
Is a subdomain result hiding behind a wildcard DNS record instead of being a real host?
runs a wildcard elimination module during resolution and marks wildcard certificate matches in the JSON output so they can be filtered from the real finds
Which passive sources actually contributed to a given enumeration, and how heavily was each queried?
the statistics output breaks down request counts and results by source, showing which ones are doing the work and which are rate-limited or idle
Which sources are currently available to query, and has that list changed since my last scan?
can print the full source list in a machine-readable format, which scripts or audits can diff against a previous run to catch sources that were added or removed between releases
Languages
Command line
No command matches.
| 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 subfinder, 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 subfinder 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…
Commercials
pricing & packaging history · ProjectDiscovery vendor page23 readings of ProjectDiscovery's pricing page since Feb 2024, with 7 relaunches of its plan lineup and 4 changes to what its plans include — each one dated, compared with the reading before it, and explained for someone buying the tool.
Pricing and packaging history is included with Researcher and Business. See how every vendor we track sells, and how that has changed over time, using data we don't publish anywhere else.
See plans → Already subscribed? Sign in →Plans by offering
Each offering on the pricing page links to its own page of plans, read at its latest capture.
Plan relaunches
Plans, prices and descriptions are quoted from the vendor's own pricing page as we read it on each date. A plan missing from a later reading is shown as no longer listed on the page — a statement about the page, not the product. Readings that failed to show any plans are left out rather than read as a change.
Website history
projectdiscovery.io, every changeProjectDiscovery's home page and 3 more pages as they looked each month from August 2021 to October 2026: 18 renders, 4 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
See plans → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Releases
34 entries
No entries match these filters.
- August 20262
- April 20261
- March 20261
- January 20261
- December 20251
- November 20251
- September 20251
- June 20251
- February 20251
- January 20251
- October 20241
- January 20241
- September 20231
- August 20231
- June 20231
- May 20232
- March 20231
- February 20231
- November 20221
- October 20221
- August 20221
- April 20221
- March 20221
- September 20211
- February 20211
- September 20202
- August 20201
- July 20201
- January 20201
- June 20181
- May 20181
Project health
Issue, contributor and maintainer activity in projectdiscovery/subfinder, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 30 +13 vs prior 12 months
- Maintainers 10 +9 joined · −3 left, last 12 months
- Bus factor 4 committers behind half the commits
- Community-filed 68% of issues opened, last 12 months
- Median time to close 4.6 days first maintainer reply 46 hours
- Open backlog 1 of 562 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 1
- Contributors / month 4
- Commits / month 9
- Stars 14,470
- bugs 33%
- features 26%
- other 41%
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
Articles
1 article · updated Nov 4, 2026Where subfinder turns up in what others publish: how-tos, attack reports that name it, and incident write-ups. A row says why it is here and quotes where the article names it; the link goes to the publisher.
Breach post-mortems & incident response 1
-
Gaming the system: how a Chinese-speaking actor turned Brazilian government sites into an SEO weapon
subfinder – takes root domains, resolvers, and a depth, then enumerates subdomains via DNS brute force, certificate transparency, and passive sources, returning the discovered subdomains.
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.
Choose a badge style and copy the code →