Bulk Website Tech Stack Detector (7,000+ technologies)
Pricing
Pay per event
Bulk Website Tech Stack Detector (7,000+ technologies)
Detect the technologies behind any list of websites (CMS, ecommerce platform, analytics, CDN, frameworks, versions) with ~7,700 open-source fingerprints, no browser. Schedule 'changes' mode to see which technologies each site added or dropped since the last run.
Pricing
Pay per event
Rating
0.0
(0)
Developer
Lindenbyte Studio
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
32 minutes ago
Last modified
Categories
Features
Share
Bulk Website Tech Stack Detector: 7,700 technologies, no browser, with change tracking
Paste a list of domains and get the technology stack of every website as clean spreadsheet-ready rows: CMS, ecommerce platform, analytics, tag managers, CDN, web server, frameworks, payment providers, chat widgets, marketing tools, with versions and a confidence score. Matching uses about 7,700 open-source fingerprints (the community webappanalyzer set, a fork of the Wappalyzer rules) and runs on plain HTTP: no browser, fast and cheap.
Then switch to changes mode and schedule it: each run tells you which technologies each site added or dropped since the last run (for example "just installed Shopify", "removed Intercom", "jQuery 3.5 to 3.7"). That is a ready-made trigger for lead generation, competitor monitoring and agency prospecting.
Use cases
- Lead generation: find every store on Shopify, WooCommerce or Magento, every site running HubSpot, Klaviyo or Stripe, from a list of prospects.
- Sales triggers: be told when a prospect adds or removes a tool you sell against or integrate with.
- Competitor monitoring: watch which analytics, payment, chat and marketing tools competitors adopt.
- Agency and SEO audits: bulk-check CMS, outdated library versions and tracking setup across client sites.
- Market research: market share of platforms inside a segment, built from your own domain list.
- Security hygiene: spot visible outdated versions (server, CMS, jQuery) on your own portfolio.
Input
| Field | What it does |
|---|---|
urls | Domains (example.com) or URLs. One analysis per domain, duplicates removed |
mode | detect (default) or changes (adds added / removed / version changes since the last run) |
includeCategories | Optional: keep only these categories, e.g. CMS, Ecommerce, Analytics, CDN |
stateKey | Name of the monitor for changes mode; different names keep separate memories |
concurrency | Sites analysed in parallel (default 5) |
requestTimeoutSecs | Per-site timeout (default 25) |
Example: weekly competitor tech watch
{"urls": ["competitor-a.com", "competitor-b.com", "https://competitor-c.com"],"mode": "changes","includeCategories": ["Ecommerce", "Analytics", "Marketing automation", "Payment processors"]}
Create a schedule (Console > Schedules) and connect an integration (email, Slack, webhook) to receive the rows where hasChanges is true.
Output
One row per domain (real example, filtered to three categories):
{"domain": "wordpress.org","url": "https://wordpress.org/","finalUrl": "https://wordpress.org/","status": "ok","httpStatus": 200,"technologies": [{ "name": "MySQL", "categories": ["Databases"], "version": null, "confidence": 100, "website": "https://mysql.com" },{ "name": "PHP", "categories": ["Programming languages"], "version": null, "confidence": 100, "website": "https://php.net" },{ "name": "WordPress", "categories": ["CMS", "Blogs"], "version": null, "confidence": 100, "website": "https://wordpress.org" }],"techCount": 3,"analyzedAt": "2026-11-13T20:09:25.650Z"}
In changes mode each row also has baseline (true on the first run for that domain), added, removed (technology names), versionChanged ({name, from, to}), hasChanges and previousCheck. Sites that fail (DNS error, timeout, HTTP 4xx/5xx, empty page) appear as status: "error" with the reason and are not charged. A run summary is saved to the key-value store record SUMMARY.
Pricing
Pay per site analysed: you pay for each website that was successfully fetched and analysed (also in changes mode), plus a small start fee per run. Failed sites are free. Set a max charge per run in the run options to cap your spend.
How detection works, and its limits (honest)
- The Actor downloads each page once (HTML, response headers, cookies) and matches it against the fingerprints: HTML patterns, response headers, cookies, script URLs, inline scripts, meta tags, URL patterns, page text and CSS selectors, plus "implies", "excludes" and "requires" rules and version extraction.
- No JavaScript is executed. Fingerprints that need a real browser (JavaScript globals such as
window.Shopify, network requests made after load, DNS records, TLS data) are not evaluated. Technologies that only reveal themselves that way can be missed, and sites that render everything client-side (some SPAs) show fewer technologies than a browser-based tool would find. - Only the page you give is analysed (the homepage for a bare domain), not the whole site.
- Some sites block non-browser requests (bot protection, HTTP 403); they are reported as errors and not charged.
- Detection is pattern-based: a match is strong evidence, not proof. Check
confidenceandversion. - In
changesmode a "change" can also be a difference in what the site served that time (A/B tests, geo or consent banners). State is kept in your account's named key-value storetech-stack-detector-state.
Legal and attribution
Public pages only: one standard page request per domain, like a browser visit. No personal data is collected. Not affiliated with, endorsed by or a reseller of Wappalyzer, BuiltWith or any website analysed.
Technology fingerprints come from the open-source enthec/webappanalyzer project, licensed under GPL-3.0, and are downloaded at build time from a pinned commit. All credit to its authors and contributors; the licence text is shipped with the Actor. Detection code and this Actor wrapper are by Lindenbyte.