# Website & Email Domain Checker: SSL, DNS, SPF, DMARC, DKIM (`damodaran_dhanuauraman/website-email-domain-checker`) Actor

Bulk domain checker: website status, redirects, SSL expiry, security headers, MX email provider, SPF/DMARC grade, common DKIM selectors, tech hints and AI-crawler robots.txt. $8 per 1,000 domains.

- **URL**: https://apify.com/damodaran_dhanuauraman/website-email-domain-checker.md
- **Developed by:** [Damodaran Dhanusuraman](https://apify.com/damodaran_dhanuauraman) (community)
- **Categories:** Developer tools, SEO tools, Lead generation
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$8.00 / 1,000 domain checkeds

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

## Website & Email Domain Checker: SSL, DNS, MX, SPF, DMARC, DKIM

**Bulk domain checker API: SSL certificate expiry, SPF, DMARC, DKIM, MX email provider, HTTP status and tech stack for a list of domains. One JSON row per domain, $0.008 per domain, invalid domains free.**

Bulk-check any list of domains or URLs in one run and get one clean JSON record per domain:

- **Website health**: HTTP status, full **redirect chain**, final URL, HTTPS enforcement, **response time**. Plain-HTTP-only sites work too (automatic https → http fallback, flagged as `plainHttpOnly`)
- **SSL/TLS certificate**: valid or not, issuer, **expiry date and days left**, TLS version
- **Security headers**: HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, COOP, with a 0–100 score
- **Email setup**: does the domain receive mail (**MX records**), which **email provider** (Google Workspace, Microsoft 365, Zoho, Proofpoint…), **SPF**, **DMARC** policy, **DKIM** (common selectors probed), and an **A–F email-authentication grade**
- **Tech stack hints** (fingerprints): CDN/hosting (Cloudflare, CloudFront, Vercel, Netlify…), CMS (WordPress, Shopify, Wix, Webflow…), frameworks and analytics tags
- **AI readiness**: which AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended…) robots.txt blocks, and whether `/llms.txt` exists
- **DNS**: A/AAAA, NS, CAA, TXT domain-verification hints (Google, Microsoft, Atlassian, Stripe…)

Public data only: DNS queries, one TLS handshake, the homepage, `robots.txt` and `llms.txt`. No logins, no personal data, no scraping behind walls.

### Use cases

- **Sales and GTM teams, Clay, n8n and Make users**: qualify leads by email provider, tech stack and whether the website is alive.
- **Agencies and freelancers**: instant website and email-deliverability audit for prospects ("your DMARC is missing, your SSL expires in 9 days").
- **IT, security and deliverability teams**: monitor SSL expiry and SPF/DMARC/DKIM across many domains on a schedule.
- **AI agents (MCP)**: a cheap, fast tool for "check this domain's email security / SSL / tech stack".

### Input

| Field | Type | Default | Notes |
|---|---|---|---|
| `domains` | array of strings | — (required) | Domains or URLs. Duplicates removed. |
| `maxDomains` | integer | 1000 | Budget guard. |
| `checkDkim` | boolean | true | Probes ~19 common DKIM selectors. |
| `dkimSelectors` | array | — | Replace the default selector list. |
| `checkRobots` | boolean | true | AI-crawler policy and llms.txt. |
| `dnsResolver` | `doh` / `system` | `doh` | DNS-over-HTTPS (Cloudflare, Google fallback) or the container resolver. |
| `timeoutSecs` | integer | 15 | Hard limit per HTTP/TLS request (connect + response). Each domain also has an overall cap, so one slow site never stalls the run. |
| `maxConcurrency` | integer | 10 | Parallel domains (max 50). |

Example input:

```json
{ "domains": ["stripe.com", "https://www.github.com/features", "example.com"], "maxConcurrency": 10 }
```

### Output (one item per domain)

Each item has `summary` (flat, spreadsheet-friendly), plus `website`, `ssl`, `dns`, `email` and `errors`. Trimmed example from a real run (stripe.com, 3 Nov 2026; live values change over time):

```json
{
  "domain": "stripe.com",
  "ok": true,
  "summary": { "resolves": true, "websiteUp": true, "sslValid": true, "sslDaysLeft": 187, "mailConfigured": true,
               "mailProvider": "Google Workspace", "emailAuthGrade": "A", "securityHeadersScore": 86, "responseTimeMs": 2535 },
  "website": { "finalUrl": "https://stripe.com/in", "finalStatus": 200, "redirectCount": 1, "httpsEnforced": true,
               "techHints": ["Next.js", "nginx"], "robots": { "aiCrawlersBlocked": [] }, "llmsTxt": { "present": true } },
  "ssl": { "valid": true, "issuer": "DigiCert, Inc.", "validTo": "2027-05-09T23:59:59.000Z", "daysUntilExpiry": 187, "protocol": "TLSv1.3" },
  "email": { "hasMailSetup": true, "provider": "Google Workspace", "spf": { "allQualifier": "~" }, "dmarc": { "policy": "reject" },
             "dkim": { "selectorsFound": ["google", "mandrill", "s1", "s2"] }, "authGrade": "A" }
}
```

More examples: `samples/input.example.json`, `samples/output.sample.json` (full run on 9 inputs, including invalid and non-existent domains).

Export as JSON, CSV, Excel, or use the **Overview** table view.

### Pricing (pay per event)

- **$0.008 per domain checked** (`domain-checked` event) — $8 per 1,000 domains.
- Invalid inputs and domains that do not resolve are **free** (pushed with an error, not charged).
- The run stops cleanly when your spending limit is reached.

### Limits and accuracy notes

- **DKIM**: DNS cannot list DKIM selectors; common ones are probed. "No selector found" does not prove DKIM is absent. Wildcard `_domainkey` records are detected and ignored.
- **Tech hints** are lightweight fingerprints from headers and homepage HTML, not a full BuiltWith-style crawl.
- Response time is measured from the Actor's server location.
- Only the homepage, `robots.txt` and `llms.txt` are fetched. It is not a site crawler or a vulnerability scanner.
- Sites that block datacenter traffic or rate-limit may show errors or different status codes than in your browser.
- `emailAuthGrade` is a simple score: SPF (35), DMARC policy (40), DKIM found (25).

### How it compares

- **vs. a plain DNS or SPF/DMARC lookup tool:** those return DNS records only, and some cost less per domain. This Actor also does a TLS handshake (certificate expiry, issuer, TLS version), fetches the homepage (status, redirects, HTTPS enforcement, response time, security headers, tech hints) and reads `robots.txt` / `llms.txt`. If you only need DNS records, a DNS-only tool may be the cheaper choice.
- **vs. BuiltWith or Wappalyzer:** tech hints here are light fingerprints from one homepage, not a full technology profile. Use those tools if tech detection is your main need.
- **vs. a vulnerability scanner:** this is not one. It reads public records and one page and does not probe for weaknesses.

### Schedule it (SSL and email-auth monitoring)

1. Save your domain list as a **Task** in Apify Console.
2. Add an **Apify Schedule** (for example every Monday 09:00).
3. In your integration, alert when `summary.sslDaysLeft` < 21, `summary.emailAuthGrade` is D or F, or `summary.websiteUp` is false.

Keep `checkDkim: false` on very large lists if you want faster runs.

### Use in Clay, n8n, Make or any HTTP tool

**Any HTTP tool (one call, results in the response):**

```
POST https://api.apify.com/v2/acts/damodaran_dhanuauraman~website-email-domain-checker/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>
Content-Type: application/json

{ "domains": ["example.com", "stripe.com"], "checkDkim": false }
```

**Clay:** add an Apify enrichment ("Run Apify Actor"), choose `damodaran_dhanuauraman/website-email-domain-checker`, set the input to `{"domains": ["<Company Domain column>"], "checkDkim": false}`, then map `summary.mailProvider`, `summary.emailAuthGrade`, `summary.websiteUp`, `summary.sslDaysLeft` and `website.techHints`. Skip rows without a domain. Rows with an invalid domain are not charged.

**n8n / Make:** Schedule trigger → read domains (e.g. Google Sheets) → Apify "Run Actor" (or the HTTP request above) → filter on the `summary` fields → Slack or email alert.

### Use with AI agents, API and integrations

Call it from the Apify API, the Apify MCP server (tool name follows the Actor name), Clay, n8n, Make or Zapier. Typical agent prompt: *"Check the SSL expiry, email provider and DMARC policy of these 50 domains."* Schedule it daily or weekly to monitor SSL expiry and email-auth changes.

### Feedback

Found a wrong result? Open an issue in the **Issues** tab with the domain and the field that looks wrong.

### FAQ

**Is this legal?** It only reads public DNS records and public web pages, the same as any browser or `dig`.
**Does it collect personal data?** No. It returns technical records about domains only.
**How much does a run cost?** $0.008 per domain that resolves. 100 domains = $0.80. Invalid and non-resolving domains are free.
**How fast is it?** Usually a few seconds per domain, 10 in parallel by default (up to 50).
**Can it watch for changes?** Run it on a schedule and compare `summary` fields between runs in your sheet or workflow. It does not store history itself.
**Can I check subdomains?** Yes. The host you enter is fetched; email checks run on the registrable domain with `www.` stripped.

Keywords: SSL certificate checker, SSL expiry monitor, DMARC checker, SPF checker, DKIM lookup, MX lookup, email provider lookup, domain checker, website status checker, redirect checker, security headers scanner, tech stack lookup, BuiltWith alternative, Wappalyzer alternative, llms.txt checker, AI crawler robots.txt checker.

# Actor input Schema

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

Domains or URLs to check, e.g. "stripe.com" or "https://www.example.org/page". Duplicates are removed. Only the domain/host is used.

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

Stop after this many domains (protects your budget).

## `checkDkim` (type: `boolean`):

DKIM keys cannot be listed via DNS. When on, about 19 common selectors (google, selector1, selector2, k1, ...) are probed.

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

Optional. Replaces the default selector list.

## `checkRobots` (type: `boolean`):

Reports which AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, ...) are blocked, and whether /llms.txt exists.

## `timeoutSecs` (type: `integer`):

Timeout for each HTTP or TLS request.

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

How many domains to check in parallel.

## `dnsResolver` (type: `string`):

"doh" = DNS-over-HTTPS via Cloudflare with Google fallback (consistent results anywhere). "system" = the container's own resolver.

## Actor input object example

```json
{
  "domains": [
    "apify.com",
    "example.com"
  ],
  "maxDomains": 1000,
  "checkDkim": true,
  "checkRobots": true,
  "timeoutSecs": 15,
  "maxConcurrency": 10,
  "dnsResolver": "doh"
}
```

# Actor output Schema

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

One row per domain: website status, SSL, security headers, MX, SPF/DMARC/DKIM grade, tech stack, AI-crawler rules.

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

// Run the Actor and wait for it to finish
const run = await client.actor("damodaran_dhanuauraman/website-email-domain-checker").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",
        "example.com",
    ] }

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

```

## MCP server setup

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

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/E04D97TmnUABZNtdC/builds/5PPFHbGs7a8HNn97K/openapi.json