getallurls
v2.2.1 open-sourceThe section your link pointed to isn't on getallurls's page any more, so we've brought you to the top.
getallurls (gau) fetches known URLs from AlienVault's Open Threat Exchange, the Wayback Machine, Common Crawl, and URLScan for any given domain.
getallurls --timeout 5s https://example.com getallurls -b '.js,.css,.png' example.com getallurls -p http://proxy.internal:8080 example.com
Summary
getallurls (gau) is an open-source command-line tool, MIT-licensed, that fetches known URLs for a given domain from AlienVault's Open Threat Exchange, the Wayback Machine, Common Crawl, and URLScan. It takes a domain or list of domains on stdin, spawns worker threads to query these sources in parallel, and writes results to a file or stdout, with flags to filter by status code, mime-type, date range, or file extension, and to fold duplicate parameter variants of the same endpoint. It suits penetration testers and bug bounty hunters building a target's URL inventory before deeper scanning, and its README credits Tomnomnom's waybackurls as its inspiration, positioning it as a multi-source alternative. First committed in 2020 with 20 contributors and 13 tracked releases, it has seen only one commit in the past year and no release in 662 days, suggesting maintenance has slowed considerably.
getallurls (gau) fetches known URLs from AlienVault's Open Threat Exchange, the Wayback Machine, Common Crawl, and URLScan for any given domain.
How getallurls helps
What URLs has this domain ever exposed publicly, including pages taken down long ago?
queries the Wayback Machine, Common Crawl, OTX, and URLScan in parallel and merges every historical URL each source has archived for the domain
Which subdomains and their URLs belong to this target so I can build a scanning list?
walks subdomains of the given domain when asked and folds every URL found under the same run, ready to pipe into another scanner
Are there old parameterized endpoints on this site worth testing that current crawlers no longer link to?
pulls URLs recorded at any past point in these archives, surfacing forgotten endpoints that live traffic and current sitemaps would never reveal
Which of these thousands of archived URLs are actually worth looking at rather than dead weight?
filters the merged list by status code or mime-type so only URLs matching or excluding specific responses or content types make it into the output
Did this domain's exposed URLs change within a specific time window I care about?
restricts the archive query to a start and end date, returning only URLs the sources recorded within that range
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 getallurls, 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 getallurls 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
7 entries
No entries match these filters.
- November 20232
- April 20221
- November 20211
- December 20201
- October 20201
- April 20201
Project health
Issue, contributor and maintainer activity in lc/gau, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 1 −2 vs prior 12 months
- Maintainers 0 +0 joined · −1 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 2.6 hours
- Open backlog 23 of 113 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 23
- Contributors / month 0
- Commits / month 0
- Stars 5,098
- 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.