web-check
2.3.0 open-sourceThe section your link pointed to isn't on web-check's page any more, so we've brought you to the top.
Web-Check is an open source tool that provides on-demand intelligence for any website, uncovering server architecture, security configurations, and technologies in use.
PORTS_TO_CHECK=80,443,8080 web-check <target_url>
Summary
web-check is an open-source reconnaissance tool, released under an open license, that runs scans against a given website to surface how it's built and where it might be exposed — IP info, SSLSSLA cryptographic protocol for encrypting network connections, now deprecated in favor of TLS but whose name persists colloquially. Cyber tools reference it when handling HTTPS or other encrypted-channel inspection and termination. configuration, DNS records, open ports, headers, cookies, traceroute, subdomains, and known vulnerabilities or advisories. It can be used via a hosted demo or deployed yourself, with documented paths to Netlify, Vercel, Docker, Render, or running from source, which suits security researchers or developers who want it wired into their own infrastructure rather than relying on someone else's instance. It sits in the OSINTOSINTOpen-source intelligence, collecting and analyzing information from publicly available sources. Investigators use it to learn about people, infrastructure or threats. and attack-surface reconnaissance space, aimed at anyone assessing a site's exposure rather than at a single named alternative. Recent additions include a vulnerabilities panel with WAFWAFA reverse proxy that inspects HTTP/HTTPS traffic and blocks requests matching known attack patterns such as SQL injection or XSS, sitting between clients and a web application to filter malicious input before it reaches the server. detection and per-check configuration, suggesting active, ongoing development.
Web-Check is an open source tool that provides on-demand intelligence for any website, uncovering server architecture, security configurations, and technologies in use.
How web-check helps
Which parts of a site's stack are visible to anyone who looks?
fingerprints server architecture, headers, cookies and technologies in use and lists them in one report
Is this domain's SSL configuration sound?
inspects the certificate chain and configuration and flags weaknesses in how it's set up
Which ports are open on this host, and what does that expose?
scans for open ports and reports what's reachable on each
What does this site's DNS actually say, and does it match what I expect?
pulls DNS records and lays them out for comparison against the intended setup
Are there subdomains attached to this domain that I didn't know about?
runs a subdomain lookup and lists what it finds beyond the main host
Is this site sitting behind a WAF, and does it have known vulnerabilities on record?
checks for WAF presence and cross-references the target against security advisories, surfacing both in a dedicated panel
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 web-check, 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 web-check 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
4 entries
No entries match these filters.
- October 20261
- July 20261
- May 20261
- April 20251
Project health
Issue, contributor and maintainer activity in lissy93/web-check, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 11 +6 vs prior 12 months
- Maintainers 1 +0 joined · −1 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 100% of issues opened, last 12 months
- Median time to close 655 days first maintainer reply 95 days
- Open backlog 5 of 150 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 5
- Contributors / month 3
- Commits / month 4
- Stars 34,840
- 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.