# Bulk DNS, SPF, DMARC & SSL Checker + Tech Stack (`sipki/domain-passport`) Actor

Check SPF, DMARC, DKIM, MX, DNS records, SSL certificate expiry, mail provider and website tech stack for a list of domains. One JSON row per domain, ready for lead qualification, email deliverability audits and cert monitoring. $3 per 1,000 domains, unresolvable domains free.

- **URL**: https://apify.com/sipki/domain-passport.md
- **Developed by:** [SIPKI LLC](https://apify.com/sipki) (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

$3.00 / 1,000 domain profiles

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 Passport - bulk DNS, SPF/DMARC/DKIM, SSL certificate and tech stack checker

**Paste a list of domains, get one record per domain: DNS records, SPF, DMARC and DKIM, mail provider, SSL certificate expiry, security headers and tech stack - $3 per 1,000 domains.**

Answers questions like "which of these shops run Shopify and Google Workspace?", "which domains have no DMARC policy?" and "whose certificate expires this month?" in one run, without a browser or proxies.

**Try it now:** press **Start** with the prefilled input (three well-known company domains). Three records cost $0.009. In our cloud test 10 domains took 7.9 seconds.

### What you get per domain

- **DNS**: A, AAAA, MX, NS, TXT, CNAME
- **Email**: SPF (parsed: includes, qualifier, top-level lookup count), DMARC (policy, subdomain policy, pct, rua/ruf with the mailbox part masked as `***@`), DKIM selectors found among ~27 common ones, **mail provider** inferred from MX (Google Workspace, Microsoft 365, Zoho, Proton, Proofpoint, Mimecast, ...)
- **TLS certificate**: issuer, subject, validity dates, days left, SAN count, key type, protocol, chain trusted yes/no, hostname match
- **HTTP**: status, final URL after redirects, a curated set of response headers (security headers, server, cache, CDN hints), cookie *names* (never values), page title
- **Tech stack** from the home page: CMS, site builders, frameworks, e-commerce platforms, analytics, ad pixels, tag managers, CDN / hosting, consent tools, chat/support widgets (290+ detection rules)

### How it behaves (read this before you rely on it)

- **One home page per domain**, plus `robots.txt`. No crawling, no browser, no proxies, no CAPTCHA solving, no attempt to get around blocks.
- **robots.txt is always honoured** (RFC 9309), also on every redirect hop. If it disallows `/`, the page is not fetched and the record says `http.robots_blocked: true`. If robots.txt is unreachable, returns a 5xx, or answers 401/403/429, the page is not fetched either.
- Honest user agent: `SipkiDomainPassport/1.0 (+https://apify.com/sipki/domain-passport)`; it is never changed or rotated.
- **Blocks are respected:** if a site answers 403 or 429, the Actor does not retry, does not switch identity and does not use proxies. The record just shows the status.
- **Internal addresses are refused:** names or redirects that lead to private, loopback, link-local or cloud-metadata addresses (for example `10.x`, `127.0.0.1`, `169.254.169.254`) are never contacted; every redirect hop is checked.
- Domains on our opt-out block list are skipped (free record with `error: opted_out`).
- DNS lookups and the TLS handshake are ordinary protocol queries and do not involve fetching a web page.
- You are responsible for making sure that your use of the output complies with the law and with the terms that apply to the data you process.
- **HTTP-only detection**: no JavaScript is executed. Technologies that appear only after client-side rendering, and sites that answer with a bot-check page (HTTP 403/429), may show a partial or empty stack. In our test of 100 domains a technology stack was found for 86 and not found for 14 (6 were closed by robots.txt, 5 did not resolve, 3 of the 89 home pages actually fetched showed no detectable technology). Expect false negatives, not magic.
- DKIM selectors cannot be enumerated in DNS: "no selector found" does **not** mean "no DKIM".
- Detection rules are original to this Actor (not a copy of any third-party fingerprint database).

### Input

| Field | Meaning |
|---|---|
| `domains` | Domains or URLs, one per line (host only is used), up to 5000 |
| `fetchHomepage` | Fetch the home page for headers and tech stack (default on) |
| `checkDkim` | Probe common DKIM selectors (default on; turn off for faster runs) |
| `includeAllHeaders` | Return all response headers instead of the curated subset |
| `maxDomains` | Hard cap on domains in the run |

### Output (abridged)

```json
{
  "domain": "allbirds.com",
  "status": "ok",
  "mail_provider": "Microsoft 365 / Exchange Online",
  "email": {"spf": {"policy": "softfail", "includes": ["..."]}, "dmarc": {"policy": "reject"}, "dkim_selectors_found": ["selector1"]},
  "tls": {"issuer": "Let's Encrypt", "not_after": "2027-01-07", "days_left": 82, "chain_trusted": true},
  "http": {"status": 200, "final_url": "https://www.allbirds.com/", "robots": "ok", "headers": {"server": "cloudflare"}},
  "tech": [{"name": "Shopify", "category": "E-commerce", "via": "cookie"}, {"name": "Cloudflare", "category": "CDN", "via": "header"}]
}
```

`status` is `ok` (DNS + TLS + home page), `partial` (something obtained, e.g. DNS only because robots.txt blocks the page), or `dead` (nothing resolved).

### Pricing

Pay per event: **$0.003 per domain** (event `domain`). You are charged only for domains where at least something was obtained; unresolvable domains are free. The run stops when your spending limit is reached. Platform usage is small (a few seconds of a 256 MB container per 10 domains).

### Limitations

Home page only; no JavaScript rendering; WAF-protected sites may return 403/429; mail provider is inferred from MX only (a gateway such as Proofpoint or Mimecast hides the mailbox provider behind it).

### How to use

1. Paste domains or URLs into **Domains** (one per line, up to 5,000; for a full URL only the host name is used).
2. Turn off **Fetch home page** if you only need DNS and email checks, or **Check DKIM** for faster runs.
3. Press **Start**. Export as JSON, CSV or Excel, or call it from the Apify API, a schedule, an integration or the Apify MCP server.

### Who uses it

- **Sales and lead-gen teams** - qualify lists by mail provider, e-commerce platform and analytics stack.
- **Email deliverability and security teams** - find missing or weak SPF and DMARC across many domains.
- **IT and agencies** - monitor certificate expiry (`days_left`) on a schedule.

### More questions

**Does it return WHOIS (registrar, creation date)?** No. It covers DNS, email authentication, TLS and the home page.
**Why is DKIM "not found" for a domain that uses DKIM?** DKIM selectors cannot be listed in DNS; the Actor probes about 27 common selectors. "Not found" does not mean "no DKIM".
**What does a run of 1,000 domains cost?** $3.00. Domains that do not resolve are free.

### Not affiliated

Not affiliated with, endorsed or sponsored by any of the technology or service providers whose names appear in the output (for example Shopify, Cloudflare, Google, Microsoft). Product names are used only to identify detected technologies.

### Acceptable use

This Actor is a tool. You decide which sites, companies or files it processes and what you do with the results, and you are responsible for that use. Use it only where you have the right to access the data, and in line with applicable law (including data-protection, anti-spam and copyright law) and the terms of the sources. Do not use it to send unsolicited messages, to build lists for spam, to bypass blocks or access controls, or to place excessive load on any site. If a site owner asks us to stop, we may exclude that site. Sipki, LLC does not receive or store your results; they stay in your Apify storage.

### No warranty

The Actor and its output are provided "as is", without warranty of accuracy, completeness or fitness for a purpose. Verify results before relying on them. Liability of Sipki, LLC is limited as set out in the Apify Standard Actor Contract that governs your use of this Actor.

### Personal data

Results may contain personal data (for example, a mailbox name in a DNS record). For such data you are the controller and Sipki, LLC acts only as your processor under section 5 of the Apify Standard Actor Contract. You need a lawful basis for your processing and must handle data-subject requests. To request deletion of anything related to you, open an Issue on this Actor's page.

### For site owners (opt-out)

The Actor identifies itself as `SipkiDomainPassport/1.0 (+https://apify.com/sipki/domain-passport)`, fetches one home page and robots.txt per domain and follows robots.txt. To exclude your domain, or to report a problem, open an Issue on this Actor's page: your domain will be added to the block list within 3 business days, and every run checks that list.

# Actor input Schema

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

One per line: mycompany.org or a URL (https://www.mycompany.org/page - only the host is used). Up to 5000.

## `fetchHomepage` (type: `boolean`):

One GET of the home page (plus robots.txt). If robots.txt disallows it, the page is NOT fetched and the record says so. Turn off for DNS/TLS only.

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

Looks up TXT records for ~20 common selectors (google, selector1, k1, s1, ...). DKIM selectors are not enumerable, so 'none found' does not mean 'no DKIM'.

## `includeAllHeaders` (type: `boolean`):

Default returns a curated subset (server, security headers, cache, CDN hints). Cookie values are never returned, only names.

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

Hard cap for the run (also caps your cost).

## Actor input object example

```json
{
  "domains": [
    "stripe.com",
    "shopify.com",
    "github.com"
  ],
  "fetchHomepage": true,
  "checkDkim": true,
  "includeAllHeaders": false,
  "maxDomains": 5000
}
```

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

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

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

```

## MCP server setup

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

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/l7wkx5P0N8oJLG6cW/builds/U6vgtlGyhmby7abjg/openapi.json