# Website Tech Stack Detector — CMS, Ecommerce, Analytics & Email (`jeffev/website-tech-stack`) Actor

Detect the technologies behind any list of websites: CMS, ecommerce platform, analytics, ad pixels, marketing automation, chat, payments, frameworks, hosting and CDN, plus the company's email provider and email-sending tools from DNS.

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

## Pricing

from $3.50 / 1,000 website analyseds

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

## Website Tech Stack Detector — CMS, ecommerce, analytics & email provider

Find out **what technologies any website uses**, for a whole list of domains at once. Perfect for sales prospecting ("all Shopify stores using Klaviyo"), competitor research, market sizing and lead qualification.

### What it detects (150+ technologies)

| Category | Examples |
|---|---|
| CMS & site builders | WordPress, Drupal, Webflow, Wix, Squarespace, Framer, HubSpot CMS, Elementor |
| Ecommerce | Shopify, WooCommerce, Magento, BigCommerce, VTEX, Nuvemshop, Tray, Loja Integrada, Salesforce Commerce |
| Analytics & tags | Google Analytics 4, Google Tag Manager, Hotjar, Clarity, Mixpanel, Amplitude, Segment, PostHog |
| Advertising pixels | Meta Pixel, Google Ads, LinkedIn Insight, TikTok Pixel, Criteo, Taboola |
| Marketing & CRM | HubSpot, RD Station, Marketo, Pardot, ActiveCampaign, Mailchimp, Klaviyo, Salesforce |
| Chat & support | Intercom, Zendesk, Drift, Crisp, Tawk.to, JivoChat, WhatsApp button |
| Payments | Stripe, PayPal, Mercado Pago, PagSeguro, Adyen, Klarna |
| Frameworks | React, Next.js, Nuxt, Vue, Angular, Svelte, Astro, Laravel, Django, Rails, ASP.NET |
| Hosting & CDN | Cloudflare, CloudFront, Fastly, Akamai, Vercel, Netlify, WP Engine, Nginx, Apache |
| **Email (from DNS)** | **Google Workspace, Microsoft 365**, Zoho, plus sending tools: SendGrid, Amazon SES, Mailgun, Mandrill |

The **email provider from DNS** (MX/SPF records) is something most technology detectors miss, and it tells you a lot about a company: Google Workspace vs Microsoft 365, and which tools send their emails.

### Why this one

- **Summary fields** for quick filtering: `cms`, `ecommerce`, `emailProvider`, `hosting`, `cdn`, `frontendFramework`.
- **Evidence** for every detection (which script, header, cookie or DNS record matched).
- **Gets past blocks**: retries through Apify Proxy and a residential IP when a site refuses the server.
- **Pay only for websites that could be analysed.** Unreachable sites are listed with the reason, free.

### Input

```json
{ "urls": ["allbirds.com", "rdstation.com", "https://www.shopify.com"] }
```

### Output (one item per website)

```json
{
  "domain": "allbirds.com",
  "ecommerce": "Shopify",
  "emailProvider": "Microsoft 365",
  "cdn": "Cloudflare",
  "technologyCount": 6,
  "byCategory": {"Ecommerce": ["Shopify"], "Tag manager": ["Google Tag Manager"], "Analytics": ["Microsoft Clarity"], "...": []},
  "technologies": [{"name": "Shopify", "category": "Ecommerce", "evidence": "html: cdn.shopify.com"}]
}
```

### Example output

One real item from a test run (long texts and lists shortened):

```json
{
  "url": "https://rdstation.com",
  "finalUrl": "https://www.rdstation.com/",
  "domain": "rdstation.com",
  "siteOpened": true,
  "technologies": [
    {
      "name": "WordPress",
      "category": "CMS",
      "evidence": "html: /wp-content/"
    },
    {
      "name": "RD Station",
      "category": "Marketing automation",
      "evidence": "html: rdstation"
    },
    {
      "name": "Next.js",
      "category": "JavaScript framework",
      "evidence": "html: /_next/static/"
    }
  ],
  "technologyCount": 6,
  "byCategory": {
    "CMS": [
      "WordPress"
    ],
    "Marketing automation": [
      "RD Station"
    ],
    "JavaScript framework": [
      "Next.js"
    ],
    "CDN": [
      "Cloudflare"
    ],
    "Email provider": [
      "Google Workspace"
    ],
    "Email delivery": [
      "SendGrid"
    ]
  },
  "cms": "WordPress",
  "emailProvider": "Google Workspace",
  "cdn": "Cloudflare",
  "frontendFramework": "Next.js",
  "mxRecords": [
    "alt2.aspmx.l.google.com",
    "aspmx.l.google.com",
    "alt3.aspmx.l.google.com"
  ]
}
```

### How much does it cost?

You pay only for results delivered, at a fixed price per item. **Apify platform usage is included** in that price, so there are no compute costs on top. Errors and items that couldn't be found are free.

| What you get | Price | Example |
|---|---|---|
| Website analysed | $0.005 each | 1,000 website analyseds = $5.00 |

The Apify **Free plan includes $5 of monthly credit**, enough for about **1,000 website analyseds** per month at no cost. You can also set a maximum spend per run.

On paid Apify plans it gets cheaper automatically: **10% off on Starter, 20% on Scale and 30% on Business**.

# Actor input Schema

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

One per line: full URL or just the domain (example.com).

## `useResidentialFallback` (type: `boolean`):

If a site blocks the server IP and the regular proxy, try once more through a residential IP.

## `proxy` (type: `object`):

Used automatically for websites that block the server IP.

## Actor input object example

```json
{
  "urls": [
    "https://www.allbirds.com",
    "rdstation.com"
  ],
  "useResidentialFallback": true,
  "proxy": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `techstack` (type: `string`):

One item per website with detected technologies, grouped by category, plus email provider.

# 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.allbirds.com",
        "rdstation.com"
    ],
    "proxy": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("jeffev/website-tech-stack").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.allbirds.com",
        "rdstation.com",
    ],
    "proxy": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("jeffev/website-tech-stack").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.allbirds.com",
    "rdstation.com"
  ],
  "proxy": {
    "useApifyProxy": true
  }
}' |
apify call jeffev/website-tech-stack --silent --output-dataset

```

## MCP server setup

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

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/qNc7vRWlnObI3Shi0/builds/dSWO5WEetMhwtcDOh/openapi.json