# Tech Stack Detector: BuiltWith & Wappalyzer alternative (`steadyline/tech-stack-detector`) Actor

Detect the technology stack of any list of domains: CMS, ecommerce platform, analytics, marketing tools, CDN, hosting, frameworks and email provider (from MX/TXT/NS DNS). HTTP-first and cheap, with an optional headless-browser fallback. By Steadyline Data.

- **URL**: https://apify.com/steadyline/tech-stack-detector.md
- **Developed by:** [Steadyline Data](https://apify.com/steadyline) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 domain analyzeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Tech Stack Detector: BuiltWith & Wappalyzer alternative (bulk domains)

Paste in a list of domains and get each site's technology stack back as clean JSON: **CMS, ecommerce platform, analytics, tag managers, marketing automation, chat, payments, consent tools, frameworks, CDN, hosting, DNS host and email provider**. It is built for lead lists, competitor research, agency prospecting and CRM enrichment, where you need thousands of domains checked cheaply rather than one site at a time in a browser extension.

### How it works

1. **HTTP first.** Each domain is fetched once with a normal browser user agent. We match response headers, cookie names, `<meta>` tags, `<script src>` URLs and HTML patterns against about 290 hand-written fingerprints.
2. **DNS.** MX, TXT (SPF and verification records), NS and the CNAME of `www` reveal the email provider (Google Workspace, Microsoft 365, Zoho...), email security gateways (Proofpoint, Mimecast), sending services (SendGrid, Mailchimp, SES), DNS host and CDN. This also works when the website itself blocks bots.
3. **Optional browser fallback.** Turn on `browserFallback` and domains that return 403/429/503, a bot challenge, or an empty JavaScript shell are re-tried in headless Chrome. The fallback also checks JavaScript globals.

Each technology has a `confidence` value. Header, cookie, script, meta and DNS matches score 100. HTML-pattern matches score 80, implied technologies score at most 90 (WooCommerce implies WordPress, which implies PHP), and weak heuristics score 50–60. Use `minConfidence` to filter. A `version` is returned when the page exposes one, for example a WordPress generator tag.

### Input

```json
{ "domains": ["shopify.com", "allbirds.com", "hubspot.com"], "browserFallback": false, "includeDns": true, "minConfidence": 50 }
```

### Output sample (real cloud run, trimmed)

```json
{
  "domain": "allbirds.com",
  "finalUrl": "https://www.allbirds.com/",
  "httpStatus": 200,
  "technologies": [
    {
      "name": "Cloudflare",
      "categories": [
        "CDN",
        "Security / WAF"
      ],
      "version": null,
      "confidence": 100
    },
    {
      "name": "Microsoft 365",
      "categories": [
        "Email provider"
      ],
      "version": null,
      "confidence": 100
    },
    {
      "name": "Shopify",
      "categories": [
        "Ecommerce"
      ],
      "version": null,
      "confidence": 100
    },
    {
      "name": "Shopify hosting",
      "categories": [
        "Hosting / PaaS"
      ],
      "version": null,
      "confidence": 100
    },
    {
      "...": "7 more"
    }
  ],
  "technologyCount": 11,
  "categoriesSummary": {
    "CDN": [
      "Cloudflare"
    ],
    "Security / WAF": [
      "Cloudflare"
    ],
    "Email provider": [
      "Microsoft 365"
    ],
    "Ecommerce": [
      "Shopify"
    ]
  },
  "emailProvider": "Microsoft 365",
  "emailSecurityGateway": null,
  "cdn": [
    "Cloudflare"
  ],
  "cms": null,
  "ecommerce": "Shopify",
  "analytics": [
    "Microsoft Clarity"
  ],
  "hosting": [
    "Shopify hosting"
  ],
  "method": "http",
  "analyzedAt": "2026-10-29T22:55:19.948Z",
  "error": null
}
```

The **Overview** dataset view shows one row per domain. The **All technologies** view shows one row per detected technology.

### Pricing (pay per event)

| Event | Price |
|---|---|
| `domain-analyzed`: domain fetched over HTTP and analyzed | $0.002 |
| `domain-analyzed-browser`: domain needed the browser fallback | $0.004 (instead of, not on top of, the HTTP event) |

**Failures are never charged.** Unreachable domains, DNS errors and sites that block us (also in the browser) are still returned with their DNS-based findings and an `error` message, but they cost you nothing.
**Cost example:** 10,000 domains, of which about 5% need the browser = 9,500 × $0.002 + 500 × $0.004 = **$21**. In our test, 20 diverse domains took 5 seconds at 512 MB.

### Accuracy & limitations

- Detection only sees what the homepage and DNS expose. Tools loaded later through Google Tag Manager (such as Google Analytics behind GTM) may only appear with the browser fallback, or not at all.
- Some large sites block datacenter IPs. In our test, nytimes.com returned 403 even in the browser. Those rows are free and still include the DNS findings.
- TXT verification records (`Verified SaaS (DNS)`) show that a company verified a domain with a vendor. They do not prove active use.

### Fingerprint data & license

The fingerprint set is an original, clean-room dataset by Steadyline Data. It was written from vendor documentation and markup we observed on public sites. It is **not** copied or derived from Wappalyzer or its GPL-3.0 forks (e.g. webappanalyzer), and it does not use BuiltWith data. Product names are trademarks of their owners and are used here only to identify them.

### Acceptable use

Use this Actor only on public websites and for legitimate purposes such as market research, sales and security inventory. It makes one ordinary page request per domain plus public DNS queries. Do not use it to bypass access controls, to attack or overload sites, or in ways that break a site's terms or applicable law (including GDPR/CCPA when you combine results with personal data). You are responsible for how you use the output.

### Support

Found a missed or wrong detection? Open an issue with the domain and the expected technology. Fingerprint additions ship regularly. Made by **Steadyline Data**.

# Actor input Schema

## `domains` (type: `array`):

Domains (example.com) or full URLs. Duplicates and www. variants are merged.

## `browserFallback` (type: `boolean`):

When the plain HTTP fetch is blocked (403/429/503, bot challenge) or returns an empty JavaScript shell, render the page in headless Chrome. Those domains are charged at the browser price. Needs at least 1024 MB memory.

## `includeDns` (type: `boolean`):

Look up MX, TXT, NS records and the CNAME of www to detect email provider, email-sending services, DNS hosting and CDN.

## `minConfidence` (type: `integer`):

Drop detections below this confidence (0-100). Header/cookie/script/DNS matches score 100, HTML-pattern matches 80, implied technologies 90 max, weak heuristics 50-60.

## `includeEvidence` (type: `boolean`):

Add detectedVia (header, cookie, script, html, meta, dns-mx...) to each technology and the raw DNS records to each row.

## `maxConcurrency` (type: `integer`):

Domains analyzed in parallel.

## `timeoutSecs` (type: `integer`):

Per-request timeout.

## Actor input object example

```json
{
  "domains": [
    "shopify.com",
    "wordpress.org",
    "allbirds.com",
    "hubspot.com",
    "vercel.com"
  ],
  "browserFallback": false,
  "includeDns": true,
  "minConfidence": 50,
  "includeEvidence": false,
  "maxConcurrency": 10,
  "timeoutSecs": 20
}
```

# Actor output Schema

## `results` (type: `string`):

One row per domain with the headline stack.

## `technologies` (type: `string`):

One row per detected technology.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

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

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "domains": [
        "shopify.com",
        "wordpress.org",
        "allbirds.com",
        "hubspot.com",
        "vercel.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("steadyline/tech-stack-detector").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "domains": [
        "shopify.com",
        "wordpress.org",
        "allbirds.com",
        "hubspot.com",
        "vercel.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("steadyline/tech-stack-detector").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "domains": [
    "shopify.com",
    "wordpress.org",
    "allbirds.com",
    "hubspot.com",
    "vercel.com"
  ]
}' |
apify call steadyline/tech-stack-detector --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,steadyline/tech-stack-detector"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/7pWgH5nGPYchenNDf/builds/ckpzCezl2nKrgnfzY/openapi.json