# Tech Stack Detector – Wappalyzer & BuiltWith Alternative (`drobe86/tech-stack-detector`) Actor

Find out what any website is built with: CMS, ecommerce platform, analytics, JavaScript frameworks, CDN, hosting, payments and more. Returns versions, confidence scores and the evidence behind every detection.

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

## Pricing

from $20.00 / 1,000 site-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

## Website Tech Stack Detector

Find out what any website is built with. Give it a list of domains and get back the CMS, ecommerce platform, analytics, JavaScript frameworks, CDN, hosting, payment providers and more, with versions, confidence scores and the evidence behind every detection.

It works as a bulk alternative to browser extensions and technology-lookup APIs such as Wappalyzer and BuiltWith: no API key, no login, no monthly plan. You pay only for websites that were successfully analyzed.

### What you can do with it

- **Qualify leads by technology.** Find the Shopify stores, WordPress sites or HubSpot users in a list of prospects.
- **Research competitors.** See which frameworks, CDNs, payment providers and marketing tools they rely on.
- **Enrich a CRM or spreadsheet.** One row per domain, with ready-made columns for the categories people filter on most.
- **Track migrations.** Run it on a schedule to see when a site changes platform or adds a tool.

### What makes it different

- **More than 7,000 technologies** across 100+ categories, refreshed with every build.
- **Evidence for every detection.** Each technology comes with the header, script URL, cookie, meta tag or DNS record that triggered it, so you can check the result yourself.
- **Versions and confidence scores** where the website exposes them.
- **DNS and TLS signals.** Finds the email provider, DNS host, certificate authority and the SaaS vendors a company has verified its domain with. These never appear in the page itself.
- **Website technology and company vendors are kept apart.** A DNS record proves a company uses a service, not that the website runs on it, so those results go in their own column.
- **Fair billing.** Unreachable, blocked and invalid websites are returned with a status and are not charged.

### Input

| Field | Description |
|---|---|
| `urls` | Domains or URLs to analyze. A bare domain such as `stripe.com` works. |
| `minConfidence` | Only return technologies detected with at least this confidence (default 50). |
| `includeEvidence` | Include the evidence and a short description for each technology (default on). |
| `checkDns` | Also check DNS records, the TLS certificate and robots.txt (default on). |
| `maxConcurrency` | Websites analyzed in parallel (default 10). |

```json
{
    "urls": ["allbirds.com", "https://woocommerce.com"],
    "minConfidence": 50
}
```

### Output

One item per website. The flat columns are convenient for CSV and Excel exports; `technologies` holds the full detail.

```json
{
    "url": "allbirds.com",
    "finalUrl": "https://www.allbirds.com/",
    "domain": "allbirds.com",
    "status": "ok",
    "httpStatus": 200,
    "title": "Allbirds",
    "technologyCount": 16,
    "technologyNames": "Apple Pay, Cloudflare, Google Tag Manager, PayPal, Shopify, Swiper",
    "dnsVerifiedServices": "DocuSign, Microsoft 365, Miro",
    "cms": null,
    "ecommerce": "Shopify",
    "cdn": "Cloudflare",
    "paymentProcessors": "Apple Pay, PayPal",
    "email": "Microsoft 365",
    "technologies": [
        {
            "name": "Shopify",
            "slug": "shopify",
            "categories": ["Ecommerce"],
            "version": null,
            "confidence": 100,
            "detectedVia": ["page"],
            "website": "https://shopify.com",
            "evidence": ["script: https://cdn.shopify.com/s/files/1/1104/4168/files/app.js"]
        }
    ],
    "analyzedAt": "2026-10-04T18:00:00.000Z"
}
```

Summary columns: `cms`, `ecommerce`, `analytics`, `tagManagers`, `jsFrameworks`, `webFrameworks`, `programmingLanguages`, `webServers`, `cdn`, `hosting`, `paymentProcessors`, `marketingAutomation`, `advertising`, `liveChat`, `crm`, `email`.

`status` is one of:

| Status | Meaning | Charged |
|---|---|---|
| `ok` | The website was fetched and analyzed. | Yes |
| `blocked` | The website answered with an error or a bot challenge. Whatever the response revealed is still returned. | No |
| `unreachable` | The website could not be reached. | No |
| `invalid_url` | The input is not a website address. | No |

### How it works

For each website the actor makes one request for the page, plus optional DNS, TLS and robots.txt lookups. It then matches the response against a library of technology fingerprints: HTTP headers, cookies, HTML, meta tags, script URLs, inline scripts, page elements, DNS records and the certificate issuer.

It does not run a browser, which keeps it fast and inexpensive: websites are analyzed in parallel, and a list of several hundred finishes in a few minutes.

### Limitations

- Tools that only appear after JavaScript runs, for example an analytics tag injected by a tag manager, can be missed. The tag manager itself is detected.
- Websites behind a strict bot challenge return `blocked`. Their CDN, security vendor and DNS-based results are still reported.
- Detection covers the page you provide, usually the homepage. Technologies used only on other pages, such as a checkout, are not seen.
- Results reflect public signals and can occasionally be wrong. Check the `evidence` field when a detection matters.

### Credits

Technology fingerprints come from the open-source [webappanalyzer](https://github.com/enthec/webappanalyzer) project (GPL-3.0). This actor is not affiliated with Wappalyzer or BuiltWith.

# Actor input Schema

## `urls` (type: `array`):

Domains or URLs to analyze, one per line. A bare domain such as stripe.com works.

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

Only return technologies detected with at least this confidence (1-100). Lower it to see weaker matches.

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

For each technology, include what triggered the detection (header, script URL, cookie, DNS record) and a short description.

## `checkDns` (type: `boolean`):

Finds technologies that never appear in the page itself, such as the email provider, DNS host and certificate authority. Turn off for the fastest runs.

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

How many websites to analyze at the same time.

## Actor input object example

```json
{
  "urls": [
    "stripe.com",
    "https://www.allbirds.com"
  ],
  "minConfidence": 50,
  "includeEvidence": true,
  "checkDns": true,
  "maxConcurrency": 10
}
```

# Actor output Schema

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

One item per website with its detected technologies, summary columns and evidence.

# 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 = {
    "urls": [
        "stripe.com",
        "https://www.allbirds.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("drobe86/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 = { "urls": [
        "stripe.com",
        "https://www.allbirds.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("drobe86/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 '{
  "urls": [
    "stripe.com",
    "https://www.allbirds.com"
  ]
}' |
apify call drobe86/tech-stack-detector --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,drobe86/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/ZLnqTudkabDojbaMe/builds/sWvFf9HIpgovXYEcA/openapi.json