# Website Tech Stack Detector (Wappalyzer-style, CMS, CDN) (`arthursbuisness/website-tech-stack-detector`) Actor

- **URL**: https://apify.com/arthursbuisness/website-tech-stack-detector.md
- **Developed by:** [Arthur](https://apify.com/arthursbuisness) (community)
- **Categories:** Developer tools, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$2.00 / 1,000 analysed urls

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Website Tech Stack Detector (Wappalyzer-style, CMS, CDN)

Find out what any website is built with — from a single plain HTTP request, no browser, no proxies, no API key. The actor fetches each URL, follows redirects, and matches response headers, cookies, HTML, script/link URLs, inline JavaScript/CSS and meta tags against the open-source **webappanalyzer** fingerprint database (the MIT-licensed continuation of Wappalyzer: 7,500+ technologies in 100+ categories). You get the full technology list with versions, confidence and categories, plus ready-to-filter columns for **CMS, e-commerce platform, frameworks, analytics, CDN, web server, hosting, languages, tag managers, marketing tools, payment providers, live chat** and more.

Typical uses: lead lists filtered by platform ("all Shopify / WooCommerce / HubSpot sites in my list"), competitor research, migration and agency prospecting, security/asset inventories, market-share studies.

### What you get

One dataset row per URL:

| field | meaning |
|---|---|
| `url`, `final_url`, `status`, `redirects`, `redirect_chain[]`, `title` | fetch result |
| `technologies[]` | every detected technology: `name`, `version` (when a fingerprint exposes it), `confidence` (0–100), `categories[]`, `website`, `detected_via[]` (e.g. `header:Server`, `scriptSrc`, `meta:generator`, `cookie:_shopify_s`, `implied by WordPress`) |
| `technology_count`, `technology_names[]` | quick summary |
| `cms`, `ecommerce`, `blogs`, `frameworks`, `analytics`, `cdn`, `web_servers`, `hosting`, `languages`, `tag_managers`, `marketing`, `advertising`, `payment`, `live_chat`, `security`, `page_builders`, `caching`, `databases`, `operating_systems`, `ui`, `video`, `seo`, `email`, `static_site_generators`, `reverse_proxies`, `wordpress_plugins`, `wordpress_themes`, `shopify_apps` | technology names (with version) grouped by category — flat columns for CSV/Sheets filtering |
| `server`, `powered_by`, `generator` | raw `Server`, `X-Powered-By` headers and `<meta name="generator">` |
| `hosting_hints[]` | infrastructure inferred from headers (Cloudflare, AWS/CloudFront, Vercel, Netlify, GitHub Pages, Fastly, Akamai, Azure, Google Cloud, Kinsta, WP Engine, Webflow …) |
| `header_hints{}`, `cookie_names[]`, `script_hosts[]` | raw evidence you can build your own rules on |
| `dns_detected_services[]`, `dns_detected[]` | SaaS the *organisation* uses, revealed by MX/TXT DNS records (Google Workspace, Microsoft 365, SendGrid, Atlassian, Stripe, Zendesk, HubSpot …) — kept separate from the website stack |
| `error` | only for unreachable/invalid URLs — such rows are **not billed** |

Example (abridged):

```json
{"url":"https://wordpress.org","status":200,"technology_count":9,"cms":["WordPress 7.2"],"languages":["PHP"],"databases":["MySQL"],
 "web_servers":["Nginx"],"tag_managers":["Google Tag Manager"],"generator":"WordPress 7.2-alpha-63368",
 "technologies":[{"name":"WordPress","version":"7.2","confidence":100,"categories":["CMS","Blogs"],"detected_via":["html","meta:generator","scriptSrc"]}, "…"]}
{"url":"https://www.shopify.com","ecommerce":["Shopify"],"frameworks":["Tailwind CSS"],"cdn":["Cloudflare"],"hosting":["Amazon Web Services"],
 "dns_detected_services":["Google Workspace","Microsoft 365","Sendgrid","Stripe","Zendesk"]}
```

### Input

| field | default | meaning |
|---|---|---|
| `urls` | — | pages to analyse (bare domains are upgraded to `https://`); duplicates skipped |
| `checkDns` | true | also look up MX/TXT records (DNS-over-HTTPS) for DNS-based fingerprints → `dns_detected_services` |
| `minConfidence` | 50 | drop technologies below this confidence |
| `userAgent` | desktop Chrome | User-Agent header to send |
| `concurrency` | 5 | URLs processed in parallel (1–10) |
| `timeoutSecs` | 20 | per request |
| `maxItems` | 1000 | cost cap |

```json
{ "urls": ["https://wordpress.org", "https://www.shopify.com", "https://github.com", "https://mailchimp.com"] }
```

### Pricing

Pay per event: **$0.002 per URL** ($2 per 1,000). Charged only for rows successfully written to the dataset; unreachable or invalid URLs are stored with an `error` and are free. Roughly 1–3 seconds per URL; 1,000 URLs ≈ 5–8 minutes at 256 MB.

### How it works & limitations (honest list)

- **Plain GET, no JavaScript execution.** Fingerprints that need the live DOM or JavaScript globals (Wappalyzer's `js` and `dom` rules) are not evaluated. Technologies that only reveal themselves after scripts run (some SPA frameworks, A/B tools loaded by tag managers) can be missed; anything visible in the initial HTML, headers, cookies or script URLs is caught. In practice this covers CMS, e-commerce platforms, CDNs, servers, analytics and most marketing tags well.
- Rule types evaluated: `headers`, `cookies`, `html`, `scriptSrc` (script and link URLs), `scripts` (inline JS), `css` (inline CSS), `meta`, `url`, `dns`, plus `implies` / `requires` / `excludes` chains. Confidence is summed per technology and capped at 100.
- The fingerprint database is snapshotted into the image at build time (fast runs). If it is missing it is downloaded at run start.
- Bot-protected sites (Cloudflare challenge, Akamai) may return 403 or a challenge page; you still get the headers-based detections (the row is billed because a result was stored).
- Versions are reported only when a fingerprint exposes one (meta generator, script URL, header); absence of a version is not a signal.
- Not affiliated with Wappalyzer; uses the MIT-licensed webappanalyzer fingerprint data.

# Actor input Schema

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

Pages to analyse, one per line. Bare domains are upgraded to https://. Duplicates are skipped.

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

Look up MX and TXT records over DNS-over-HTTPS to detect SaaS used by the organisation (Google Workspace, Microsoft 365, SendGrid, Stripe …). Reported separately in dns\_detected\_services.

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

Drop technologies whose summed fingerprint confidence is below this value (0–100).

## `userAgent` (type: `string`):

User-Agent header sent with each request. Default: a desktop Chrome string.

## `concurrency` (type: `integer`):

1–10.

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

Applies to each HTTP request (per redirect hop).

## `maxItems` (type: `integer`):

Stop after this many URLs (cost control).

## Actor input object example

```json
{
  "urls": [
    "https://wordpress.org",
    "https://www.shopify.com",
    "https://github.com",
    "https://mailchimp.com"
  ],
  "checkDns": true,
  "minConfidence": 50,
  "concurrency": 5,
  "timeoutSecs": 20,
  "maxItems": 1000
}
```

# Actor output Schema

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

All items as JSON

## `resultsCsv` (type: `string`):

Same dataset as CSV — open in Excel/Sheets

# 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": [
        "https://wordpress.org",
        "https://www.shopify.com",
        "https://github.com",
        "https://mailchimp.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("arthursbuisness/website-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": [
        "https://wordpress.org",
        "https://www.shopify.com",
        "https://github.com",
        "https://mailchimp.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("arthursbuisness/website-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": [
    "https://wordpress.org",
    "https://www.shopify.com",
    "https://github.com",
    "https://mailchimp.com"
  ]
}' |
apify call arthursbuisness/website-tech-stack-detector --silent --output-dataset

```

## MCP server setup

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