# DNS Technographics - SaaS Stack from DNS Records (Bulk) (`dennydevelops/dns-technographics`) Actor

Find which SaaS any company uses (email, security, marketing automation, CRM, support, hosting, collaboration, AI) from its public DNS: SPF, TXT verification, MX, DMARC, nameservers, subdomain CNAMEs. Bulk and cheap.

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

## Pricing

Pay per event + usage

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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

## DNS Technographics – SaaS Stack from DNS Records

Find out which SaaS any company uses, in bulk, from its **public DNS records**. Page-based tech detectors only see what's on the homepage. DNS also reveals the back-office tools a company has connected to its domain: email and email security, marketing automation, CRM, support desk, collaboration, e-signature, payments, AI, hosting and CDN.

### What it reads

| Record | Reveals (examples) |
|---|---|
| SPF includes | Google Workspace, Microsoft 365, SendGrid, Mailgun, Amazon SES, HubSpot, Marketo, Salesforce, Zendesk, Klaviyo |
| TXT verification records | Atlassian, Slack, Zoom, DocuSign, Adobe, Stripe, OpenAI, Anthropic, Okta, 1Password, Canva, Miro, Notion, Meta Business |
| MX | Email provider and security gateway (Proofpoint, Mimecast, Barracuda, Cisco) |
| DMARC report address | DMARC vendor (dmarcian, Valimail, Red Sift, EasyDMARC…) |
| Nameservers | DNS and CDN provider (Cloudflare, Route 53, Akamai…) |
| CNAMEs of help., status., docs., careers., shop., go.… | Zendesk, Freshdesk, Intercom, Statuspage, GitBook, Greenhouse, Lever, Shopify, Marketo, Webflow… |

About 150 vendor signatures. Each detected tool comes with its evidence (the exact record), so you can verify it.

### Input

| Field | Default | Meaning |
|---|---|---|
| `domains` | – | Domains, website URLs or email addresses (the domain part is used) |
| `onlyIfUsing` | – | Only output domains using any of these vendors (e.g. `Zendesk`, `HubSpot`). Good for building lead lists |
| `checkSubdomains` | true | Also check common subdomains |
| `maxDomains` | 10000 | Cap per run |

### Output

```json
{
  "domain": "acme.com",
  "emailProvider": "Google Workspace", "emailSecurityGateway": null, "dmarcVendor": "dmarcian", "dnsProvider": "Cloudflare",
  "toolCount": 9,
  "categories": ["Collaboration", "Customer support", "Email", "Email delivery", "AI", "..."],
  "tools": [{"name": "Zendesk", "category": "Customer support", "evidence": ["SPF include mail.zendesk.com", "help.acme.com → acme.zendesk.com"]}, "..."],
  "spfIncludes": ["_spf.google.com", "sendgrid.net", "mail.zendesk.com"], "hasMx": true, "checkedAt": "…"
}
```

Verification token values are never output, only which vendor they belong to.

### Pricing (pay per event)

$0.001 per run and **$0.001 per domain**: 10,000 domains for about $10.

### How it works

Lookups go through DNS-over-HTTPS (Cloudflare, with Google as fallback), about 20 queries per domain, 10 domains at a time. It doesn't load the company's website.

# Actor input Schema

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

Domains, website URLs or email addresses (the domain is used).

## `onlyIfUsing` (type: `array`):

Vendor names, e.g. Zendesk, HubSpot, Microsoft 365 (any match). Every domain checked is still billed.

## `checkSubdomains` (type: `boolean`):

Look up help., status., docs., careers., shop. and similar for support, docs, recruiting and e-commerce tools.

## `maxDomains` (type: `integer`):

Caps work and cost per run.

## Actor input object example

```json
{
  "domains": [
    "stripe.com",
    "shopify.com",
    "apify.com"
  ],
  "checkSubdomains": true,
  "maxDomains": 10000
}
```

# Actor output Schema

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

No description

## `summary` (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",
        "apify.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("dennydevelops/dns-technographics").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",
        "apify.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("dennydevelops/dns-technographics").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",
    "apify.com"
  ]
}' |
apify call dennydevelops/dns-technographics --silent --output-dataset

```

## MCP server setup

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

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/o6dSwew81A11uGwFH/builds/e7amKDwOW9ep65fTk/openapi.json