PAGES
← all tools
◆ Reconnaissance & OSINT

urlfinder

v0.0.3 open-source

Free plan: not checked yet · Open source: yes

URLFinder is a high-speed, passive URL discovery tool that gathers URLs for web asset discovery without active scanning.

What you can do now

Checking Plays…

Summary

urlfinder is an MIT-licensed open-source reconnaissance command-line tool that passively discovers URLs from curated sources, aimed at penetration testers, bug bounty hunters, and security researchers. You install it with Go or use a precompiled binary, then provide a domain or domain list; results can be written as JSONLJSONLA text format where each line is a self-contained, valid JSON object, making it easy to stream, append, and process large datasets line by line without parsing a full JSON array into memory., files, or standard output for pipeline use. Its distinctive control is scope handling: regexes and fields such as registered domain or fully qualified domain name determine what it follows, excludes, or displays externally, with VirusTotal among its sources. The README shows ongoing releases.

URLFinder is a high-speed, passive URL discovery tool that gathers URLs for web asset discovery without active scanning.

How urlfinder helps

Which URLs are associated with my target domain?

passively gathers URLs from curated sources, including VirusTotal, without actively scanning the target

Which web assets can I discover without sending active scans?

collects URLs from passive sources, so the results reflect available source data rather than responses from an active probe

Which discovered URLs fall within my intended scope?

follows URLs matching supplied patterns and applies domain, registered-domain, fully qualified domain, or custom-regex scope rules

Which third-party or unrelated URLs should I exclude from my results?

filters discovered URLs using out-of-scope patterns or host-based scope settings, though excluded sources cannot appear in the final results

Which external endpoints did scoped discovery encounter?

surfaces out-of-scope endpoints found while following in-scope URLs when external results are enabled

How can I pass the discovered URLs into my existing workflow?

emits results to standard output, files, or structured JSONL, and accepts domain input from a list or pipeline; it does not validate that every URL is live

all 5 features, with the evidence for each →

Languages

Not documented

Features

5 capabilities

Built from urlfinder'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 →

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

What urlfinder offers you

  • Command-line interface1
  • JSON data export1

All capabilities 5 capabilities
Crawl scope control suggested Lets users define in-scope and out-of-scope boundaries for crawling by field type, custom regex patterns, or by disabling host-based scoping entirely, and can surface out-of-scope endpoints discovered during a scoped crawl. 5 releases · 4 other sources · first seen Mar 2025

Suggested capability: Attack surface inventory. This is our guess, not confirmed.

Also counts toward: Command-line interface

URL filtering and matching Lets users include or exclude URLs based on patterns, with support for combined match/filter rules and file-based pattern lists. 3 other sources
Passive URL discovery Collects URLs from passive sources, including VirusTotal, without sending active requests to the target. 1 release · 1 other source · first seen Nov 2024

Shared capability: Attack surface inventory

Active URL enumeration Enumerates URLs for a given domain by sending requests directly to the target. 1 other source

Shared capability: Attack surface inventory

JSONL output Outputs results in JSONL format for downstream processing. 1 other source

Also counts toward: JSON data export

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 urlfinder, 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 urlfinder 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

2 entries

  1. March 20251
  2. November 20241

    2 entries

    Project health

    Issue, contributor and maintainer activity in projectdiscovery/urlfinder, 2023-12 – 2026-11, as of 2026-11-03. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors not measured distinct committers, last 12 months
    2. Maintainers not measured core set, last 12 months
    3. Bus factor not measured committers behind half the commits
    4. Community-filed 50% of issues opened, last 12 months
    5. Median time to close 2.7 days first maintainer reply 2.7 days
    6. Open backlog 1 of 23 issues ever filed
    1. Issues opened / month 0 · 1 communitymaintainers
    2. Open backlog 1
    3. Contributors / month not measured
    4. Commits / month not measured
    5. Stars not measured
    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 →
    Saved in this browser. Sign in to sync your tools.