# Website Tech Stack Detector: CMS, Analytics, Email, Age (`dataforge_api/website-tech-stack-ppe`) Actor

Detect the tech stack of websites from a domain list: CMS, e-commerce, frameworks, analytics, ads, chat, CDN, plus mail provider (MX), domain age (RDAP) and public role emails. Respects robots.txt.

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

## Pricing

Pay per event

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: CMS, Analytics, Email, Age

Give a list of domains, get the technology each site runs and a few facts that help prospecting. The Actor reads only the public homepage, its response headers, public DNS and public RDAP records. It checks `robots.txt` first and skips sites that disallow access.

### What you get per site

- **Technologies** with category and evidence: CMS (WordPress, Wix, Squarespace, Webflow, Drupal and more), e-commerce (Shopify, WooCommerce, Magento, BigCommerce), frameworks (Next.js, Nuxt, React, Vue, Angular), analytics and tag managers, advertising pixels, marketing tools (HubSpot, Klaviyo, Mailchimp), chat and support, payments, CDN, hosting and web server. About 70 signatures written for this Actor.
- **Deep profile (optional):** mail provider from MX records (Google Workspace, Microsoft 365, Mimecast and others), domain age, registrar and expiry from RDAP.
- **Contact hints:** role emails published on the homepage (info@, support@, sales@ and similar) and social links. Personal addresses are not returned.

### Use cases

Find all sites that use a given tool (`mustUseTechnology`), segment leads by stack or mail provider, spot new domains, or enrich a company list with its web technology.

### Limits

- Detection is based on the homepage only, so tools loaded on inner pages or after login are missed. A missing technology is not proof that it is not used.
- Technologies that load through a tag manager are not seen. Signatures can have false positives on pages that merely mention a tool in text; they are written to match code, not text.
- Sites that refuse automated requests or disallow robots are skipped and not charged. Nothing protected is bypassed.

### Pricing

Pay per event: `website-tech-stack-site` $0.004 per analysed site and `website-tech-stack-deep` $0.012 per site when mail provider or domain age is found. Unreachable, robots-disallowed and filtered-out sites are not charged.

# Actor input Schema

## `domains` (type: `array`):

Domains or URLs to analyse, for example stripe.com or https://www.bbc.com. Unreachable sites and sites that disallow robots are skipped and not charged.

## `mustUseTechnology` (type: `array`):

Optional filter. Keep only sites where every listed technology is detected, for example Shopify or Klaviyo. Names are matched exactly (case-insensitive). Sites that do not match are not charged.

## `deepProfile` (type: `boolean`):

Add the mail provider from DNS MX records and the domain age, registrar and expiry from RDAP. Charged as an extra event when at least one of them is found.

## `respectRobotsTxt` (type: `boolean`):

Skip domains whose robots.txt disallows automated access to the homepage.

## `maxResults` (type: `integer`):

Maximum number of site records saved in the run.

## Actor input object example

```json
{
  "domains": [
    "stripe.com",
    "allbirds.com",
    "techcrunch.com"
  ],
  "mustUseTechnology": [],
  "deepProfile": true,
  "respectRobotsTxt": true,
  "maxResults": 500
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

## `dataset` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("dataforge_api/website-tech-stack-ppe").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("dataforge_api/website-tech-stack-ppe").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 '{}' |
apify call dataforge_api/website-tech-stack-ppe --silent --output-dataset

```

## MCP server setup

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

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/QfON1diTwRTvbJ2i6/builds/gXwlUYvF1g4HenMKr/openapi.json
