# Website Tech Stack Detector – BuiltWith Wappalyzer Alternative (`ntriqpro/website-tech-detector`) Actor

Find out what any website is built with: frameworks, CMS, analytics, hosting, JavaScript libraries and payment gateways, detected from the live page. Scan domains in bulk — an open-source alternative to Wappalyzer Pro for sales research and competitive analysis.

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

## Pricing

$50.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?

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 – BuiltWith Wappalyzer Alternative

**Give it up to 50 website URLs and get one row per site naming the technologies it runs** — CMS, e-commerce platform, JavaScript framework, analytics, marketing tools, CDN, hosting, server stack and payment provider — matched against 39 named fingerprints on the fully rendered page. Built for sales prospecting, competitive analysis and market research, as an open-source alternative to BuiltWith and Wappalyzer lookups.

### Features

- **39 named technologies** — WordPress, Shopify, Wix, Squarespace, Webflow, Ghost, Drupal, Joomla, WooCommerce, Magento, BigCommerce, React, Vue.js, Angular, Next.js, Nuxt.js, Svelte and more (full list below)
- **Multi-Layer Analysis** — HTTP headers, HTML metadata, JavaScript patterns, DOM attributes
- **Fast & Reliable** — Powered by Crawlee with Playwright Chrome
- **Bulk Processing** — Analyze up to 50 websites per run
- **Detailed Results** — Technology list, server info, HTTP status, disclaimers
- **Pay-Per-Event Pricing** — $0.05 per website analyzed

### Detected technologies

Every name below is a fingerprint in the detection engine. The **Signal** column says what the engine looks for on the live page, so you know why a technology was (or was not) reported.

#### CMS and website builders

| Technology | Signal |
|---|---|
| WordPress | `wp-content/`, `wp-includes/` script paths; `generator` meta tag |
| Shopify | `cdn.shopify.com` scripts; `Shopify.theme`, `shopify-section` markup; `x-shopid` header |
| Wix | `static.wixstatic.com` scripts; `wix-code-sdk` markup |
| Squarespace | `static.squarespace.com` scripts; `generator` meta tag |
| Webflow | `webflow.js`; `data-wf-` attributes; `generator` meta tag |
| Ghost | `generator` meta tag; `x-ghost-cache-status` header |
| Drupal | `drupal.js`, `/sites/default/` paths; `data-drupal-` attributes; `x-generator` header |
| Joomla | `/media/jui/` paths; `generator` meta tag |

#### E-commerce platforms

| Technology | Signal |
|---|---|
| WooCommerce | `woocommerce` scripts, `wc-ajax` endpoints, `wc_` markup |
| Magento | `mage/cookies` scripts; `data-mage-` attributes |
| BigCommerce | `cdn11.bigcommerce.com` scripts |
| Shopify | see CMS table above |

#### JavaScript frameworks and UI libraries

| Technology | Signal |
|---|---|
| React | `react.js` / `react.min.js`, `react-dom` scripts; `__REACT_`, `data-reactroot`, `data-reactid` markup |
| Vue.js | `vue.js` / `vue.min.js`, `vue-router` scripts; `data-v-` attributes, `v-bind`, `v-model` |
| Angular | `angular.js`, `@angular/core`; `ng-version`, `ng-app` markup |
| Next.js | `__NEXT_DATA__`, `_next/static`; `x-powered-by: Next.js` header |
| Nuxt.js | `__NUXT__`, `_nuxt/` paths; `data-n-head` markup |
| Svelte | `svelte` scripts; `s-` scoped class names |
| jQuery | `jquery.min.js`, versioned `jquery-x.y` scripts |
| Bootstrap | `bootstrap.min.js`, `bootstrap.bundle`; `container`/`row`/`col-` classes |
| Tailwind CSS | utility class patterns such as `flex`, `grid`, `text-*-500`, `bg-*-500`, `p-4` |

#### Analytics, marketing and customer messaging

| Technology | Signal |
|---|---|
| Google Analytics | `google-analytics.com/analytics.js`, `gtag`; `UA-` and `G-` property IDs |
| Google Tag Manager | `googletagmanager.com/gtm.js`; `GTM-` container IDs |
| Hotjar | `static.hotjar.com`; `hjBootstrap` markup |
| Mixpanel | `cdn.mxpnl.com`; `mixpanel.init` |
| Segment | `cdn.segment.com`; `analytics.segment` |
| HubSpot | `js.hs-scripts.com`, `js.hubspot.com`; `hs-beacon` markup |
| Intercom | `widget.intercom.io`, `js.intercomcdn.com`; `x-intercom-version` header |
| Drift | `js.drift.com`, `driftt.com` |

#### CDN and hosting

| Technology | Signal |
|---|---|
| Cloudflare | `cf-ray` header; `server: cloudflare` |
| AWS CloudFront | `x-amz-cf-id` header; `via: CloudFront` |
| Fastly | `x-fastly-request-id` header; `via: varnish` |
| Vercel | `x-vercel-id` header; `server: Vercel` |
| Netlify | `x-nf-request-id` header; `server: Netlify` |

#### Backend and server stack

| Technology | Signal |
|---|---|
| Node.js | `x-powered-by: Express` or `Node.js` header |
| PHP | `x-powered-by: PHP` header |
| Ruby on Rails | `x-powered-by: Phusion Passenger`, `server: Passenger` |
| ASP.NET | `__VIEWSTATE`, `aspnetForm` markup; `x-powered-by: ASP.NET`, `x-aspnet-version` headers |

#### Payment providers

| Technology | Signal |
|---|---|
| Stripe | `js.stripe.com`, `stripe.js` |
| PayPal | `paypal.com/sdk`, `paypalobjects.com` |

A technology that is not in these tables is not reported. If you need a name that is missing, ask in the Actor's Issues tab.

### How it compares to other tech-stack detectors

Facts below were read from the Apify Store on 3 September 2026 and from each product's own listing; prices are the Free-plan figures shown there and can change.

| | This Actor | misterkhan/website-tech-stack-scanner | pulsedata/website-tech-stack-detector | BuiltWith / Wappalyzer |
|---|---|---|---|---|
| Coverage | 39 named technologies, each with a documented signal (tables above) | 7,000+ technologies (listing) | 7,500+ technologies with versions and confidence (listing) | Large commercial databases |
| Page rendering | Headless Chrome (Playwright) — JavaScript executed before matching | Not stated on listing | Not stated on listing | Own crawlers |
| Input | `urls` array, up to 50 per run | `startUrls` array, up to 100 per run | `urls` array | Web UI / API by subscription |
| Price per site | $0.05 flat on every Apify plan | $0.10 on the Free plan, $0.07 on higher plans | $0.002 | Subscription products |
| Output | `technologies` list, `techCount`, `serverInfo`, `responseStatus` per URL | Per listing | Per listing | Per product |

Pick this Actor when you want a short, explainable list of well-known platforms per site at a fixed price. Pick a large-catalogue detector when you need long-tail or version-level identification.

### Input

```json
{
  "urls": [
    "https://example.com/",
    "https://vercel.com/",
    "https://github.com/"
  ],
  "timeout": 30000
}
```

#### Input Parameters

- **urls** (array, required) — List of website URLs to analyze. Maximum 50 URLs per run. Each URL should start with `http://` or `https://`.
- **timeout** (integer, optional) — Maximum time to wait for each page to load in milliseconds. Default: 30000 (30 seconds).

### Output

```json
{
  "url": "https://vercel.com/",
  "technologies": ["React", "Next.js", "Vercel", "Google Analytics"],
  "techCount": 4,
  "serverInfo": "Vercel",
  "responseStatus": 200,
  "disclaimer": "This tool detects website technologies using publicly observable signals..."
}
```

#### Output Fields

- **url** — The analyzed website URL
- **technologies** — Array of detected technology names
- **techCount** — Total number of detected technologies
- **serverInfo** — HTTP server header or x-powered-by value
- **responseStatus** — HTTP response status code
- **error** (conditional) — Error message if page failed to load
- **disclaimer** — Legal disclaimer about detection limitations

### Pricing

Free plan: each run returns up to 25 results (the first 3 inputs). Paid Apify plans receive the full result set.

- **Model** — Pay-Per-Event
- **Cost** — $0.05 USD per website analyzed
- **Billing** — Only charged for successful page loads

### Example Usage

#### Basic Usage

```json
{
  "urls": ["https://example.com/"]
}
```

#### Multiple URLs

```json
{
  "urls": [
    "https://github.com/",
    "https://vercel.com/",
    "https://notion.so/",
    "https://figma.com/"
  ]
}
```

#### With Custom Timeout

```json
{
  "urls": ["https://slowsite.example.com/"],
  "timeout": 60000
}
```

### How It Works

1. **Page Fetch** — Uses Playwright Chrome to fetch each URL with full JavaScript rendering
2. **Content Analysis** — Extracts HTML content and HTTP response headers
3. **Pattern Matching** — Compares against 39 technology fingerprints:
   - Script source URLs and names
   - HTML element patterns and class names
   - Meta tag contents
   - HTTP header values
4. **Result Compilation** — Returns detected technologies, server info, and metadata

### Detection Limitations

- **JavaScript Dependencies** — Some technologies may be obfuscated, lazy-loaded, or server-side only
- **False Positives/Negatives** — Detection is based on observable signals and may be incomplete
- **Dynamic Content** — Technologies loaded after page render may not be detected
- **Custom Implementations** — Custom or white-label solutions won't be detected

### Legal Disclaimer

This tool detects website technologies using publicly observable signals (HTTP headers, HTML source, JavaScript patterns). Detection results are best-effort estimates and may be incomplete or inaccurate. Some technologies may be obfuscated or server-side only.

Results are for **informational and research purposes only**. Do not use for:

- Unauthorized security testing
- Competitive espionage
- Targeting websites without consent
- Any illegal or unethical purposes

The operator makes no warranty regarding the completeness or accuracy of technology detection results. Use at your own risk and in compliance with all applicable laws and the target website's terms of service.

### License

This Actor uses [Crawlee](https://crawlee.dev/) under Apache License 2.0. See Crawlee documentation for more details.

### Support

For issues, feature requests, or questions, contact the Actor author or visit the Apify documentation.

***

### 🔗 Related Actors by ntriqpro

Build your data pipeline with the ntriqpro Actor suite:

- [**maigret-actor**](https://apify.com/ntriqpro/maigret-actor) — Maigret OSINT — Username search (5.0★)
- [**github-repo-intelligence**](https://apify.com/ntriqpro/github-repo-intelligence) — GitHub Repo Audit — OSS due diligence
- [**phish-radar**](https://apify.com/ntriqpro/phish-radar) — Phishing & Malicious Domain Detector

### ⭐ Love it? Leave a Review

Your rating helps professionals discover this actor. [Rate it here](https://apify.com/ntriqpro/website-tech-detector/reviews).

# Actor input Schema

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

List of website URLs to analyze (max 50 per run). Free plan: each run returns up to 25 results (the first 3 inputs). Paid Apify plans receive the full result set.

## `timeout` (type: `integer`):

Maximum time to wait for each page to load in milliseconds

## Actor input object example

```json
{
  "urls": [
    "https://www.example.com/",
    "https://vercel.com/"
  ],
  "timeout": 30000
}
```

# Actor output Schema

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

No description

# 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://www.example.com/",
        "https://vercel.com/"
    ],
    "timeout": 30000
};

// Run the Actor and wait for it to finish
const run = await client.actor("ntriqpro/website-tech-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://www.example.com/",
        "https://vercel.com/",
    ],
    "timeout": 30000,
}

# Run the Actor and wait for it to finish
run = client.actor("ntriqpro/website-tech-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://www.example.com/",
    "https://vercel.com/"
  ],
  "timeout": 30000
}' |
apify call ntriqpro/website-tech-detector --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,ntriqpro/website-tech-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/bGJw7tKO03Ok6O0Ww/builds/44hcWWO8tLaao7MIT/openapi.json