# Tech Stack & DNS Detector: Website Tech, Email Provider, SaaS (`jobdata_labs/tech-stack-dns-detector`) Actor

From a domain: website technologies (CMS, frameworks, analytics, pixels, chat, payments, CDN) plus email provider, email senders (HubSpot, Salesforce...) and verified SaaS (Atlassian, Slack, DocuSign...) from public DNS.

- **URL**: https://apify.com/jobdata_labs/tech-stack-dns-detector.md
- **Developed by:** [Momi](https://apify.com/jobdata_labs) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 domains

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 Stack & DNS Detector — website technologies + email provider + SaaS tools

Find out **what a company runs on** from just its domain: website technologies **and** the business tools that only show up in **public DNS records** — email provider (Google Workspace, Microsoft 365…), email/marketing senders (HubSpot, Salesforce, Mailchimp, SendGrid…) and verified SaaS accounts (Atlassian, Slack, DocuSign, Zoom, OpenAI, Miro…).

Most tech detectors only read the HTML of a page. For B2B prospecting, knowing that a company **uses Microsoft 365 and HubSpot and has an Atlassian account** is often worth more than knowing it uses jQuery. This Actor gives you both in one row.

### What it detects

**From the homepage** (one request per domain, robots.txt respected): CMS & website builders (WordPress, Shopify, Webflow, Wix, Framer, Drupal…), JavaScript frameworks (Next.js, Nuxt, React, Vue, Angular…), analytics & tag managers, ad pixels (Meta, LinkedIn, TikTok, Google Ads…), marketing automation, live chat & support, payments, cookie consent, CDN & hosting (Cloudflare, Vercel, Netlify, CloudFront…), monitoring, A/B testing and more — ~120 rules.

**From public DNS:** email provider and email security gateway (MX), email sending services (SPF), verified SaaS (TXT verification records), DMARC policy, DNS provider (NS).

### Output example

```json
{
  "domain": "bunq.com",
  "emailProvider": "Google Workspace",
  "emailSendingServices": ["Mailchimp", "Salesforce", "Mandrill", "Google Workspace"],
  "verifiedServices": ["Apple", "DocuSign", "Miro", "Postman", "Microsoft 365"],
  "dnsProvider": "AWS Route 53",
  "dmarcPolicy": "reject",
  "technologies": [
    { "name": "Framer", "category": "Website builder", "evidence": "html" },
    { "name": "Sentry", "category": "Monitoring", "evidence": "html" }
  ],
  "allTechnologies": ["Google Workspace", "Mailchimp", "Salesforce", "DocuSign", "Miro", "Framer", "Sentry"],
  "technologyCount": 13
}
```

### Use cases

- **Lead generation & segmentation:** find companies on Microsoft 365 vs Google Workspace, on HubSpot vs Salesforce, on Shopify vs WooCommerce.
- **Competitive intelligence:** see which tools competitors and prospects adopt.
- **Sales personalization:** mention the stack the prospect already uses.
- **Email deliverability audits:** check SPF and DMARC policy across many domains.

### Pricing

Pay per event: **one fee per domain analyzed**. Domains that don't exist are not charged.

### Notes & limits

- Detection is signature-based: a technology loaded only after login or user interaction may not be visible.
- Sites that block automated access or disallow crawling in robots.txt are not fetched; DNS results are still returned.
- No personal data is collected.

# Actor input Schema

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

One per line, e.g. stripe.com or https://www.notion.so. Only the homepage is fetched (robots.txt respected); DNS records are public.

## `checkWebsite` (type: `boolean`):

Fetch the homepage and detect CMS, frameworks, analytics, ads pixels, chat, payments, consent tools, CDN and hosting.

## `checkDns` (type: `boolean`):

Read public MX, SPF, TXT verification, DMARC and NS records: email provider, email sending tools, verified SaaS (Atlassian, Slack, DocuSign...), DNS provider.

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

How many domains are analyzed at the same time.

## Actor input object example

```json
{
  "domains": [
    "stripe.com",
    "shopify.com",
    "notion.so"
  ],
  "checkWebsite": true,
  "checkDns": true,
  "maxConcurrency": 10
}
```

# 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",
        "shopify.com",
        "notion.so"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("jobdata_labs/tech-stack-dns-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 = { "domains": [
        "stripe.com",
        "shopify.com",
        "notion.so",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("jobdata_labs/tech-stack-dns-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 '{
  "domains": [
    "stripe.com",
    "shopify.com",
    "notion.so"
  ]
}' |
apify call jobdata_labs/tech-stack-dns-detector --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jobdata_labs/tech-stack-dns-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/1UbVJMNZjLHA9Pf1c/builds/07TIDJSP2NHl3LM0s/openapi.json