# Tech Stack Detector – BuiltWith & Wappalyzer Alternative (`siftsmith/tech-enricher`) Actor

Tech stack lookup for any domain list: 84 common CMS, ecommerce, analytics, marketing, support, hosting/CDN and framework signatures from the homepage, plus email and DNS provider. $0.02 per profiled domain, not found = free. Works in Clay.

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

## Pricing

$20.00 / 1,000 domain reports

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

## Tech Enricher — Website Stack & Email/DNS Detector

Give it a list of domains. Get back the CMS, ecommerce, analytics, marketing, support, hosting/CDN, and frontend framework technologies each one runs — plus its email provider and DNS host, from public DNS records.

A pay-as-you-go alternative to Wappalyzer and BuiltWith. No subscription, no seat fees.

### What you get per domain

| Field | Example |
|---|---|
| `input` | `https://www.Stripe.com/pricing`: the input exactly as you gave it, on every row (including duplicates, skipped and not-found rows), so each row joins back to your list |
| `domain` | `stripe.com`: the domain the input reduces to (see "Input") |
| `technologies` | React, Next.js, Cloudflare, Google Analytics |
| `technologiesByCategory` | `{"Frontend": ["React"], "Hosting": ["Cloudflare"]}` |
| `emailProvider` | The inbound mail provider, from MX records. Mailbox providers: Google Workspace, Microsoft 365, Zoho Mail, ProtonMail, Fastmail, Amazon SES / WorkMail, Yandex 360, VK WorkSpace (Mail.ru). Mail security gateways in front of the mailbox: Mimecast, Proofpoint, Cisco Secure Email (IronPort), Broadcom/Symantec Email Security (MessageLabs), Barracuda Email Protection, Cloudflare Email Security (incl. Area 1), Trend Micro Email Security, Sophos Email, Hornetsecurity, Forcepoint Email Security. Consumer mail is `<Brand> (personal)`: `Outlook.com (personal)` for outlook.com/hotmail.com, `Gmail (personal)` for gmail.com, `Yahoo (personal)`, `Yandex (personal)`, `Mail.ru (personal)` and other free-mail domains, and any domain whose MX is the consumer Outlook.com service. Only the primary (lowest-numbered) MX records count, since that's where mail is delivered; a backup MX never names the provider. `null` when there's no MX or the primary MX isn't a recognised provider (e.g. self-hosted mail). Same answer as the `emailProvider` of our Email Security Signals Actor |
| `dnsProvider` | Cloudflare DNS, AWS Route 53, Google Cloud DNS, Google Domains, Google (own nameservers, e.g. google.com), Azure DNS, Vercel DNS, Netlify DNS, NS1, CSC, MarkMonitor, Akamai Edge DNS, GoDaddy DNS, … (from NS records). `null` when the nameservers aren't a recognised provider |
| `spfSenders` | third-party services allowed to send mail as this domain, from SPF `include:` and `redirect=` targets (up to 10). The domain's own SPF hosts (e.g. `_spf.example.com`) aren't listed; the services they include are, one level deep. Empty when the policy only lists IP ranges |
| `server`, `finalUrl`, `httpStatus` | raw signal for debugging |
| `parked` | `true` on a free `found: false` row for a parked or for-sale domain (see "Pricing") |
| `noSignal` | `true` on a free `found: false` row for a live homepage where nothing at all was detected |
| `dnsOnly` | `true` on a free `found: false` row whose homepage couldn't be read (unreachable, robots-blocked, error, bot-challenge or SSO sign-in redirect page) but whose email/DNS profile could; `technologies` is absent |

### How it works

100% public data, no logins:

- Fetches the domain's homepage (https, falling back to http) and matches its HTML, script tags, response headers, and Content-Security-Policy (which reveals tags loaded dynamically via a tag manager, not just static `<script>` tags) against fingerprints for 84 technologies: Analytics 15, CMS 11, Frontend 10, Hosting/CDN 9, Marketing 9, Support 7, CRM 5 (Salesforce, HubSpot CRM, Pipedrive, Zoho SalesIQ, Freshsales), Ecommerce 4, Recruiting/ATS 4, Payments 3, Video 3, Fonts 2, A/B testing 2. CRM fingerprints only count a script the page actually loads (a `<script src>` or the CSP), not a link or a mention in the text, so a link to a Salesforce login page or a domain like workforce.com doesn't read as "uses Salesforce".
- Looks up MX, NS, and TXT (SPF) records over DNS-over-HTTPS to identify the email provider, DNS host, and third-party mail senders.
- Respects `robots.txt`: skips domains that disallow root-path fetches.

### Use cases

- **Sales & RevOps:** find accounts running the stack you integrate with or replace (e.g. "on WooCommerce, not Shopify").
- **Recruiting agencies / hiring-signals pairing:** cross-reference detected ATS (Greenhouse/Lever/Ashby/Workable) with [Hiring Signals](https://apify.com/siftsmith/hiring-signals) for a full pipeline.
- **Competitive & market research:** track which analytics/marketing tools a market segment standardizes on.
- **Security/IT vendor risk:** inventory external services a domain depends on (CDN, email, chat, forms) without agent installs.

### Input

Domains, URLs, or email addresses. Each is reduced to its hostname: scheme, `www.`, `user@`, port, path, `?query` and `#fragment` are dropped, so `https://www.stripe.com/pricing?ref=abc` and `jane@stripe.com` both become `stripe.com`. A mistyped scheme (`http:/stripe.com`, `https:stripe.com`) is repaired the same way.

### Pricing

**$0.02 per profiled domain** ($20 per 1,000), versus $250–450/month for Wappalyzer or BuiltWith plans. Unreachable, robots-blocked and bot-protected domains (an HTTP 4xx/5xx error, or a bot-challenge or SSO sign-in redirect page served in place of the homepage), domains whose DNS lookup fails (retry those), parked or for-sale domains (a redirect to a domain-marketplace sale listing, parking-provider nameservers or mail servers, or a parking lander such as "This domain may be for sale"; the row carries `parked: true`), homepages where no technology, email provider, DNS provider or SPF sender is detected at all (a live but self-hosted or minimal site; the row carries `noSignal: true`), and unparseable, bare-IP and `localhost` / private-network inputs are free (returned as `found: false` with an `error`). When the homepage can't be read but the DNS lookups succeed and find at least one of an email provider, DNS provider or SPF sender (common for large sites behind bot protection), the free row also carries `dnsOnly: true` with `emailProvider`, `dnsProvider` and `spfSenders`, so you still get the email and DNS profile at no charge. If those DNS lookups fail, the row has `dnsLookupFailed: true` instead; retry the domain for its DNS profile. IP addresses and private names are rejected before anything is fetched. Set a max charge per run and you're never charged more than that: once it's reached, every remaining input still gets a short free row with `skipped: true` and a `reason` (bare-IP, `localhost` and private-network inputs keep their own `error` row), so no input goes missing from the dataset.

Duplicates are charged once. Inputs are deduplicated on the domain they reduce to, before anything is fetched: `stripe.com`, `STRIPE.COM`, `www.stripe.com` and `stripe.com?ref=abc` in one run give one charged profile. Each later duplicate still gets its own row, free, with its own `input` and `duplicateOf` set to the input that was profiled.

### Use it in Clay

Clay has a built-in Apify integration, so this works as a per-row enrichment column:

1. In your Clay table, add an enrichment, search **Apify**, and choose **Run Apify Actor**.
2. Connect your Apify account with your Apify API token (Apify Console → Settings → Integrations).
3. Pick this Actor and enter the input as JSON, putting the row's value into the `domains` list. Clay's [Apify integration guide](https://university.clay.com/docs/apify-integration-overview) shows how to insert a column into the JSON.
4. Run the column. Each row's result comes back into Clay, where you can split fields such as `technologies` into their own columns.

Billing: Apify charges $0.02 per profiled domain (unreachable domains are free) to your Apify account, with no per-run start fee. Clay counts the Action on its side but uses no Clay data credits when you bring your own Apify account.

### Limits & honesty

- Covers 84 widely used technologies, not BuiltWith's or Wappalyzer's full catalogue.
- Homepage-only detection: technologies used exclusively on subpages (e.g. checkout, docs) won't show up.
- Signatures favor precision over recall — some technologies won't be flagged if they don't leave a homepage-visible marker. Report `found: false` and inaccuracies as an issue; fingerprints get added on request.
- No firmographic data (employee count, revenue, etc.) is included — none of that is available from public, unauthenticated sources without violating a platform's terms.

### Related tools

- [Buyer Intent Signals](https://apify.com/siftsmith/buyer-intent-signals): combines this tech-stack check with a hiring score into one 0–100 intent score per company, scored higher (×1.5, capped at 100) when a hiring company doesn't run the tool category you sell.
- [Hiring Signals](https://apify.com/siftsmith/hiring-signals): a company's open jobs, recent posting velocity and hiring score from its public job board.

### Support

Open an issue on the Actor's Issues tab or email hello@siftsmith.com. Issues are read daily and fixed promptly.

More tools from Siftsmith (formerly ToolFoundry): [siftsmith.com](https://siftsmith.com/).

# Actor input Schema

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

Domains or URLs to profile, e.g. 'stripe.com' or 'https://ramp.com'. URLs are reduced to their domain. Returns one row per input with the site's technologies by category (CMS, ecommerce, analytics, marketing, support, hosting/CDN, frontend), its email provider, DNS host and SPF mail senders.

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

How many domains to process in parallel.

## Actor input object example

```json
{
  "domains": [
    "stripe.com",
    "ramp.com",
    "webflow.com"
  ],
  "maxConcurrency": 5
}
```

# 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 = {
    "domains": [
        "stripe.com",
        "ramp.com",
        "webflow.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("siftsmith/tech-enricher").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 = { "domains": [
        "stripe.com",
        "ramp.com",
        "webflow.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("siftsmith/tech-enricher").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 '{
  "domains": [
    "stripe.com",
    "ramp.com",
    "webflow.com"
  ]
}' |
apify call siftsmith/tech-enricher --silent --output-dataset

```

## MCP server setup

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

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/BN6TvmV727aOANIRu/builds/M11BZjgxD2uppQYgm/openapi.json