httprobe
open-sourceThe section your link pointed to isn't on httprobe's page any more, so we've brought you to the top.
Take a list of domains and probe for working HTTP and HTTPSHTTPSHTTP carried over an encrypted TLS connection. It protects traffic in transit and lets a browser verify the server's certificate. servers - tomnomnom/httprobe
Summary
httprobe is an open-source command-line tool that takes a list of domains piped in on stdin and probes each one for working HTTP and HTTPS servers, printing back the live URLs. It costs nothing to use and installs as a single Go binary or Docker container, run by feeding it domain lists rather than through any interface. This puts it in the hands of people doing reconnaissance work, such as bug bounty hunters and penetration testers narrowing a large domain list down to actual live hosts before deeper scanning. It fits the subdomain and web-discovery recon space, handling one narrow step in that pipeline rather than the whole workflow, with flags to tune concurrency, timeouts, custom ports, and whether HTTPS is preferred over plain HTTP. It has been around since 2017 with a small group of five contributors, but there have been no commits in the past year, so anyone adopting it should expect a stable, largely unmaintained tool rather than active development.
Take a list of domains and probe for working HTTP and HTTPS servers - tomnomnom/httprobe
How httprobe helps
Which of these thousands of subdomains actually have a web server behind them?
takes the domain list from stdin and returns only the ones that answer on standard HTTP or HTTPS ports, dropping every name that does not respond
Are these hosts reachable over plain HTTP, HTTPS, or both?
prints a separate live URL for each scheme that answers, so a host that works on both shows up twice with the scheme in front
Do any of these domains serve something on non-standard ports I'd otherwise miss?
checks additional protocol and port pairs given alongside the default probes and reports those as live URLs too
Which scheme should I bother scanning further when a host answers on both?
when told to favor HTTPS, only falls back to checking plain HTTP on a host once HTTPS on that host fails, cutting the live list down to one URL per host
Will a slow or unresponsive host stall the rest of my list?
gives up on a domain once it passes a set waiting period and moves to the next, so unreachable hosts don't hold up the final list
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 httprobe, 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 httprobe 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/httprobe, 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 not measured of issues opened, last 12 months
- Median time to close 3.2 years issues closed, last 12 months
- Open backlog 33 of 46 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 33
- Contributors / month 0
- Commits / month 0
- Stars 3,124
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.
Choose a badge style and copy the code →