PAGES
← all tools
◆ Reconnaissance & OSINT

whatweb

v0.6.4 open-source

WhatWeb identifies websites, recognising web technologies including CMSCMSA web content management system for creating and managing digital content without writing code directly; cyber tools use CMS platforms to host documentation, portals, or reporting dashboards quickly., blogging platforms, JavaScript libraries, web servers, and embedded devices using over 1800 plugins.

Summary

whatweb is an open-source, GPLv2-licensed command-line scanner that identifies the technologies behind a website — CMS, blogging platforms, analytics packages, JavaScript libraries, web servers, and embedded devices — using over 1800 plugins, and can also surface version numbers, email addresses, account IDs, and SQL errors along the way. It's built for people doing recon work, whether that's a pentester profiling a target or someone auditing their own site's exposed stack, and it sits in the web-fingerprinting corner of reconnaissance tooling rather than broader vulnerability scanning. Scans run over both HTTP and HTTPSHTTPSHTTP carried over an encrypted TLS connection. It protects traffic in transit and lets a browser verify the server's certificate. automatically, support legacy 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./TLS for older targets, and can route through Tor for .onion domains. First committed in 2010 and still active, with 73 contributors and a release as recently as 141 days ago.

WhatWeb identifies websites, recognising web technologies including CMS, blogging platforms, JavaScript libraries, web servers, and embedded devices using over 1800 plugins.

How whatweb helps

What technologies is a website actually built on?

scans the target and reports back the CMS, web server, JavaScript libraries, and analytics packages it recognizes, matched against over 1800 plugins

Which exact software versions is a site running, and could that be exposed?

runs its plugins in a more thorough mode that digs for precise version strings instead of just naming the technology

Has a site leaked anything it shouldn't have, like email addresses or account IDs?

picks through page content and headers for those patterns and surfaces them alongside the fingerprint results

Are there embedded devices or SQL errors hiding in a set of sites I'm responsible for?

sweeps a list of hosts and flags SQL error text and known embedded-device signatures wherever its plugins match

Can I fingerprint a hidden service without leaking DNS lookups?

routes the scan through a proxy and skips DNS resolution for onion domains so the lookup itself doesn't reveal the target

Will an older or legacy server even respond to a modern scan?

negotiates legacy SSL/TLS versions alongside current ones so older targets that only speak outdated protocols still return a fingerprint

all 12 features, with the evidence for each →

Languages

Not documented

Features

12 capabilities

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

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

What whatweb offers you

  • Command-line interface3
  • Plugin system2
  • Plugin API support1
  • Scripting language support1
  • User-defined detection rules1
All capabilities 12 capabilities
Framework detection shipped suggested Identifies specific web technologies, CMS platforms, and server-side frameworks by analyzing page content, headers, and source code patterns. 22 releases · first seen Mar 2010

Suggested capability: Service and version detection. This is our guess, not confirmed.

Also counts toward: Scripting language support

release 22 total

  • Adds detection of Dell-OpenManage-Switch-Administrator v0.5.5 · Jan 2021 · source · release history
  • Adds Grafana plugin to detect Grafana monitoring dashboards. v0.5.4 · Dec 2020 · source · release history
  • Adds BlockScout plugin to detect BlockScout blockchain explorer instances. v0.5.4 · Dec 2020 · source · release history
  • Adds ElasticSearch plugin to detect Elasticsearch instances. v0.5.4 · Dec 2020 · source · release history
  • Adds Matomo plugin to detect Matomo analytics platform. v0.5.3 · Oct 2020 · source · release history
  • Adds AEM plugin to detect Adobe Experience Manager. v0.5.3 · Oct 2020 · source · release history
Request handling shipped Controls how HTTP requests are processed, including redirect following and URL construction patterns. 7 releases · 2 other sources · first seen May 2010

release 7 total

  • Adds --cookie-jar=FILE to load cookies from a file in document.cookie format v0.5.0 · Oct 2019 · source · release history
  • Adds -u and --user flags for HTTP basic authentication support. 0.4.6 · Mar 2011 · source · release history
  • Adds redirect control via internal option (values: never, http-only, meta-only, same-site, same-domain, always). 0.4.6 · Mar 2011 · source · release history
  • Adds -H or --header flags to send custom headers; can specify multiple times (e.g., 'foo:bar'). 0.4.6 · Mar 2011 · source · release history
  • Adds --max-redirects flag to control the maximum number of contiguous redirects followed. 0.4.6 · Mar 2011 · source · release history
  • Adds --url-prefix, --url-suffix, and --url-pattern flags to control how target URLs are constructed 0.4.5 · Aug 2010 · source · release history

example

  • Load session cookies from a local file for authenticated scanning whatweb --cookie-jar=/path/to/cookies.txt <target> v0.5.0 · Oct 2019 · source
  • Scan a site without following redirect chains to analyze the initial response body whatweb --no-redirect http://example.com 0.4.3 · May 2010 · source
MongoDB logging shipped Allows storing scan results directly into a MongoDB database for centralized aggregation. 2 releases · 2 other sources · first seen Mar 2011

release

  • Adds --output-elasticsearch to export scan results to Elasticsearch v0.4.9 · Nov 2017 · source · release history
  • Adds --log-mongo-database, --log-mongo-host, --log-mongo-collection, --log-mongo-username, and --log-mongo-password flags for MongoDB logging output. 0.4.6 · Mar 2011 · source · release history

example

  • Export scan results directly to an Elasticsearch cluster for centralized indexing. whatweb --output-elasticsearch http://localhost:9200/target v0.4.9 · Nov 2017 · source
  • Log scan results directly to a MongoDB instance for centralized collection aggregation. whatweb --log-mongo-database scans --log-mongo-host localhost --log-mongo-collection targets http://example.com 0.4.6 · Mar 2011 · source
Output formatting shipped Formats scan results in structured formats such as XML or modified string representations for easier parsing. 3 releases · 1 other source · first seen Mar 2010

release

  • Adds XML stylesheet whatweb.xsl for formatting XML reports. 0.4.6 · Mar 2011 · source · release history
  • Adds JSON logging support (requires json ruby gem or Ruby 1.9). 0.4.6 · Mar 2011 · source · release history
  • Output format changed from single quotes to square brackets for all strings 0.4 · Mar 2010 · source · release history

example

  • Capture tool output and version information in a structured XML format for downstream processing whatweb --log-xml report.xml http://example.com 0.4.3 · May 2010 · source
Plugin extensibility shipped Allows users to define custom detection logic via dedicated directories or command-line arguments, separate from core tools. 2 releases · 2 other sources · first seen May 2010

Also counts toward: Command-line interface, User-defined detection rules, Plugin system

release

  • Adds --custom-plugin flag to define detection logic directly on the CLI 0.4.5 · Aug 2010 · source · release history
  • Adds my-plugins/ folder support to keep personal plugins separate from core 0.4.3 · May 2010 · source · release history

example

  • Define a one-off detection rule for a specific text string on the command line. whatweb --custom-plugin "{:text=>'powered by abc'}" -i ./targets 0.4.5 · Aug 2010 · source
  • Store custom detection logic in a dedicated directory separate from WhatWeb's core plugins mkdir -p ~/my-plugins && echo '# My Plugin' > ~/my-plugins/my_custom.plg 0.4.3 · May 2010 · source
Heuristic detection shipped Detects unknown or unlisted systems by generating structural hashes from HTML elements, headers, and page footers. 3 releases · 1 other source · first seen Apr 2010

Shared capability: Attack surface inventory

Also counts toward: Plugin system

release

  • Adds div-span-structure plugin that generates a signature hash from div and span tag structures. 0.4.2 · Apr 2010 · source · release history
  • Adds header-hash plugin that creates a hash of the first 500 characters to help identify unknown systems. 0.4.2 · Apr 2010 · source · release history
  • Adds footer-hash plugin that hashes the last 500 characters if page length exceeds 1000, aiding identification of unknown systems. 0.4.2 · Apr 2010 · source · release history

example

  • Scan a target to identify unknown systems using content hashing plugins whatweb --plugin=header-hash,footer-hash,div-span-structure https://example.com 0.4.2 · Apr 2010 · source
Advanced output control shipped Provides mechanisms to suppress console output and direct logs to external systems like MagicTree. 2 releases · first seen Mar 2011

Also counts toward: Command-line interface

release

  • Adds --quiet and -q flags to suppress Brief Output on stdout. 0.4.6 · Mar 2011 · source · release history
  • Adds nmap-style IP address range support for target specification. 0.4.6 · Mar 2011 · source · release history
Tool information shipped Provides access to tool version details, plugin authorship metadata, and other introspection data. 2 releases · first seen May 2010

Also counts toward: Command-line interface

release

Proxy support shipped Routes outbound scan requests through an HTTP proxy to facilitate anonymization or network routing requirements. 1 release · 1 other source · first seen Apr 2010

release

example

  • Scan a site through an HTTP proxy to identify frameworks like SilverStripe or HTML5 features. whatweb --proxy=http://proxy:8080 http://example.com 0.4.1 · Apr 2010 · source
Target expansion shipped Supports complex target specification including IP address ranges. 1 other source · first seen Mar 2011

example

  • Scan a site requiring authentication while respecting rate limits to avoid bans. whatweb -u 'admin:password' --wait 2 http://example.com/admin 0.4.6 · Mar 2011 · source
Batch scanning shipped Processes multiple targets or specific URL patterns in a single execution pass. 1 other source · first seen Aug 2010

example

  • Scan a list of targets for specific URL patterns without hardcoding them in config. whatweb --url-pattern 'example.com/%s%.html' -i target_list.txt 0.4.5 · Aug 2010 · source
Detection confidence shipped Assigns certainty levels to detection results using a standardized confidence keyword and value system. 1 release · first seen Jun 2010

Also counts toward: Plugin API support

release

  • :certainty keyword replaces :probability in plugins, defaulting to 100 0.4.4 · Jun 2010 · source · release history

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

Show

19 entries

  1. April 20261
  2. October 20251
  3. August 20252
  4. January 20211
  5. December 20201
  6. October 20201
  7. June 20201
  8. February 20201
  9. October 20191
  10. November 20171
  11. April 20111
  12. March 20111
  13. August 20101
  14. June 20101
  15. May 20101
  16. April 20102
  17. March 20101
    Show

    19 entries

    Project health

    Issue, contributor and maintainer activity in urbanadventurer/WhatWeb, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 4 +2 vs prior 12 months
    2. Maintainers 2 +1 joined · −0 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed 100% of issues opened, last 12 months
    5. Median time to close 6.1 years first maintainer reply 113 days
    6. Open backlog 41 of 222 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 41
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars 6,846
    Issue themes, last 12 months
    • features 25%
    • other 75%

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

    Where whatweb 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

    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 →
    browse all tools → score card for your toolchain →