# Website Tech Stack Detector

Website Tech Stack Detector fetches a domain over plain HTTP and returns one JSON row listing every technology it recognises, with name, slug, category, version where exposed, a confidence score and the header, cookie, script URL or HTML snippet behind the hit. It runs 3,588 Wappalyzer fingerprints plus 25 additional rules, and costs $0.001 per analysed domain ($1.00 per 1,000). Run it in the Apify Console, via the API or as an MCP tool.

## Key facts

- Price: from $0.001 per analysed domain, $1.00 per 1,000, down to $0.0007 on higher Apify plans
- Pricing model: Pay per event
- Output: JSON, CSV, Excel, XML, RSS via Apify datasets
- Access: Apify Console, REST API, Python and JS clients
- Version: Updated Nov 2026, build 0.1.3
- Actor: subimpact/website-tech-stack-detector

## Who it is for

- Agencies qualifying prospects by the platform they already run
- Sales teams filtering Shopify, WooCommerce or WordPress accounts
- Market researchers sizing a stack across thousands of domains
- SEO and analytics consultants auditing tags and CDNs

## Use cases

### Build a platform-segmented lead list

Paste domains into the input and read the ecommerce and cms convenience columns, which exist so a CSV opens with the answer in one field. Filter to WooCommerce shops and you have a list of merchants whose plugin stack you can support, with technologyCount and the full technologies array as the supporting detail. Domains that never answered come back with a siteState and are not charged.

### Prove the detection to a client

With includeEvidence on, every detection carries the exact header, cookie, script URL, meta tag or HTML snippet that triggered it. A row saying Magento 2 with the text/x-magento-init marker and the static version path is evidence a client can check, rather than a label they have to trust. Set minConfidence to raise the bar and drop weaker guesses.

### Audit analytics and tag coverage

The analytics and cdn columns group detections by category, and includeFeatures adds HSTS, HTTP/2, HTTP/3, Open Graph, PWA and RSS to a separate features list that never counts as a technology. That pairing shows whether a site has modern transport but no PWA, or a CDN but no tag manager, which is the gap a consulting pitch usually starts from.

### Read deeper on thin homepages

Some homepages show little. Set maxPagesPerDomain to 2 or 3 and the Actor fetches same-site shop, products, collections, blog, about or contact pages, one second apart, for an extra $0.0004 per page. That often surfaces the ecommerce platform or the checkout widget that the landing page hides, and pagesFetched records what was read.

### Screen a domain list before outreach

siteState distinguishes ok from parked, expired, blocked, dns-error, timeout and http-error, and only ok rows with at least one technology are charged. Point the Actor at a purchased list and you find out which domains are actually live businesses before anyone emails them. maxDomains caps the run so a large list cannot overspend.

## Price events

- Analysed domain (`domain`): $0.001, lowest tier $0.0007. One domain that answered and was analysed (siteState ok with at least one technology detected). Platform usage included. Blocked, dead, expired and empty domains are not charged.
- Extra page (`extra-page`): $0.0004, lowest tier $0.00028. One page beyond the homepage that was fetched and analysed (only when pages per domain is 2 or 3). Platform usage included.

Prices from the Apify Store. Apify shows the final price before each run.

## How it compares with other Apify actors

Price per 1,000 domains at Apify Store list prices, checked 20 Nov 2026.

| Actor | Price per 1,000 domains (Free plan) | Higher plans (Gold) | Start fee per run | Platform usage | Users | Rating | Last build |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Website Tech Stack Detector (this API) | $1.00 | $0.7 | None | Included | 3 | No reviews yet | 20 Nov 2026 |
| [BuiltWith Official Technology Scraper](https://apify.com/builtwith/builtwith-official-technology-scraper) | $2.00 | $2.00 | None | Included | 812 | 5.0 (5 reviews) | 20 Mar 2026 |
| [Website Tech Stack Detector (Wappalyzer API Scraper)](https://apify.com/rl1987/wappalyzer-tech-lookup) | Charges per technology row, so a domain with many detections costs several rows. | Same unit, see the first price column | None | Included | 78 | No reviews yet | 14 Nov 2026 |
| [Website Technology Stack Detector (BuiltWith Alternative)](https://apify.com/scrapemint/website-tech-stack-detector) | $10.00 | $10.00 | None | Included | 168 | No reviews yet | 9 Nov 2026 |
| [Tech Stack Detector](https://apify.com/automation-lab/tech-stack-detector) | $2.30 | $1.20 | None | Included | 428 | No reviews yet | 18 Nov 2026 |
| [Website Tech Stack Scanner | Website Technology Detector](https://apify.com/misterkhan/website-tech-stack-scanner) | $100.00 | $70.00 | None | Included | 519 | 5.0 (3 reviews) | 4 Nov 2026 |

### Where BuiltWith Official Technology Scraper is stronger

- Draws on BuiltWith's own crawl database rather than a live page fetch
- Also surfaces DNS and name server records from that crawl data
- A long established index that can cover sites a live fetch cannot reach

### Where this API is stronger

- Reports versions, confidence and the evidence behind each detection
- Runs a live fetch, so the row reflects the site as it stands today
- Charges only for domains with at least one technology detected

### Where Website Tech Stack Detector (Wappalyzer API Scraper) is stronger

- Uses the Wappalyzer rule set, which many teams already recognise
- Returns traffic rank and a confirmed date with each technology
- Flat rows with one technology each, simple to load into a spreadsheet

### Where this API is stronger

- Charges per domain rather than per technology row
- Reports a confidence score and the page evidence for each hit
- Blocked, dead and empty domains are not charged at all

### Where Website Technology Stack Detector (BuiltWith Alternative) is stronger

- Very simple input, a list of websites with no options to configure
- Returns evidence for detections in a single row per domain

### Where this API is stronger

- Fingerprint set covers thousands of technologies rather than about a hundred rules
- Second and third pages per domain can be scanned with a page event
- Confidence thresholds and evidence fields can be switched on per run

### Where Tech Stack Detector is stronger

- Can detect email provider and SaaS tools from DNS records
- Returns response headers, server and generator fields per site
- Failed URLs are not charged

### Where this API is stronger

- Fingerprint set covers thousands of technologies rather than about eighty five
- Confidence scores and per hit evidence are returned by default
- No separate run start charge on top of the per domain event

### Where Website Tech Stack Scanner | Website Technology Detector is stronger

- Advertises a very large fingerprint set of its own
- Groups detections into marketing and analytics categories inside each row

### Where this API is stronger

- Reports versions, confidence scores and evidence for every technology
- Charges only for domains where at least one technology was detected
- Optional second and third pages per domain can be scanned

Technology lookups split between live fetches and indexed databases. BuiltWith suits teams that value historical crawl data and DNS records, while the smaller live actors are simple to run but cover a narrow rule set. This actor sits in the live fetch group with a much larger fingerprint set, per hit evidence and charging that skips dead or blocked domains.

Prices are Apify Store list prices, checked 20 Nov 2026. Platform usage 'Paid separately' means Apify bills compute on top of the event price. Check each listing before you buy.

## Input

- `domains` (array, optional): Websites to analyse. Bare domains (allbirds.com) or full URLs (https://www.coxandcox.co.uk/) both work. Only the host is used for de-duplication: one row per domain. One unreadable entry costs only that entry, never the run.
- `maxPagesPerDomain` (integer, optional): How many pages to read per domain (1-3). 1 = the homepage only, which finds the platform for almost every site. 2 or 3 adds same-site /shop, /products, /collections, /blog, /about or /contact pages, fetched one second apart, and each ext...
- `minConfidence` (integer, optional): Drop detections below this confidence (0-100). The default of 50 already removes hits that come only from a Content-Security-Policy allow-list, because an allow-list is not usage.
- `includeEvidence` (boolean, optional): Adds the header, cookie, script URL, meta tag or HTML snippet behind each detection. Turn it off to shrink rows.
- `includeFeatures` (boolean, optional): Also report generic protocol facts (HSTS, HTTP/2, HTTP/3, Open Graph, PWA, RSS) in a separate features list. They are never counted as technologies.
- `maxDomains` (integer, optional): Global cap on domains fetched in one run (1-100000). Bill-shock guard: anything past the cap is not fetched and not charged.
- `proxyConfiguration` (object, optional): Optional. Most sites answer a plain request from Apify's servers, so no proxy is the cheapest and fastest choice. Add a proxy only for domains that block datacenter IPs: those rows come back with siteState "blocked" and are not charged. ...

### Example input

```json
{
  "domains": [
    "allbirds.com",
    "webflow.com"
  ]
}
```

## Output fields

- `domain` (string/null): Host that was analysed (e.g. coxandcox.co.uk). Null on rows for an unreadable list entry.
- `inputUrl` (string/null): URL the run fetched for this row, or the raw list entry on an unreadable-entry row
- `finalUrl` (string/null): URL after redirects; null when nothing was fetched
- `statusCode` (integer/null): Status of the final response hop; null when no response arrived
- `siteState` (string/null): ok, redirected-offsite, expired, parked, blocked, dns-error, timeout or http-error. Only ok rows are charged.
- `pagesFetched` (integer): Pages analysed for this domain (homepage plus, when maxPagesPerDomain > 1, the extra same-site pages)
- `technologies` (array/null): One object per detected technology: name, slug, category, categories, version, confidence, evidence, source and website. Empty on rows that were not analysed.
- `technologyCount` (integer): Number of detected technologies (protocol features are not counted)
- `categories` (object/null): Category name mapped to the technologies found in it, e.g. {"Ecommerce": ["Magento"], "CDN": ["Fastly"]}
- `cms` (string/null): Convenience column: the first CMS, site builder or page builder found (WordPress, Shopify is under Ecommerce, Webflow, Wix, Squarespace...)
- `ecommerce` (string/null): Convenience column: the first ecommerce platform found (Shopify, WooCommerce, Magento, BigCommerce...)
- `cdn` (array/null): Every CDN detected (Cloudflare, Fastly, CloudFront, jsDelivr, cdnjs...)
- `analytics` (array/null): Every analytics tool detected (Google Analytics, Adobe Analytics, Matomo, Plausible...)
- `features` (array/null): Only filled when includeFeatures is on: HSTS, HTTP/2, HTTP/3, Open Graph, PWA, RSS and similar facts that are not part of the buyer's stack
- `fingerprintDatasetVersion` (string/null): Version of the fingerprint data used for this row
- `checkedAt` (string/null): ISO 8601 UTC timestamp of the run
- `error` (string/null): Reason the domain or list entry could not be analysed; rows with an error are never charged

## Sample output

Trimmed from one of our own test runs. Personal data is redacted.

```json
[
  {
    "domain": "webflow.com",
    "inputUrl": "https://webflow.com/",
    "finalUrl": "https://webflow.com/",
    "statusCode": 200,
    "siteState": "ok",
    "pagesFetched": 1,
    "technologies": [
      {
        "name": "cdnjs",
        "slug": "cdnjs",
        "category": "CDN",
        "categories": [
          "CDN"
        ],
        "version": null,
        "confidence": 100,
        "evidence": [
          "script https://cdnjs.cloudflare.com/ajax/libs/three.js/r128/three.min.js"
        ],
        "source": "wappalyzer-mit-6.10.54",
        "website": "https://cdnjs.com"
      },
      {
        "name": "Cloudflare",
        "slug": "cloudflare",
        "category": "CDN",
        "categories": [
          "CDN"
        ],
        "version": null,
        "confidence": 100,
        "evidence": [
          "header cf-ray: a5d51efddd756064-IAD"
        ],
        "source": "subimpact-rules",
        "website": "https://www.cloudflare.com"
      },
      {
        "name": "Google Hosted Libraries",
        "slug": "google-hosted-libraries",
        "category": "CDN",
        "categories": [
          "CDN"
        ],
        "version": null,
        "confidence": 100,
        "evidence": [
          "script https://ajax.googleapis.com/ajax/libs/webfont/1.6.26/webfont.js"
        ],
        "source": "wappalyzer-mit-6.10.54",
        "website": "https://developers.google.com/speed/libraries"
      },
      "..."
    ],
    "technologyCount": 10,
    "categories": {
      "CDN": [
        "cdnjs",
        "Cloudflare",
        "Google Hosted Libraries",
        "..."
      ],
      "Font scripts": [
        "Google Font API"
      ],
      "JavaScript graphics": [
        "three.js"
      ],
      "JavaScript libraries": [
        "jQuery"
      ],
      "Security": [
        "reCAPTCHA"
      ],
      "Tag managers": [
        "Google Tag Manager"
      ],
      "Website builder": [
        "Webflow"
      ]
    },
    "cms": "Webflow",
    "ecommerce": null,
    "cdn": [
      "cdnjs",
      "Cloudflare",
      "Google Hosted Libraries",
      "..."
    ],
    "analytics": [],
    "features": [],
    "fingerprintDatasetVersion": "wappalyzer-mit-6.10.54+subimpact-2026.11",
    "checkedAt": "2026-11-20T05:41:25.818Z",
    "error": null
  },
  {
    "domain": "allbirds.com",
    "inputUrl": "https://allbirds.com/",
    "finalUrl": "https://www.allbirds.com/",
    "statusCode": 200,
    "siteState": "ok",
    "pagesFetched": 1,
    "technologies": [
      {
        "name": "Cloudflare",
        "slug": "cloudflare",
        "category": "CDN",
        "categories": [
          "CDN"
        ],
        "version": null,
        "confidence": 100,
        "evidence": [
          "header cf-ray: a5d52024dea8e608-IAD, a5d520292e468be3-IAD"
        ],
        "source": "subimpact-rules",
        "website": "https://www.cloudflare.com"
      },
      {
        "name": "Shopify",
        "slug": "shopify",
        "category": "Ecommerce",
        "categories": [
          "Ecommerce"
        ],
        "version": null,
        "confidence": 100,
        "evidence": [
          "header shopify-complexity-score: 6, 10",
          "cookie _shopify_essential",
          "script https://cdn.shopify.com/s/files/1/1104/4168/files/jsEncrypt.js?v=1756910700"
        ],
        "source": "subimpact-rules",
        "website": "https://www.shopify.com"
      },
      {
        "name": "Apple Pay",
        "slug": "apple-pay",
        "category": "Payment processors",
        "categories": [
          "Payment processors"
        ],
        "version": null,
        "confidence": 100,
        "evidence": [
          "dom script#apple-pay-shop-capabilities"
        ],
        "source": "wappalyzer-mit-6.10.54",
        "website": "https://www.apple.com/apple-pay"
      },
      "..."
    ],
    "technologyCount": 4,
    "categories": {
      "CDN": [
        "Cloudflare"
      ],
      "Ecommerce": [
        "Shopify"
      ],
      "Payment processors": [
        "Apple Pay"
      ],
      "Tag managers": [
        "Google Tag Manager"
      ]
    },
    "cms": null,
    "ecommerce": "Shopify",
    "cdn": [
      "Cloudflare"
    ],
    "analytics": [],
    "features": [],
    "fingerprintDatasetVersion": "wappalyzer-mit-6.10.54+subimpact-2026.11",
    "checkedAt": "2026-11-20T05:41:25.818Z",
    "error": null
  }
]
```

## How to run it

1. List the sites in domains, either bare hosts such as allbirds.com or full URLs such as https://www.coxandcox.co.uk/; only the host is used, so www and non-www are one row.
2. Leave maxPagesPerDomain at 1 for a fast pass, or raise it to 2 or 3 when the homepage is thin.
3. Set minConfidence, default 50, higher if you only want strong hits, and keep includeEvidence on if the result will be shown to someone else.
4. Set maxDomains as a cap for a large list, then start the run in the Apify Console.
5. Read technologies, cms, ecommerce, cdn and analytics per row, then export as JSON, CSV or Excel.

### cURL

```bash
curl -X POST "https://api.apify.com/v2/acts/subimpact~website-tech-stack-detector/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"domains":["allbirds.com","webflow.com"]}'
```

### Python

```python
from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("subimpact/website-tech-stack-detector").call(run_input={
      "domains": [
        "allbirds.com",
        "webflow.com"
      ]
    })

for item in client.dataset(run["default_dataset_id"]).iterate_items():
    print(item)
```

### JavaScript

```javascript
import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('subimpact/website-tech-stack-detector').call({
  "domains": [
    "allbirds.com",
    "webflow.com"
  ]
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();

console.log(items);
```

### n8n

Use the Apify node (Run an Actor).
Actor ID: subimpact/website-tech-stack-detector
Input JSON: paste the example input below.

## Limits

- Plain HTTP only: tags injected by a tag manager and JavaScript-global fingerprints are not visible.
- The fingerprint snapshot dates from January 2023 aside from the custom rules, so newer products may be missed.
- No DNS or nameserver data, because only the HTTP response is read.
- One to three pages per domain; the Actor does not crawl a site further.

## FAQ

### What does a domain cost?

$0.001 per analysed domain, which is $1.00 per 1,000 domains, plus $0.0004 for each extra page when maxPagesPerDomain is 2 or 3. There is no start fee. Blocked, dead, expired, timed-out and technology-free domains are not charged.

### How reliable are the detections?

Each hit carries a confidence score from 0 to 100, and minConfidence defaults to 50, which already drops detections that come only from a Content-Security-Policy allow-list. With evidence on you can see the header or snippet behind every detection rather than trusting a label.

### Do you need a browser or JavaScript?

No. The Actor fetches over plain HTTP and reads response headers, cookies, meta tags, script URLs, inline scripts, HTML, the final URL and static CSS selectors. That means tags injected later by a tag manager, and fingerprints that exist only as a JavaScript global, are not visible.

### How current is the fingerprint database?

It is the Wappalyzer 6.10.54 snapshot, a January 2023 dataset, plus 25 additional rules written for products it misses, such as Payload CMS and Fastly. A product released after 2023 is only recognised once a rule for it is added.

### What if a site blocks the request?

The row comes back with siteState set to blocked and is not charged. In the fixture set about one domain in eleven refused a datacenter IP. A proxy can be set in proxyConfiguration, though residential traffic is billed by Apify separately and can cost more than the run itself.

### Can I see DNS or nameserver records?

No. The Actor reads the HTTP response, so NS and DNS records are not part of the output. What it does report is the redirect chain, including 103 Early Hints, plus cookies and headers from the final response.

### What are the cms, ecommerce and cdn columns?

They are convenience fields for CSV users, extracted from the full technologies array: cms holds the detected content management system, ecommerce the shop platform, and cdn plus analytics hold lists. The array remains the source of truth, with category, version, confidence and evidence per technology.

## Links

- Page: https://subimpact.net/apis/website-tech-stack-detector/
- Category: https://subimpact.net/apis/category/leads/
- Run on Apify: https://apify.com/subimpact/website-tech-stack-detector
- All data APIs: https://subimpact.net/apis/
- Catalogue JSON: https://subimpact.net/apis/catalogue.json
