Website Tech Stack Detector avatar

Website Tech Stack Detector

Pricing

from $0.70 / 1,000 analysed domains

Go to Apify Store
Website Tech Stack Detector

Website Tech Stack Detector

Find the stack behind any website: CMS, ecommerce platform, CDN, analytics and 3,500+ more fingerprints, with versions and per-hit evidence. From $1.00 per 1,000 domains, platform usage included.

Pricing

from $0.70 / 1,000 analysed domains

Rating

0.0

(0)

Developer

subimpact network

subimpact network

Maintained by Community

Actor stats

0

Bookmarked

3

Total users

2

Monthly active users

16 hours ago

Last modified

Features

Limited permissions

Share

Find out what a website is built with, one row per domain: CMS, ecommerce platform, CDN, analytics, tag managers, payment providers, hosting, JavaScript frameworks and more. Every detection carries a confidence score and, unless you turn it off, the exact evidence behind it (the response header, cookie, script URL, meta tag or HTML snippet).

3,588 fingerprint technologies from the MIT-licensed Wappalyzer 6.10.54 snapshot, plus 25 clean-room rules we wrote ourselves for things that snapshot misses, such as Payload CMS and Fastly.

What it does

  • Fetches one page per domain over plain HTTP, with no browser, so it is fast and cheap.
  • Reads every response header (including 103 Early Hints and redirect hops), cookies, meta tags, script URLs, inline scripts, raw HTML, the final URL and static CSS selectors.
  • Reports versions where the page exposes them (WordPress 7.1.5, WooCommerce 11.4.0, Magento 2, jQuery 3.5.1, Sentry 7.120.3).
  • Marks dead, parked, expired, off-site and blocked domains with a siteState instead of guessing, and never charges for them.
  • Optionally reads up to two more pages per domain (shop, blog, about, contact) when the homepage is thin.

Input

{
"domains": ["allbirds.com", "https://woocommerce.com/", "vercel.com", "coxandcox.co.uk"],
"maxPagesPerDomain": 1,
"includeEvidence": true,
"includeFeatures": false,
"minConfidence": 50,
"maxDomains": 100
}
FieldTypeDefaultNotes
domainslistallbirds.com, webflow.comBare domains or full URLs. Only the host is used, so example.com and www.example.com are one row. One unreadable entry becomes its own uncharged error row and the run continues.
maxPagesPerDomainnumber11 to 3. Extra pages are picked from same-site shop, blog, about or contact links and fetched one second apart.
maxDomainsnumber100Global cap. Domains past the cap are not fetched and not charged.
minConfidencenumber500 to 100. The default already drops detections that come only from a Content-Security-Policy allow-list.
includeEvidencebooleantrueTurn it off to make rows smaller.
includeFeaturesbooleanfalseAdds HSTS, HTTP/2, HTTP/3, Open Graph, PWA and RSS to a separate features list. They never count as technologies.
proxyConfigurationobjectemptyOptional. Most sites answer a plain request from Apify's servers. See Limits.

Output

One dataset item per domain, written as soon as that domain is analysed. This is a real row from coxandcox.co.uk, trimmed to two of its fourteen technologies:

{
"domain": "coxandcox.co.uk",
"inputUrl": "https://www.coxandcox.co.uk/",
"finalUrl": "https://www.coxandcox.co.uk/",
"statusCode": 200,
"siteState": "ok",
"pagesFetched": 1,
"technologies": [
{
"name": "Magento",
"slug": "magento",
"category": "Ecommerce",
"categories": ["Ecommerce"],
"version": "2",
"confidence": 100,
"evidence": ["type=\"text/x-magento-init\"", "/static/version1794967550/frontend/"],
"source": "subimpact-rules",
"website": "https://business.adobe.com/products/magento/magento-commerce.html"
},
{
"name": "Fastly",
"slug": "fastly",
"category": "CDN",
"categories": ["CDN"],
"version": null,
"confidence": 100,
"evidence": ["header x-served-by: cache-lhr-egwu1540075-LHR", "header x-timer: S1795083700.670329,VS0,VE3281"],
"source": "subimpact-rules",
"website": "https://www.fastly.com"
}
],
"technologyCount": 14,
"categories": {"Ecommerce": ["Magento"], "CDN": ["Fastly"]},
"cms": null,
"ecommerce": "Magento",
"cdn": ["Fastly"],
"analytics": [],
"features": [],
"fingerprintDatasetVersion": "wappalyzer-mit-6.10.54+subimpact-2026.11",
"checkedAt": "2026-11-20T04:50:14Z",
"error": null
}

cms, ecommerce, cdn and analytics are convenience columns for CSV users. siteState is one of ok, redirected-offsite, expired, parked, blocked, dns-error, timeout or http-error. Rows that are not ok, and rows with no technology, are never charged.

Pricing

  • $0.001 per analysed domain ($1.00 per 1,000 domains), platform usage included.
  • $0.0004 per extra page when maxPagesPerDomain is 2 or 3.
  • No start fee. A default run with the two prefilled domains costs $0.002.

You are only charged for a domain that answered, was analysed and produced at least one technology. Blocked, dead, timed-out, expired and empty domains produce a row with error or a siteState and cost nothing.

How this compares

Free-plan list prices on the Apify Store, read on 2026-11-20. This actor includes platform usage in its price; for competitors' usage terms, see each listing.

ActorPriceWhat you get
this actor$0.001 per domain, usage included, no start fee3,588 technologies plus clean-room rules, versions, confidence, per-hit evidence, live fetch
builtwith/builtwith-official-technology-scraper$0.002 per item ($2.00 per 1,000)BuiltWith's crawl database, not a live fetch, so it also shows DNS and NS records. No version, confidence or evidence
rl1987/wappalyzer-tech-lookupfrom $0.63 per 1,000 rows, one row per technology (roughly $6 or more per 1,000 domains)Wappalyzer API results, defaults to a residential proxy
scrapemint/website-tech-stack-detector$0.01 per detection row ($10 per 1,000)Live fetch with about 100 rules
motivational_nickel/website-technology-detector$0.0015 per item plus $0.002 per startLive fetch
automation-lab/tech-stack-detector$0.0023 per URL plus $0.035 per start"85+ technologies"
apivault_labs/tech-stack-lookup$0.003 per itemLive fetch
misterkhan/website-tech-stack-scanner$0.10 per itemLive fetch

Our price is half the lane leader's. The small live-fetch actors advertise about 85 to 100 rules; this one runs 3,588 fingerprints plus 25 clean-room rules, and it publishes the evidence behind every hit, which BuiltWith does not.

Limits

  • Plain HTTP, no JavaScript. The headline platform (CMS, ecommerce, CDN) came from plain HTTP on every reachable homepage we tested. What we cannot see: tags injected later by a tag manager (for example a pixel that only exists inside a Google Tag Manager container), 382 fingerprints that only expose a JavaScript global or an XHR endpoint, and versions that only exist as a JS global.
  • One to three pages per domain. A homepage has the platform; /shop or /blog occasionally adds a widget. We do not crawl further.
  • DNS is not visible. BuiltWith shows NS and DNS records (Route 53, Cloudflare DNS) from its own crawler. We read the response.
  • Some sites block datacenter IPs. In our fixture set 1 of 11 domains refused a datacenter IP (an Akamai-style reset followed by a timeout). Those rows come back as siteState: blocked and are not charged. If you hit them often, add a proxy in the input; residential traffic is billed separately by Apify and can cost more than the run.
  • The fingerprint snapshot is from January 2023 plus our own rules for the products that matter most. New products released after 2023 are only covered once we add a rule.
  • Expired and parked pages are reported from headers only, because the page body is not the buyer's site.

Responsible use

The actor fetches the public homepage of each domain you give it, plus at most two same-site pages, one second apart. That is normal browser-like traffic. Please keep it that way: do not point it at systems you are not allowed to query, and keep maxDomains in line with the sites you actually need. It does not log in, fill in forms or bypass access controls.

Data licence

Fingerprint data: Wappalyzer 6.10.54, MIT licence as declared in the package.json of that npm release, vendored unmodified with a NOTICE file. Additional rules are our own, written from vendor documentation and response headers we observed ourselves.