Domain Intel: WHOIS/RDAP, DNS, SPF/DMARC, SSL & Tech Stack API

Domain lookup API for AI agents and data pipelines: WHOIS-style registration data via RDAP, all DNS records, an SPF/DMARC/DKIM email-security grade, the live SSL/TLS certificate, the website's tech stack and optional subdomains, in one JSON result per domain. Use it as an MCP tool in Claude or Cursor, or in bulk from the API, n8n, Make or Zapier.

One domain in, one clean JSON profile out. Registration, DNS, email-security grade, live TLS certificate and the website's tech stack in a few seconds, plus optional certificate-transparency history with subdomains. Public sources only. Built for AI agents, lead-enrichment pipelines, security triage and vendor checks.

Price: $0.005 per domain (pay per event). No start fee. Invalid domains, unregistered or non-resolving domains, and lookups where every check fails are free. Duplicates in one run are billed once.

Pricing examples: 100 domains = $0.50, 1,000 domains = $5, 10,000 domains = $50. An agent checking one domain pays half a cent. Apify's free plan includes monthly platform credit, enough for hundreds of lookups.

What you get per domain

Section	What is in it	Source
registration	Registrar (name, IANA ID, abuse contact), created / updated / expiry dates, domain age, days to expiry, status codes, nameservers, DNSSEC delegation	RDAP (the official successor to WHOIS), via the IANA bootstrap registry
dns	A, AAAA, CNAME, NS, MX, TXT, CAA, SOA, DNSSEC validation flag	DNS over HTTPS (Cloudflare, Google fallback)
emailSecurity	SPF (qualifier, includes, lookup count, issues), DMARC (policy, pct, reporting), DKIM keys on 20 common selectors, MTA-STS policy, TLS-RPT, BIMI, a 0-100 score and an A-F grade	DNS + the domain's MTA-STS policy file
tls	Live certificate: issuer, validity, days left, SANs, key type, fingerprint, chain, trust and hostname match, negotiated TLS version	Direct TLS handshake on port 443
certificateTransparency (optional, off by default)	Total certificates, first seen, last issued, issuer mix, discovered subdomains, wildcards, newest certificates	crt.sh (Cert Spotter fallback)
techStack	CDN, hosting, web server, CMS, framework, analytics, ads, chat, payments, consent and monitoring tools, plus mail provider, email senders, DNS host and SaaS verified on the domain. Each with a category, a 0-100 confidence and the signals that matched. Page title, security headers	One GET of the homepage (headers, cookies, script/link URLs, HTML), DNS (MX, SPF, TXT, NS, CNAME), robots.txt and security.txt. No browser
summary	Flat one-line view: registrar, dates, DNS and mail provider, email grade, DMARC policy, TLS issuer and expiry, subdomain count, technologies	Derived

Each section has ok, ms and either data or error, so one slow or broken source never sinks the rest.

Privacy

Registrant, admin, technical and billing contacts are never returned, even when a registry publishes them. Only the registrar (a business) is kept, plus a flag saying whether the registry redacted registrant data. No WHOIS scraping, no logins, no proxies.

Input

{
  "domains": ["stripe.com", "https://www.bbc.co.uk/news", "ceo@shopify.com"],
  "modules": ["rdap", "dns", "email", "tls", "tech"],
  "includeCertificateHistory": false,
  "dkimSelectors": ["s1024"],
  "ctMaxRecent": 20,
  "ctMaxSubdomains": 200,
  "maxConcurrency": 5
}

Only domains is required. URLs and email addresses are reduced to their hostname. Leave modules empty for all the fast checks.

Certificate history is optional

Certificate-transparency history (certificateTransparency: total certificates, first seen, issuers, discovered subdomains) is off by default because it is much slower: crt.sh can take up to about 60 seconds per domain and is sometimes unavailable. Turn it on with "includeCertificateHistory": true (or by listing ct in modules). The price stays $0.005 per domain either way. Without it a typical domain takes 2-4 seconds.

Output (trimmed)

{
  "domain": "stripe.com",
  "success": true,
  "summary": {
    "registrar": "SafeNames Ltd.",
    "registeredAt": "1995-09-12T04:00:00Z",
    "domainAgeDays": 11368,
    "dnsProviderHint": "Amazon Route 53",
    "mailProviderHint": "Google Workspace",
    "emailSecurityGrade": "A",
    "dmarcPolicy": "reject",
    "tlsIssuer": "DigiCert, Inc.",
    "tlsDaysToExpiry": 195,
    "ctSubdomains": 73,
    "technologies": ["nginx", "Next.js"]
  },
  "registration": { "ok": true, "ms": 391, "data": { "...": "..." } },
  "emailSecurity": { "ok": true, "ms": 675, "data": { "grade": "A", "score": 85, "spf": {}, "dmarc": {}, "dkim": {}, "mtaSts": {} } }
}

Use with AI agents (MCP)

Through the Apify MCP server, your agent gets this Actor as a tool and can answer questions like "Is acme.com's DMARC set to reject?", "Who hosts this domain and when does its certificate expire?" or "Which of these 20 leads use Google Workspace?".

Add this to Claude Desktop (claude_desktop_config.json), Cursor (.cursor/mcp.json), VS Code or any client that supports remote MCP servers:

{
  "mcpServers": {
    "domain-intel": {
      "url": "https://mcp.apify.com/?tools=reynolds/domain-intel"
    }
  }
}

The client opens an Apify sign-in the first time. To use a token instead, add "headers": { "Authorization": "Bearer <APIFY_TOKEN>" }. Claude Code: claude mcp add --transport http domain-intel "https://mcp.apify.com/?tools=reynolds/domain-intel". Local (stdio) clients: npx -y @apify/actors-mcp-server --tools reynolds/domain-intel with APIFY_TOKEN in the environment.

Pair it with Company Hiring Signals for account research: ?tools=reynolds/domain-intel,reynolds/company-hiring-signals.

Integrations: API, n8n, Make, Zapier, LangChain

• REST API (run and get results in one call):

  curl -X POST "https://api.apify.com/v2/acts/reynolds~domain-intel/run-sync-get-dataset-items" \
    -H "Authorization: Bearer $APIFY_TOKEN" -H "Content-Type: application/json" \
    -d '{"domains": ["stripe.com", "shopify.com"]}'
  

• n8n: add the Apify node, choose "Run an Actor and get dataset", Actor reynolds/domain-intel, input {"domains": ["{{ $json.website }}"]}. Useful for enriching CRM leads or alerting on certificates close to expiry.

• Make and Zapier: use the Apify app's "Run an Actor" action with the same Actor and input, then map summary fields into your sheet or CRM.

• LangChain (Python):

  from langchain_apify import ApifyActorsTool
  domain_tool = ApifyActorsTool("reynolds/domain-intel")
  

Good to know

• Speed: with the defaults a domain takes about 2-4 seconds. Certificate history (opt-in) depends on crt.sh, a free community service that can take 30-60 seconds for big domains or be briefly down; we then fall back to Cert Spotter (partial: currently unexpired certificates, first page only) and mark the result partial. To be a good citizen we send crt.sh one request at a time, so in large runs most domains get the Cert Spotter view. Leave it off unless you need it.
• DKIM: DNS cannot list DKIM keys, so we probe 20 common selectors. "None found" does not prove DKIM is off. Add selectors you know in dkimSelectors.
• RDAP coverage: all gTLDs, every ccTLD in the IANA RDAP registry, plus .de, .io, .co, .me, .us, .ch, .sh and .ac via their registries' own RDAP servers. Some ccTLDs (for example .it, .es, .se, .jp, .eu) have no public RDAP server; for those registration fails with a clear error and the other sections still run.
• Tech stack is a light fingerprint from the homepage only (no crawling, no JavaScript execution), so client-side-only tools can be missed.

FAQ

Is this a WHOIS lookup? It uses RDAP, the official, structured successor to WHOIS run by the same registries. You get registrar, dates, status and nameservers, without personal contact data.

Can I check SPF, DKIM and DMARC in bulk? Yes. Send up to thousands of domains in domains; each gets an emailSecurity section with a 0-100 score and an A-F grade.

Does it find subdomains? Yes, when you turn on includeCertificateHistory. Subdomains come from certificate-transparency logs (crt.sh, with Cert Spotter as fallback).

How fast is it? About 2-4 seconds per domain with the defaults, with several domains processed in parallel.

What if one check fails? The others still run. Each section has its own ok flag and error. If every check fails, you are not charged.

Use cases

Lead enrichment (company age, mail provider, stack), email deliverability and spoofing audits, vendor and phishing-domain triage, attack-surface discovery via CT subdomains, certificate expiry monitoring, and agent tool calls that need "tell me about this domain" in one step.

Support

Open an issue on the Actor's Issues tab. Responses within 2 working days.