Domain Intelligence: WHOIS, DNS, SSL & Tech Stack

One run gives you a complete technical profile of any domain: registration data, DNS records, TLS certificate and website metadata with detected technologies.

Built for lead enrichment, SEO audits, security reviews and domain portfolio monitoring — no proxies, no logins, no per-domain manual lookups.

What you get

For every domain, one dataset item:

Block	Data
whois	Registrar, IANA ID, registration date, last update, expiration date, domain age in days, days to expiry, status flags, nameservers, DNSSEC
dns	A, AAAA, MX, TXT, NS, CNAME, SOA records
ssl	Issuer, subject, valid from/to, days left, SAN list, serial number, TLS protocol
http	Status code, final URL, title, H1, meta description, Open Graph, canonical, robots, security headers
technologies	CMS, frameworks, analytics and hosting detected from headers and HTML (WordPress, Shopify, Next.js, React, Cloudflare, Vercel and 30+ more)
errors	Per-block error messages, so partial failures never break the run

Use cases

• Lead enrichment — append registrar, hosting and tech stack to a list of company domains.
• Domain monitoring — track expiration dates and SSL expiry to avoid outages.
• Competitor research — see which platforms and tools other companies run on.
• SEO audits — DNS, canonical URLs, Open Graph and metadata health in one pass.
• Security triage — certificate issuer, SAN list and DNSSEC status at a glance.

Input example

{
  "domains": ["apify.com", "https://example.com/pricing", "stripe.com"],
  "whois": true,
  "dns": true,
  "ssl": true,
  "http": true,
  "concurrency": 5,
  "timeoutSecs": 15
}

Output example

{
  "domain": "apify.com",
  "rootDomain": "apify.com",
  "checkedAt": "2026-11-01T03:10:00.000Z",
  "whois": {
    "registrar": "GoDaddy.com, LLC",
    "createdAt": "2015-05-14T18:23:22Z",
    "expiresAt": "2028-05-14T18:23:22Z",
    "ageDays": 3823,
    "daysToExpiry": 559,
    "status": ["clientDeleteProhibited", "clientTransferProhibited"],
    "nameservers": ["ns1.apify.com", "ns2.apify.com"],
    "dnssec": false
  },
  "dns": {
    "A": ["18.208.5.10"],
    "MX": ["10 inbound-smtp.us-east-1.amazonaws.com"],
    "TXT": ["v=spf1 include:amazonses.com ~all"],
    "NS": ["ns1.apify.com", "ns2.apify.com"]
  },
  "ssl": {
    "issuer": "Let's Encrypt",
    "validTo": "2027-01-20T12:00:00.000Z",
    "daysLeft": 80,
    "altNames": ["DNS:apify.com", "DNS:www.apify.com"],
    "protocol": "TLSv1.3"
  },
  "http": {
    "statusCode": 200,
    "title": "Apify: Full-stack platform for web scraping",
    "description": "Build and run web scrapers in the cloud.",
    "ogImage": "https://apify.com/img/og-image.png"
  },
  "technologies": ["Cloudflare", "Google Tag Manager", "Next.js", "React"],
  "errors": []
}

Notes

• WHOIS data comes from RDAP (the modern structured replacement of port-43 WHOIS). Some ccTLD registries do not publish RDAP; those domains return a whois.error but the other blocks still work.
• DNS is resolved through Google Public DNS over HTTPS, so results are not affected by the runner's local resolver.
• The actor never stores or logs page contents — only extracted metadata.
• Works well with 1–1000 domains per run. For larger lists, split into batches or run on a schedule.