# Tech Stack Detector + Email & DNS Stack Lookup (`donrulezz/tech-stack-email-dns`) Actor

Find the technologies behind any website (7,600+ fingerprints: CMS, ecommerce, frameworks, analytics, CDN, hosting, payments) plus its email & DNS stack: mail provider, sending services from SPF, DMARC policy, DNS host, TLS issuer. $2 per 1,000 sites.

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

## Pricing

from $1.40 / 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

## Tech Stack Detector + Email & DNS Stack Lookup

Find out **what any website is built with** and **how it handles email**, for one site or 100,000. Each result lists the technologies detected (CMS, ecommerce platform, JavaScript frameworks, analytics and marketing tags, CDN, hosting, payments, security headers and more) with version, category and confidence, **plus the company's email and DNS stack**: mailbox provider, the services it sends email through, its DMARC policy, DNS host and TLS certificate issuer.

Uses 7,600+ open technology fingerprints (the community-maintained successor of Wappalyzer's dataset, refreshed on every build), checked against the page HTML, scripts, meta tags, HTTP headers, cookies, robots.txt, DNS records and the TLS certificate. No browser is needed, so it's fast and cheap.

### What you get

| Field | Description |
|---|---|
| `technologies` | `name`, `version`, `categories`, `confidence`, `website`, `icon` for each technology |
| `byCategory` | Technologies grouped by category (CMS, Ecommerce, Analytics, CDN, JavaScript frameworks...) |
| `technologyNames`, `technologyCount` | Flat list for spreadsheets |
| `servicesFromDns` | SaaS the company has verified its domain with (TXT records such as DocuSign, Atlassian, Notion, Zoom, Stripe, OpenAI): what the company uses, not what its website runs |
| `emailDns.mailProvider` | From MX records: Google Workspace, Microsoft 365, Zoho, Proofpoint, Mimecast... |
| `emailDns.sendingServices` | From the SPF record: SendGrid, Mailchimp, HubSpot, Salesforce, Zendesk, Klaviyo, Amazon SES... |
| `emailDns.dmarcPolicy` | `reject`, `quarantine`, `none` or `missing` |
| `emailDns.dnsProvider`, `nameservers` | Cloudflare, Route 53, GoDaddy, Azure DNS... |
| `tlsIssuer` | Who issued the site's certificate (Let's Encrypt, Google Trust Services, DigiCert...) |
| `title`, `statusCode`, `finalUrl` | Page basics |

### Use cases

- **Lead generation and sales prospecting:** find every Shopify store using Klaviyo, or every company on Microsoft 365 without DMARC, and segment your list by stack. `servicesFromDns` adds the SaaS tools a company pays for (Notion, Zoom, Atlassian, DocuSign...).
- **Competitor and market research:** see which CMS, analytics and payment tools competitors use, and how a market splits between platforms.
- **Agencies and consultants:** audit a client's site and email setup in one pass before a pitch or a migration.
- **Security and IT due diligence:** spot outdated versions, missing security headers, weak DMARC and the mail gateway in front of a domain.
- **Enriching CRM and spreadsheet data:** add technology and email-provider columns to a list of company domains.

### Input example

```json
{
  "startUrls": ["https://www.allbirds.com", "https://vercel.com", "https://wordpress.org/news/"],
  "minConfidence": 50
}
```

### Output example

From a test run on 26 Oct 2026 (lists shortened):

```json
{
  "url": "https://www.allbirds.com",
  "statusCode": 200,
  "technologyNames": ["Shopify", "Cloudflare", "Google Tag Manager", "PayPal", "Apple Pay", "Swiper", "HSTS", "HTTP/3"],
  "byCategory": {"Ecommerce": ["Shopify"], "Payment processors": ["Apple Pay", "PayPal"], "CDN": ["Cloudflare"]},
  "servicesFromDns": ["DocuSign", "Microsoft 365", "Miro"],
  "emailDns": {
    "mailProvider": ["Microsoft 365"],
    "sendingServices": ["Microsoft 365"],
    "dmarcPolicy": "quarantine"
  },
  "tlsIssuer": "Let's Encrypt"
}
```

### Pricing

Pay per event: **$2 per 1,000 websites** (less on higher Apify plans). Sites that can't be loaded, or that return an HTTP error such as a 403 bot block, are **not charged**. Set a maximum spend per run in the run options; the actor stops cleanly when it is reached.

### Good to know

- Detection works on what a normal page load shows: technologies that appear only after JavaScript runs in a browser (some single-page-app internals) can be missed.
- The email & DNS stack comes from public DNS, so it works even when the website itself blocks bots.
- Sites behind strict bot protection may answer 403; turn on **Proxy** (residential works best). Those results are free.

### Credits

Technology fingerprints: [webappanalyzer](https://github.com/enthec/webappanalyzer) (GPL-3.0), the open, community-maintained continuation of the Wappalyzer fingerprints. Not affiliated with Wappalyzer or BuiltWith.

### FAQ

**Is this the same as Wappalyzer?** It uses the same open fingerprint format, maintained by the community, and adds the email and DNS stack. It is not the Wappalyzer product.

**Something wrong or a technology missing?** Open an issue on the actor's Issues tab and it will be fixed.

# Actor input Schema

## `startUrls` (type: `array`):

Websites to analyse, one per line (domain or URL). No limit.

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

Hide technologies detected with less confidence than this. Most detections are 100%.

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

How many websites to analyse at the same time (1-20).

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

Optional. Use Apify Proxy for sites that block data-centre traffic (fewer HTTP 403 errors).

## Actor input object example

```json
{
  "startUrls": [
    "https://www.allbirds.com",
    "https://vercel.com",
    "https://wordpress.org/news/"
  ],
  "minConfidence": 50,
  "maxConcurrency": 8,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

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

One row per site with technologies, mail provider, sending services, DMARC and DNS host.

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

Full items including versions, categories, icons and nameservers.

# 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 = {
    "startUrls": [
        "https://www.allbirds.com",
        "https://vercel.com",
        "https://wordpress.org/news/"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("donrulezz/tech-stack-email-dns").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 = { "startUrls": [
        "https://www.allbirds.com",
        "https://vercel.com",
        "https://wordpress.org/news/",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("donrulezz/tech-stack-email-dns").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 '{
  "startUrls": [
    "https://www.allbirds.com",
    "https://vercel.com",
    "https://wordpress.org/news/"
  ]
}' |
apify call donrulezz/tech-stack-email-dns --silent --output-dataset

```

## MCP server setup

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

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/2xX3ahdfagw7rczfj/builds/UxQBGKjuZyK4Zy1DV/openapi.json