Find out what any website is built with — and how to reach the people behind it.
Give it a list of websites and get back each one's **complete technology stack** (CMS, ecommerce, frameworks, analytics, CDN, server, JavaScript libraries, payment and marketing tools) **with categories and versions** — plus the **technographic and contact signals** most detectors skip: **email provider, SSL issuer, hosting, emails and social profiles**. A **BuiltWith & Wappalyzer alternative** that turns technology detection into **ready-to-use sales leads** — no code required. *** ### ⚡ At a glance | | | |---|---| | 🧩 **Full tech stack** | CMS, ecommerce, frameworks, analytics, CDN, server, JS libs… | | 🏷️ **Categories & versions** | Every technology tagged and versioned where detectable | | 📧 **Email provider** | Google Workspace / Microsoft 365 / Zoho… via DNS MX | | 🔒 **SSL & hosting** | Certificate issuer, CDN, web server, IP address | | 📇 **Contact leads** | Emails, phones and social profiles from the page | | 📦 **Bulk** | Analyse one site or thousands from a file/list | | ⚡ **Fast & serverless** | Pure-HTTP — no browser, quick and cheap | | 💾 **Export** | Excel, CSV, JSON, HTML or API | *** ### 📌 Why this Actor? Most tech detectors stop at a list of technologies. This one is built for **technographic lead generation** — it adds the signals sales, marketing and research teams actually act on: - 🧩 **Complete stack** — hundreds of detectable technologies across CMS, ecommerce, frameworks, analytics, tag managers, CDNs, web servers, programming languages, payment processors and marketing tools. - 📧 **Email provider** — is the company on **Google Workspace** or **Microsoft 365**? Detected from the domain's DNS MX records — a powerful qualification signal. - 🔒 **Infrastructure** — SSL certificate issuer & expiry, CDN, web server and IP address. - 📇 **Contact data** — emails, phone numbers and social-media profiles pulled straight from the site. - 📦 **Built for bulk** — feed a list of prospect domains and get an enriched technographic dataset back. The result: not just *what* a site runs, but *who to contact* and *how they're set up*. *** ### ✨ What you get (data fields) > **Coverage key:** 🟢 almost every site · 🟡 when published/available · ⚪ situational #### 🧩 Technology | Field | Description | Coverage | |-------|-------------|:--------:| | `technologyNames` | Flat list of all detected technologies | 🟢 | | `technologiesByCategory` | Technologies grouped by category | 🟢 | | `technologies` | Detailed detections (category, version, confidence) | 🟢 | | `cms` | Detected CMS (WordPress, Drupal…) | 🟡 | | `ecommercePlatform` | Detected ecommerce platform (Shopify, Magento…) | 🟡 | #### 🏗️ Infrastructure | Field | Description | Coverage | |-------|-------------|:--------:| | `server` | Web server (Nginx, Apache, cloudflare…) | 🟡 | | `cdn` | Content delivery network | 🟡 | | `poweredBy` | `X-Powered-By` header | ⚪ | | `ipAddress` | Resolved IPv4 address | 🟢 | | `sslIssuer` / `sslValidTo` | SSL certificate issuer & expiry | 🟢 | #### 📧 Technographic & contact (lead data) | Field | Description | Coverage | |-------|-------------|:--------:| | `emailProvider` | Email provider via DNS MX (Google Workspace / Microsoft 365 / …) | 🟢 | | `mailServers` | Raw MX hostnames | 🟢 | | `emails` | Emails found on the page | 🟡 | | `socialLinks` | Social-media profiles | 🟡 | | `phones` | Phone numbers found on the page | ⚪ | #### 📄 Page & meta | Field | Description | Coverage | |-------|-------------|:--------:| | `url` / `finalUrl` | Requested and post-redirect URL | 🟢 | | `statusCode` | HTTP status | 🟢 | | `title` / `description` | Page title & meta description | 🟢 | | `scrapedAt` | Collection timestamp | 🟢 | *** ### 🚀 Quick start 1. Click **Try for free / Start**. 2. Add your **Websites** — one domain or URL per line: ``` gymshark.com stripe.com https://www.allbirds.com ``` 3. *(Optional)* Toggle **email provider**, **SSL** and **contact** enrichment. 4. Click **Save & Start**, then export from the **Dataset** tab. > 💡 **Tip:** Have a big prospect list? Use **Websites from file / URL list** to load thousands of domains from a CSV, Google Sheet or URL. *** ### 🎯 Use cases | Use case | What it delivers | |----------|------------------| | 🧲 **Technographic lead generation** | Build lists of companies using a specific stack (e.g. Shopify + Klaviyo) — with email provider and contacts to reach them. | | 🕵️ **Competitive intelligence** | See exactly what competitors run — CMS, analytics, CDN, payment and marketing tools. | | 💼 **Sales qualification** | Qualify prospects by platform and email provider before you reach out. | | 📊 **Market research** | Measure technology adoption across a list of domains or an industry. | | 🧰 **Agency & audit** | Audit a client's or prospect's tech and infrastructure in seconds. | | 🔌 **App & integration targeting** | Find sites already using the platform your product plugs into. | *** ### ⚙️ Input reference | Input | Type | Default | Description | |-------|------|---------|-------------| | **Websites** | list | *sample* | One domain or URL per line. | | **Websites from file / URL list** | list | — | Bulk-load domains from a file, URL or Google Sheet. | | **Detect email provider (DNS MX)** | boolean | `true` | Identify Google Workspace / Microsoft 365 / etc. | | **Check SSL certificate issuer** | boolean | `true` | Report SSL issuer and expiry. | | **Extract contact & social data** | boolean | `true` | Pull emails, phones and social profiles. | | **Page timeout (seconds)** | number | `25` | Per-website response timeout. | | **Proxy configuration** | object | Datacenter | Default works well. | | **Max concurrent requests** | number | `8` | Websites analysed in parallel (5–15 recommended). | #### 📥 Example input ```json { "websites": ["gymshark.com", "allbirds.com", "stripe.com"], "detectEmailProvider": true, "checkSsl": true, "extractContacts": true, "maxConcurrency": 10 } ``` *** ### 📤 Example output ```json { "url": "https://allbirds.com/", "finalUrl": "https://www.allbirds.com/", "statusCode": 200, "title": "Allbirds: Comfortable, Sustainable Shoes & Apparel", "technologyNames": ["Shopify", "Google Tag Manager", "Cloudflare", "HSTS", "HTTP/3"], "technologiesByCategory": { "Ecommerce": ["Shopify"], "Tag managers": ["Google Tag Manager"], "CDN": ["Cloudflare"] }, "cms": null, "ecommercePlatform": "Shopify", "server": "cloudflare", "cdn": "Cloudflare", "ipAddress": "23.227.38.74", "sslIssuer": "Google Trust Services", "sslValidTo": "2026-09-01", "emailProvider": "Microsoft 365", "mailServers": ["allbirds-com.mail.protection.outlook.com"], "emails": ["help@allbirds.com"], "socialLinks": ["https://www.instagram.com/allbirds/"], "scrapedAt": "2026-07-24T13:40:00.000Z" } ``` *** ### 💡 Tips & best practices - ✅ **Feed clean domains** — `example.com` or a full URL both work; `https://` is added automatically. - ✅ **Qualify by email provider** — `Microsoft 365` vs `Google Workspace` is a strong segmentation signal. - ✅ **Group by category** — use `technologiesByCategory` to filter for a specific stack (e.g. all sites with Klaviyo). - ✅ **Turn off enrichment** you don't need (SSL / contacts) to run even faster. - ✅ **Scale up** — raise concurrency and load domains from a file for large lists. - ✅ **Combine signals** — tech + email provider + contacts = a complete technographic lead. *** ### ❓ FAQ **What technologies can it detect?** Hundreds — across CMS, ecommerce, JavaScript frameworks, analytics, tag managers, CDNs, web servers, programming languages, payment processors and marketing tools, with categories and versions where available. **How is this different from a plain tech detector?** It adds the **technographic lead layer**: email provider (DNS MX), SSL issuer, hosting/IP, and on-page emails, phones and socials — so each result is a usable lead, not just a tech list. **Do I need to code?** No. Paste your domains, click Start, and export. **Can I analyse thousands of websites?** Yes — load them from a file or URL list and raise concurrency. **Why do some sites show few technologies?** Highly custom or heavily protected sites expose fewer fingerprints. Infrastructure and DNS signals (email provider, SSL, IP) are still returned. **In what format is the data?** Structured JSON by default, exportable to CSV, Excel, HTML or via API. *** ### 📊 Output & integrations Results are stored in a standard Apify dataset. You can: - 👀 Preview them in a clean **table view** in the Console. - 💾 Export to **JSON, CSV, Excel, HTML, or RSS**. - 🔌 Pull them via the **Apify API**. - 🔗 Push them to **Google Sheets, Make, Zapier, Airbyte** and more. *** ### ⚖️ Legal & responsible use This Actor inspects **publicly available website and DNS information** for legitimate purposes such as market research, competitive analysis and B2B lead generation. - Use the data in compliance with **GDPR** and any other applicable laws, including rules on **B2B marketing and electronic communications**. - Any personal data (e.g. emails) requires a lawful basis for processing and outreach — ensure you have one and honour opt-out requests. - Respect each website's terms of service and use the data responsibly. - You are responsible for how you use the collected data. *** ### 🛟 Support Found a bug, need an extra signal, or want a tweak? **Open an issue** on the Actor's Issues tab — feedback is welcome and helps improve the Actor.Happy prospecting! 🔍
# Actor input Schema ## `websites` (type: `array`): One website per line — a domain or full URL (e.g. 'shopify.com', 'https://www.gymshark.com'). Each is analysed for its technology stack and lead signals. ## `startUrls` (type: `array`): Optional. Load a large list of websites from a file, URL, Google Sheet or Apify Request Queue instead of typing them. ## `detectEmailProvider` (type: `boolean`): Look up the domain's mail servers to identify the email provider (Google Workspace, Microsoft 365, Zoho, etc.) — a strong technographic signal. ## `checkSsl` (type: `boolean`): Read the SSL certificate to report its issuer (Let's Encrypt, DigiCert, Cloudflare, etc.) and expiry date. ## `extractContacts` (type: `boolean`): Pull emails, phone numbers and social-media profiles from the page — turning tech detection into ready-to-use technographic leads. ## `pageTimeoutSecs` (type: `integer`): How long to wait for each website to respond before giving up. ## `proxyConfiguration` (type: `object`): Proxy settings for reliable, uninterrupted analysis across many websites. Datacenter proxies (the default) work well. ## `maxConcurrency` (type: `integer`): How many websites to analyse in parallel. Higher finishes large lists faster. Recommended: 5–15. ## Actor input object example ```json { "websites": [ "shopify.com", "wordpress.org" ], "startUrls": [], "detectEmailProvider": true, "checkSsl": true, "extractContacts": true, "pageTimeoutSecs": 25, "proxyConfiguration": { "useApifyProxy": true }, "maxConcurrency": 8 } ``` # Actor output Schema ## `datasetItems` (type: `string`): Download every analysed website (JSON, CSV, Excel). ## `runUrl` (type: `string`): Open this run in the Apify Console. ## `url` (type: `string`): Website analysed ## `title` (type: `string`): Page title ## `technologyNames` (type: `string`): All detected technologies ## `technologiesByCategory` (type: `string`): Technologies grouped by category ## `cms` (type: `string`): Content management system ## `ecommercePlatform` (type: `string`): Ecommerce platform ## `server` (type: `string`): Web server ## `cdn` (type: `string`): Content delivery network ## `emailProvider` (type: `string`): Email provider via DNS MX ## `sslIssuer` (type: `string`): SSL certificate issuer ## `ipAddress` (type: `string`): Resolved IPv4 address ## `emails` (type: `string`): Emails found on the page ## `socialLinks` (type: `string`): Social-media profiles ## `phones` (type: `string`): Phone numbers found on the page ## `technologies` (type: `string`): Full detections with category, version and confidence ## `statusCode` (type: `string`): HTTP status code ## `finalUrl` (type: `string`): URL after redirects ## `scrapedAt` (type: `string`): ISO 8601 timestamp # 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 '