loading
loading
Discovery
Go Wappalyzer port for bulk technology fingerprinting.
overview
webanalyze matches response headers, cookies, HTML, and scripts against an -apps definition file (technologies.json by default). Feed -host or -hosts; raise -worker for concurrent passes; emit stdout, csv, or json with -output.
Reach for it after subdomain discovery and liveness probing, when you need a technology map across many hosts rather than a deep single-site crawl. Use -crawl to follow a few links past the root when signatures only load on inner pages.
Trickest provides webanalyze as a managed Discovery node: host list in, folder and file out. Prefer httpx when liveness and light tech detection should share one probe. Prefer upstream Wappalyzer for deeper recursive analysis of one site.
use cases
Feed a file of hosts and let webanalyze fingerprint each one concurrently, raising the worker count to build a technology inventory for the whole estate in a single pass.
Report which sites run WordPress, Drupal, Adobe Experience Manager, or another platform, so you can group targets by stack and prioritize the ones that matter.
Choose CSV or JSON output so the detected technologies feed a database node or a routing step instead of scrolling past in a console.
Set a small crawl depth so detection catches libraries and frameworks that only load on pages past the root.
reference
| Name | Type | Flag | Description |
|---|---|---|---|
| host | STRING | -host | Single host to test. |
| hosts | FILE | -hosts | Filename with hosts, one host per line. |
| output-format | STRING | -output | Output format: stdout, csv, or json (default stdout). |
| workers | STRING | -worker | Number of workers to run in parallel (default 4). |
| crawl | STRING | -crawl | Links to follow from the root page (default 0). |
| app-definition-file | FILE | -apps | App definition file with technology signatures (default technologies.json). |
Showing key inputs. webanalyze exposes 7 inputs in total.
| Name | Type | Flag | Description |
|---|---|---|---|
| host | STRING | -host | Single host to test. |
| crawl | STRING | -crawl | Links to follow from the root page (default 0). |
| hosts | FILE | -hosts | Filename with hosts, one host per line. |
| workers | STRING | -worker | Number of workers to run in parallel (default 4). |
| output-format | STRING | -output | Output format: stdout, csv, or json (default stdout). |
| search-all-urls | BOOLEAN | -search | Search all URLs on the same base domain, e.g. example.com and sub.example.com (default true). |
| app-definition-file | FILE | -apps | App definition file with technology signatures (default technologies.json). |
example
# fingerprint a host list as JSON, crawling one link deepwebanalyze -hosts hosts.txt -worker 8 -output json -crawl 1http://example.com (0.38s): Cloudflare, (CDN) Nginx, (Web servers) Adobe Experience Manager, (CMS) jQuery, 3.7.1 (JavaScript libraries) Java, (Programming languages)http://shop.example.com (0.52s): Nginx, (Web servers) React, 18.2.0 (JavaScript frameworks) Webpack, (Miscellaneous)guidance
Use webanalyze when you need Wappalyzer-style fingerprinting across many hosts. For deep recursive analysis of a single site, prefer Wappalyzer. For liveness plus inline tech detection, use httpx.
Original Node tool. Deeper recursive analysis of one site; webanalyze favors bulk host lists.
Plugin-based identifier with aggression levels. Broader recon framing, similar detection goal.
Probes liveness and runs tech detection inline, so one node both filters and fingerprints.
faq
related
Extract URLs and endpoints from Android APK files.
Web path scanner.
Crawl pages, harvest potential parameters, write a custom wordlist.
Recursive content discovery with smart defaults and rich response filters.
Maintained gau fork for passive archive URL collection.
Extract JavaScript file URLs from a page or URL list.
A host list is probed live by httpx, then webanalyze fingerprints each one and writes the technology map as a queryable output.
Facts on this page come from the live Trickest tool library.