# Domain Lookup: WHOIS/RDAP, DNS, Email Setup, Tech Stack (`dottti/domain-intel`) Actor

Bulk domain lookup: registrar, created and expiry dates from RDAP/WHOIS, DNS records, email setup (mail provider, SPF, DMARC, DKIM), hosting (IP, ASN, CDN), homepage, TLS certificate and tech stack. One row per domain. Change alerts. Unregistered and failed domains are free.

- **URL**: https://apify.com/dottti/domain-intel.md
- **Developed by:** [Dottti](https://apify.com/dottti) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

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

## Domain Lookup: WHOIS/RDAP, DNS, Email Setup, Tech Stack

Give a list of domains. Get one row per domain with its registration data, DNS records, email setup, hosting and tech stack.

Each row answers these questions:

- **Who registered it and when?** Registrar, created, updated and expiry dates, status codes, nameservers, DNSSEC, and the owner organisation and country when the registry publishes them.
- **How is DNS set up?** A, AAAA, NS, MX, TXT, CAA and SOA records.
- **How does it handle email?** Mail provider (Google Workspace, Microsoft 365, Zoho and 30 more), email security gateway, SPF, DMARC policy, DKIM keys, MTA-STS, BIMI, sending services found in SPF (Mailchimp, SendGrid, HubSpot and more), and services verified in TXT records (Google Search Console, Microsoft 365, Atlassian, OpenAI and about 60 more).
- **Where is it hosted?** IP, ASN, hosting provider, CDN, IP country and network owner.
- **What does the website run?** HTTP status, redirect chain, final URL, title, description, language, server, TLS certificate issuer and expiry, about 7,000 technologies (CMS, ecommerce, analytics, frameworks, CDN, payments, marketing tools), and social profile links.

All data comes from public sources: registry RDAP servers, registry WHOIS servers, public DNS-over-HTTPS resolvers, regional internet registries and the homepage itself. You need no API key.

### Who uses it

- **Sales and marketing teams** who enrich lead lists with the company's mail provider, CMS, ecommerce platform and marketing tools.
- **Security and IT teams** who audit SPF, DMARC and DKIM, certificate expiry and DNS setup across many domains.
- **Domain portfolio owners** who track expiry dates, registrars and status codes.
- **Researchers and analysts** who study hosting, CDN and technology use in a market, for example Saudi or UAE government sites.
- **Brand protection teams** who watch lookalike domains for new DNS, mail or website activity.

### Input examples

Check three domains with every module:

```json
{
  "domains": ["apify.com", "stc.com.sa", "github.io"]
}
```

Only registration and email setup, for a long list:

```json
{
  "domains": ["example.com", "example.org", "example.net"],
  "modules": ["rdap", "mail"],
  "maxConcurrency": 20
}
```

Alert mode for a weekly schedule:

```json
{
  "domains": ["mybrand.com", "mybrand.sa", "mybrand.ae"],
  "onlyChanged": true,
  "stateName": "brand-watch",
  "expiryAlertDays": 45
}
```

Domains can be plain names, URLs or subdomains. `https://www.Example.com/page` becomes `example.com`. Subdomains such as `shop.example.com` keep their own DNS and website checks, and use the registration data of `example.com`. Arabic and other non-Latin names (`münchen.de`) are converted to their ASCII form.

### Modules

| Module | What it adds | Source |
|---|---|---|
| `rdap` | Registrar, dates, status, nameservers, DNSSEC, owner organisation and country | Registry RDAP. Registry WHOIS for TLDs that have no RDAP (.io, .sa, .ae, .de, .co, .jo, .qa, .om and about 110 more) |
| `dns` | A, AAAA, NS, MX, TXT, CAA, SOA, www CNAME | Cloudflare DNS-over-HTTPS, Google as fallback |
| `mail` | Mail provider, gateway, SPF, DMARC, DKIM, MTA-STS, BIMI, sending and verified services, a 0-5 email authentication score | DNS |
| `hosting` | IP, ASN, provider, CDN, IP country, network name and owner | Team Cymru IP-to-ASN DNS service, regional registry RDAP (ARIN, RIPE, APNIC, LACNIC, AFRINIC) |
| `http` | Status, redirects, final URL, title, description, language, server, HSTS, TLS certificate, social links | The homepage |
| `tech` | Technologies with categories, versions and confidence, plus flat columns: `cms`, `ecommerce`, `analytics`, `jsFrameworks`, `cdnTech`, `marketing`, `payments` | Homepage headers, cookies, meta tags, HTML and scripts |

All modules are on by default. Turn off what you do not need and runs get faster. The price per domain stays the same.

### Output

Every row has a `type` field.

| type | One row is | Charged |
|---|---|---|
| `domain` | One domain with all the data you asked for | Yes |
| `status` | An input that gave no data: invalid, not registered, does not exist, failed or skipped | No |

#### Domain row (real output, 2026-10-26, some fields left out)

```json
{
  "type": "domain",
  "domain": "github.io",
  "status": "ok",
  "registered": true,
  "registrationSource": "whois (whois.nic.io)",
  "registrar": "MarkMonitor Inc.",
  "registrarIanaId": 292,
  "createdAt": "2013-03-08T19:12:48.000Z",
  "expiresAt": "2027-03-08T19:12:48.000Z",
  "domainAgeDays": 4979,
  "expiresInDays": 133,
  "expiringSoon": false,
  "domainStatus": ["client delete prohibited", "client transfer prohibited", "client update prohibited"],
  "dnssec": false,
  "registrantOrganization": "GitHub, Inc.",
  "registrantCountry": "US",
  "a": ["185.199.108.153", "185.199.109.153", "185.199.110.153", "185.199.111.153"],
  "ns": ["dns1.p05.nsone.net", "dns2.p05.nsone.net", "ns-1622.awsdns-10.co.uk", "ns-692.awsdns-22.net"],
  "caa": ["0 issue \"digicert.com\"", "0 issue \"letsencrypt.org\""],
  "acceptsMail": false,
  "spf": "v=spf1 a -all",
  "spfAll": "-all",
  "dmarcPolicy": null,
  "emailAuthScore": 2,
  "ip": "185.199.108.153",
  "asn": 54113,
  "asName": "FASTLY - Fastly, Inc., US",
  "hostingProvider": "Fastly",
  "cdn": "Fastly",
  "networkName": "US-GITHUB-20170413",
  "networkOrganization": "GitHub, Inc.",
  "httpStatus": 200,
  "finalUrl": "https://pages.github.com/",
  "redirectChain": ["301 https://github.io/"],
  "title": "GitHub Pages | Websites for you and your projects, hosted directly from your GitHub repository. Just edit, push, and your changes are live.",
  "server": "GitHub.com",
  "technologies": [
    { "name": "Fastly", "categories": ["CDN"], "version": null, "confidence": 100 },
    { "name": "GitHub Pages", "categories": ["PaaS"], "version": null, "confidence": 100 },
    { "name": "Jekyll", "categories": ["Static site generator"], "version": "3.10.0", "confidence": 100 }
  ],
  "technologyNames": ["Fastly", "GitHub Pages", "Jekyll", "jQuery", "Ruby", "Varnish"],
  "cms": "Jekyll",
  "tlsIssuerOrganization": "Let's Encrypt",
  "tlsValidTo": "2026-12-29T23:44:45.000Z",
  "tlsDaysLeft": 64,
  "tlsValid": true,
  "moduleStatus": { "rdap": "ok", "dns": "ok", "mail": "ok", "hosting": "ok", "http": "ok", "tech": "ok" },
  "errors": null
}
```

A Saudi domain (real output, email fields):

```json
{
  "domain": "stc.com.sa",
  "registrationSource": "whois (whois.nic.net.sa)",
  "registryNameservers": ["a1-200.akam.net", "a13-67.akam.net", "a20-64.akam.net"],
  "dnssec": true,
  "registrationNote": "This registry does not publish registration dates in WHOIS.",
  "mxHosts": ["imssvip1.stc.com.sa", "imssvipdr1.stc.com.sa"],
  "mailProvider": "Self-hosted or other",
  "spfAll": "-all",
  "dmarcPolicy": "reject",
  "dmarc": "v=DMARC1; p=reject; sp=none; fo=1; rua=<hidden>; ruf=<hidden>;pct=100",
  "dkimSelectorsFound": ["dkim"],
  "emailAuthScore": 5,
  "dnsVerifiedServices": ["Atlassian", "Cisco Webex", "GlobalSign", "Google Search Console", "Meta (Facebook)"],
  "hostingProvider": "Akamai",
  "cms": "Adobe Experience Manager",
  "socialLinks": { "linkedin": "https://www.linkedin.com/company/stc", "x": "https://twitter.com/stc_ksa", "youtube": "https://www.youtube.com/user/stcsaudiarabia" }
}
```

#### Status row (real output, free)

```json
{
  "type": "status",
  "domain": "nonexistzz98765qq.com",
  "status": "not_registered",
  "registered": false,
  "message": "The registry has no such domain. It may be available to register.",
  "charged": false
}
```

#### Status values

On `domain` rows:

- `ok`: every module you asked for answered.
- `partial`: some modules answered and some failed. `moduleStatus` and `errors` say which and why.

On `status` rows (free):

- `invalid_input`: the text is not a domain with a known public suffix.
- `not_registered`: the registry says the domain does not exist.
- `nxdomain`: DNS says the name does not exist, and no registry answered.
- `failed`: every lookup failed.
- `skipped_cost_limit`: your maximum cost for the run was reached.

`moduleStatus` values include `ok`, `not_registered`, `no_public_registry_lookup` (the TLD has no public RDAP or WHOIS, for example .kw and .eg), `registry_rate_limited`, `nxdomain`, `no_ip`, `no_website`, `blocked` (the homepage showed a bot check; headers are still used), `unreachable` and `headers_only_blocked`.

### Alert mode (onlyChanged)

Turn on `onlyChanged` and run the actor on a schedule. The first run returns every domain and saves a snapshot. Later runs return only domains where something changed, with a `changes` list:

```json
{
  "domain": "apify.com",
  "changeType": "changed",
  "changes": [
    { "field": "registrar", "before": "Old Registrar LLC", "after": "Amazon Registrar, Inc." },
    { "field": "mailProvider", "before": "Microsoft 365", "after": "Google Workspace" }
  ]
}
```

(Real output from a test where the saved snapshot was edited by hand.)

Tracked fields: registered, registrar, expiry date, status codes, nameservers, owner organisation, NS records, MX hosts, SPF, DMARC policy, mail provider, DKIM selectors, ASN, hosting provider, CDN, HTTP status, final URL, TLS issuer and technologies. A domain is also returned once when it enters the expiry window (`expiryAlertDays`).

IP addresses are not tracked, because CDNs rotate them between runs. A move to another network shows up as an ASN or hosting change. When a module fails in a run, its old values are kept and nothing is reported for it. Unchanged domains are not returned and not charged.

Each `stateName` is a separate watchlist. The snapshots are saved in the key-value store `domain-intel-state` in your account.

### How to schedule

1. Save your input as a task.
2. In the task, open **Schedules** and pick a cadence, for example every Monday.
3. Turn on `onlyChanged` so each run returns only what changed.
4. Add an integration (email, Slack, webhook, Google Sheets) to get the rows when the run ends.

### Pricing

You pay per domain row: **$1.50 per 1,000 domains** ($0.0015 per domain). Platform usage is included in the price.

Free, never charged: invalid inputs, domains that are not registered or do not exist, domains where every lookup failed, unchanged domains in alert mode, and domains skipped by your cost limit.

### Speed

In local tests, 50 mixed domains took 16 seconds with all modules on. At the default 256 MB, the CPU share is small, so our estimate is 30-40 minutes per 1,000 domains with all modules on. Registration and DNS only (`["rdap", "dns", "mail"]`) is several times faster. More memory gives more CPU, so a run with 1 GB finishes faster for the same price per domain.

### Limits and notes

- **Up to 10,000 domains per run.** Split bigger lists into several runs.
- **Registries limit WHOIS.** Some ccTLD registries block bulk WHOIS. The actor paces each registry and stops asking one that refuses. The domain row still comes back with DNS, mail, hosting and website data, and `moduleStatus.rdap` says `registry_rate_limited`.
  - .qa allows 100 lookups per hour per IP. The actor asks at most 90 .qa domains per run.
  - .ae publishes no limit, and blocked us after about 25 lookups in 20 minutes during testing. The actor asks at most 20 .ae domains per run, 6 seconds apart.
- **Some registries publish few fields.** .sa gives nameservers and DNSSEC but no registrar or dates. .ae gives the registrar and owner organisation but no dates. .de gives status, nameservers and last change only. .kw, .eg and about 60 other TLDs have no public lookup at all; for these, a domain with NS records counts as registered.
- **Privacy.** Personal data is never returned. From the registrant, only an organisation name and a country are kept, and only when the registry publishes them. Names of people, emails, phones and addresses are dropped. DMARC report addresses are shown as `<hidden>`. Personal LinkedIn profiles are not returned as social links.
- **Tech detection reads the homepage without a browser.** It sees headers, cookies, meta tags, HTML and script URLs. Technologies that only appear after JavaScript runs can be missed. Sites behind a bot check give header-only detection (`moduleStatus.tech: "headers_only_blocked"`).
- **Proxies.** RDAP, WHOIS and DNS never use a proxy. Only blocked homepages are retried through Apify Proxy (datacenter, then residential). Residential requests read at most 600 KB of the page.
- **DKIM** keys can only be found by selector name. The actor checks common selectors. Add your own in `dkimSelectors`.

### Run summary

The `RUN_SUMMARY` record in the default key-value store has counts by status, average and p95 time per module, requests and megabytes per 1,000 domains, and the proxy tier used for homepages.

### Technology fingerprints and licence

Technology detection uses the fingerprint set from [wappalyzergo](https://github.com/projectdiscovery/wappalyzergo) by ProjectDiscovery, released under the MIT licence. The licence text is in `data/LICENSE-wappalyzergo.md`. The actor uses a reduced copy (`data/technologies.json`) with the signals a plain HTTP fetch can see.

RDAP bootstrap files come from IANA. ASN data comes from Team Cymru's public IP-to-ASN service.

# Actor input Schema

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

Up to 10,000 domains per run. Plain names (example.com), URLs (https://www.example.com/page) and subdomains (shop.example.com) all work. Duplicates are removed. Use Bulk edit to paste a long list, one per line.

## `modules` (type: `array`):

Turn off what you do not need to make runs faster. Tech stack needs the homepage, so it also fills the website fields.

## `onlyChanged` (type: `boolean`):

For scheduled runs. The first run saves every domain and returns all of them. Later runs return only domains whose registrar, expiry date, status, nameservers, IPs, MX, SPF, DMARC, hosting, homepage, certificate or technologies changed, plus domains that enter the expiry window. Unchanged domains are not returned and not charged.

## `stateName` (type: `string`):

Name of the saved state for alert mode. Use a different name for each list you watch. The state lives in the key-value store 'domain-intel-state' of your account.

## `expiryAlertDays` (type: `integer`):

Sets expiringSoon to true when the domain expires within this many days. In alert mode a domain is returned once when it enters this window.

## `followRegistrarRdap` (type: `boolean`):

For .com and .net the registry has no owner data. This asks the registrar's RDAP server too, and keeps the organisation and country when they are public. Personal names, emails and phones are never returned. Adds one request per domain.

## `dkimSelectors` (type: `array`):

DKIM keys can only be found by name. These common selectors are tried (Google, Microsoft 365 and generic ones). Add your own if you know them. Max 20.

## `includeSocialLinks` (type: `boolean`):

Company profiles linked from the homepage: LinkedIn company page, X, Facebook, Instagram, YouTube, TikTok, GitHub, Snapchat, WhatsApp, Telegram. Personal LinkedIn profiles are skipped.

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

How many domains are checked at the same time. Registries are paced separately, so a high value cannot flood them.

## `requestTimeoutSecs` (type: `integer`):

Maximum wait for one request (homepage, RDAP, WHOIS).

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

Optional. RDAP, WHOIS and DNS never need a proxy. Leave empty to use the automatic ladder below.

## `autoProxyFallback` (type: `boolean`):

When a homepage answers with a bot check or 403/429, try again through a datacenter proxy.

## `allowResidentialFallback` (type: `boolean`):

If the datacenter proxy is blocked too, try one residential request. Platform usage is included in the price.

## Actor input object example

```json
{
  "domains": [
    "apify.com",
    "stc.com.sa",
    "noon.com",
    "github.io"
  ],
  "modules": [
    "rdap",
    "dns",
    "mail",
    "hosting",
    "http",
    "tech"
  ],
  "onlyChanged": false,
  "stateName": "default",
  "expiryAlertDays": 30,
  "followRegistrarRdap": false,
  "dkimSelectors": [
    "google",
    "selector1",
    "selector2",
    "default",
    "k1",
    "s1",
    "s2",
    "dkim",
    "mail"
  ],
  "includeSocialLinks": true,
  "maxConcurrency": 10,
  "requestTimeoutSecs": 20,
  "autoProxyFallback": true,
  "allowResidentialFallback": true
}
```

# Actor output Schema

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

All rows. Filter by the type field.

## `runSummary` (type: `string`):

Counts by status, timings per module, requests and bytes per 1,000 domains.

# 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": [
        "apify.com",
        "stc.com.sa",
        "noon.com",
        "github.io"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("dottti/domain-intel").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": [
        "apify.com",
        "stc.com.sa",
        "noon.com",
        "github.io",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("dottti/domain-intel").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": [
    "apify.com",
    "stc.com.sa",
    "noon.com",
    "github.io"
  ]
}' |
apify call dottti/domain-intel --silent --output-dataset

```

## MCP server setup

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

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/zQNRoqgri2kKSOckQ/builds/yrueWZU8k2qL1Osl3/openapi.json