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

Find out what any website is built with: CMS, ecommerce platform, frameworks, analytics, ads, CDN, hosting, payments and email provider. 7,600+ technologies (Wappalyzer fingerprints) plus DNS records. No browser: 1,000 sites in minutes. Pay only for analyzed websites.

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

## Pricing

from $30.00 / 1,000 website analyzeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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 — find out what any website is built with

Give it a list of websites and get back, for each one, the technologies it runs on: CMS, ecommerce platform, JavaScript frameworks, analytics, marketing and advertising tools, CDN, hosting, payment providers, email provider and much more.

It recognizes **7,600+ technologies** using the open-source Wappalyzer fingerprints (maintained by the community in [webappanalyzer](https://github.com/enthec/webappanalyzer)), and it adds what a page alone doesn't show: **DNS records** reveal the email provider (Google Workspace, Microsoft 365), the DNS host and SaaS tools the company has verified (Atlassian, HubSpot, Stripe, DocuSign, Zendesk…).

#### Why this Actor

- **Fast and cheap at scale.** No browser: one HTTP request and a few DNS lookups per website, so thousands of sites take minutes, not hours. Other tech-stack Actors charge up to $0.10 per website; this one costs half that, and less on higher Apify plans.
- **Pay only for results.** Websites that are unreachable, or that answer with an anti-bot page, are returned with the reason and **are not charged**.
- **Versions and confidence**, like Wappalyzer: `WordPress 7.2`, `jQuery 2.0.3`, `Shopify`…
- **Evidence on demand.** Turn on *Include evidence* to see the exact header, cookie, HTML snippet or DNS record behind every detection.
- **Spreadsheet friendly.** Every item has a `technologyNames` column (a plain comma-separated list) next to the full JSON.

#### Use cases

- **Lead generation and qualification**: find stores on Shopify, sites on WordPress, companies using HubSpot or Salesforce.
- **Competitor research**: see which analytics, A/B testing, chat and ad tools your competitors use.
- **Market research**: measure how popular a technology is across thousands of domains.
- **Sales intelligence and CRM enrichment**: add the tech stack to every account in your list.

#### Input

| Field | Description |
|---|---|
| Websites | Domains or URLs, one per line. `shopify.com`, `www.example.com` and `https://example.com/shop` all work. |
| Check DNS records | Detect technologies from MX, TXT, NS and SOA records (default: on). |
| Include evidence | Add what revealed each technology (default: off). |
| Minimum confidence | Drop detections below this confidence (default: 0, keep all). |
| Parallel requests | Websites analyzed at the same time (default: 30). |
| Proxy | Apify Proxy by default. |

#### Output

One item per website. Real output for `nextjs.org` (shortened):

```json
{
  "input": "nextjs.org",
  "url": "https://nextjs.org/",
  "domain": "nextjs.org",
  "status": "ok",
  "httpStatus": 200,
  "title": "Next.js by Vercel - The React Framework",
  "technologyCount": 11,
  "technologyNames": "Next.js, Google Workspace, Radix UI, React, Vercel, HSTS, HTTP/3, Open Graph, Priority Hints, Sendgrid, Webpack",
  "technologies": [
    {
      "name": "Next.js",
      "version": null,
      "confidence": 100,
      "categories": ["JavaScript frameworks", "Web frameworks", "Web servers", "Static site generator"],
      "website": "https://nextjs.org",
      "detectedBy": ["headers"],
      "evidence": ["headers: Next.js"]
    },
    {
      "name": "Google Workspace",
      "version": null,
      "confidence": 100,
      "categories": ["Webmail", "Email"],
      "website": "https://workspace.google.com/",
      "detectedBy": ["dns"],
      "evidence": ["dns: aspmx.l.google.com"]
    }
  ],
  "categories": {
    "JavaScript frameworks": ["Next.js", "React"],
    "Email": ["Google Workspace", "Sendgrid"],
    "PaaS": ["Vercel"]
  },
  "analyzedAt": "2026-09-28T18:17:07.581Z"
}
```

`status` is `ok`, `blocked` (the site showed an anti-bot page: only header and DNS detections are returned, not charged) or `failed` (not reachable, or it answered with an error page such as 404 or 502: not charged).

#### How it works and its limits

The Actor downloads each page once, like a browser would, and matches the fingerprints against headers, cookies, HTML, script URLs, inline scripts, meta tags, page text, the static DOM, the TLS certificate issuer and DNS records. Framework variables that pages write into their HTML (such as `__NEXT_DATA__` or `__NUXT__`) are recognized too.

Honest limits:

- About 1,500 of the fingerprints can only be seen by running the page's JavaScript in a real browser (for example tools loaded after user interaction). Those are not detected.
- Only the page you give is analyzed (usually the home page). Tools used only on other pages (e.g. checkout) may not show up.
- Some websites protect themselves with anti-bot pages. They are marked `blocked` and not charged.
- Keep the default 4 GB of memory for large lists: with less memory the Actor still works, but it is slower and may give up on slow websites (not charged).

#### Credits

Technology fingerprints: [enthec/webappanalyzer](https://github.com/enthec/webappanalyzer), the community continuation of the open-source Wappalyzer fingerprints (GPL-3.0). Wappalyzer is a trademark of its owner; this Actor is not affiliated with it.

# Actor input Schema

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

Domains or URLs to analyze, one per line (e.g. <code>shopify.com</code> or <code>https://www.example.com/shop</code>). Thousands are fine.

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

Also detect technologies that only show up in DNS: email providers (Google Workspace, Microsoft 365), DNS hosts and verified SaaS tools (e.g. Atlassian, HubSpot, Stripe).

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

Add, for every technology, the piece of HTML, header, cookie or DNS record that revealed it.

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

Only keep technologies detected with at least this confidence (0-100). Most detections are 100.

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

How many websites to analyze at the same time.

## `proxyConfiguration` (type: `object`):

Proxy used to load the websites. The default Apify Proxy works for most sites.

## Actor input object example

```json
{
  "urls": [
    "wordpress.org",
    "allbirds.com",
    "nextjs.org"
  ],
  "checkDns": true,
  "includeEvidence": false,
  "minConfidence": 0,
  "maxConcurrency": 30,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

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

One item per website: technologies with version, confidence and categories.

# 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": [
        "wordpress.org",
        "allbirds.com",
        "nextjs.org"
    ],
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("brii3343/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": [
        "wordpress.org",
        "allbirds.com",
        "nextjs.org",
    ],
    "proxyConfiguration": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("brii3343/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": [
    "wordpress.org",
    "allbirds.com",
    "nextjs.org"
  ],
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call brii3343/tech-stack-detector --silent --output-dataset

```

## MCP server setup

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