Tech Stack & Email Provider Detector (Wappalyzer + DNS)

Find out what any website is built with and which SaaS tools the company behind it uses, in bulk.

For every domain you get:

• 7,600+ website technologies from the homepage: CMS, ecommerce platform, analytics, tag managers, JavaScript frameworks, CDN, hosting, payment tools, marketing pixels and more, with versions where detectable. It uses the open Wappalyzer fingerprint database.
• Email provider from MX records: Google Workspace, Microsoft 365, Zoho, Proofpoint, Mimecast and others.
• Email-sending tools from SPF: HubSpot, Salesforce, Marketo, SendGrid, Mailchimp, Zendesk, Postmark, Amazon SES and others.
• SaaS tools verified in DNS: Atlassian, DocuSign, Stripe, Slack, OpenAI, Zoom, Miro, Jamf, Loom, Canva and 100+ more. Companies publish these ownership tokens when they roll a tool out company-wide.
• DMARC policy and the TLS certificate issuer.

DNS signals reveal the internal stack: tools that never appear in a site's HTML but show what the company pays for. HTML-only detectors such as Wappalyzer and BuiltWith-style scrapers can't see them.

Use cases

• Lead qualification. Keep only companies on Microsoft 365, HubSpot users, Shopify stores, WordPress sites and so on.
• Sales intelligence. Know a prospect's CRM, helpdesk, email and security stack before the first call.
• Market research. Measure technology adoption across thousands of domains.
• Competitor tracking. Find who uses a competitor's product by its DNS token or script.
• Enrichment for AI agents. Clean, predictable JSON per domain.

Input

{
  "domains": ["apify.com", "stripe.com", "https://wordpress.org"],
  "includeDns": true,
  "maxConcurrency": 30
}

• Bare domains or full URLs are accepted, and duplicates are removed.
• Up to 100,000 domains per run.
• No proxy is needed for most sites.

Output (one item per domain)

{
  "domain": "apify.com",
  "statusCode": 200,
  "title": "Apify: Marketplace of ready-to-run tools for AI",
  "technologyNames": ["Algolia", "Amazon CloudFront", "Amazon S3", "Amazon Web Services", "HSTS", "HTTP/3", "Leadfeeder"],
  "technologies": [{ "name": "Algolia", "version": "", "categories": ["Search engines"], "website": "https://www.algolia.com" }],
  "categories": { "Analytics": ["Leadfeeder"], "CDN": ["Amazon CloudFront", "Amazon S3"], "Search engines": ["Algolia"] },
  "tls": { "issuer": "Amazon", "subject": "*.apify.com", "notAfter": "2027-01-16T23:59:59Z" },
  "dns": {
    "emailProvider": "Google Workspace",
    "emailSendingServices": ["Amazon SES", "Google Workspace", "HubSpot", "Mailgun"],
    "saasVerifications": ["Google Search Console", "Mixpanel", "OpenAI", "Tito", "Zapier"],
    "hasDmarc": true,
    "dmarcPolicy": "reject",
    "mx": ["aspmx.l.google.com", "..."],
    "spfIncludes": ["_spf.google.com", "mailgun.org", "amazonses.com", "..."],
    "otherVerificationTokens": []
  },
  "error": null
}

You can export results as JSON, CSV, Excel, or fetch them through the API, webhooks, Make, Zapier or n8n.

Pricing

$4 per 1,000 analyzed domains ($0.004 per domain), pay per result.

• No charge for failures. Domains that don't resolve and have no reachable website are returned with an error and are not charged.
• DNS signals are included at no extra cost.
• The cost limit is respected. Set Maximum cost per run and the Actor stops when it is reached.

FAQ

How accurate is technology detection? It uses the community-maintained Wappalyzer fingerprints on the homepage HTML, headers and cookies, without a browser. That makes it fast and cheap. A few technologies that are only injected by JavaScript after page load can be missed.

Some sites return 403. Some websites block automated traffic. You still get header-based technologies and all DNS signals. You can enable Apify Proxy in the input to retry blocked sites through other IPs.

Is this legal? The Actor reads only public information: a website's public homepage and public DNS records. No logins and no personal data.

How fast is it? Roughly 300 domains in under a minute at the default settings. Unreachable sites are capped by the request timeout.