# Tech Stack, Email Provider & SaaS Detector by Domain (`lakadev/website-tech-stack-detector`) Actor Use when you have company domains and need their email provider, SaaS tools and tech stack (CMS, analytics, chat, payments). Reads DNS plus raw home page HTML and public scripts, no browser; robots.txt respected; evidence per finding. $0.002/domain, $0.005 with page. - **URL**: https://apify.com/lakadev/website-tech-stack-detector.md - **Developed by:** [Djam](https://apify.com/lakadev) (community) - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $2.00 / 1,000 domain analyzed (dns)s 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 ## Tech Stack, Email Provider & SaaS Detector by Domain Give it company domains. For each one it returns, **with the evidence for every finding**: - the **email provider** (Google Workspace, Microsoft 365, Zoho Mail, OVHcloud Mail...), read from MX records; - the **SaaS tools the domain declares in DNS**: services allowed to send its e-mail (SPF), verification tokens (Atlassian, HubSpot, DocuSign, OpenAI...), CNAME records of a few well-known subdomains; - the **website technologies** found in the raw HTML of the home page, in up to 3 scripts served by the site itself and in its public Google Tag Manager container: CMS (WordPress, Shopify, Webflow...), analytics and tag managers, chat widgets (Zendesk, Intercom...), payment tools (Stripe, PayPal...), consent tools, frameworks, web server. Each one says where it was found (`source`); - the **DNS provider**, the **hosting platform** and the **CDN** when DNS reveals them; - the **SPF** and **DMARC** policies. One action, one row per domain, structured JSON. DNS first: the e-mail provider, SPF/DMARC and SaaS proofs that page scanners do not give. It reads public DNS records and the public home page (after checking `robots.txt`), with the User-Agent `LakadevStackBot/1.0 (+https://apify.com/lakadev/website-tech-stack-detector)`. No browser, no JavaScript executed, no API key, no login, no proxy. ### When to use it - **Qualify B2B prospects.** From a list of domains, find who runs WordPress or Shopify, loads HubSpot or Intercom, or sends mail through Salesforce or SendGrid, then keep the ones that fit your offer. Stripe is rarely visible on a home page (it loads at checkout), so a Stripe finding mostly comes from DNS and means an account, not live payments. - **Find the email provider of a domain.** Google Workspace, Microsoft 365, Zoho, OVHcloud, Proton, a security gateway such as Mimecast or Proofpoint: the answer comes from MX records, with the MX host as proof. - **Spot the customers of a SaaS competitor.** Domains that declare Zendesk, HubSpot, Atlassian or Salesforce in their DNS, or whose home page names their chat widget, are likely users or past users. A DNS verification token proves the domain has an account with the service, not that it uses it today. - **Audit e-mail posture** at scale: SPF final mechanism (`~all`, `-all`), DMARC policy (`none`, `quarantine`, `reject`). - **Feed an AI agent** that needs a structured answer about a company's stack instead of reading raw HTML. It is not a replacement for a full technology database: it knows 54 website technologies and 34 DNS services (lists below). **How to read the results:** an absence proves nothing. "No chat widget found" means none appears in the HTML, the scripts read or the GTM container, not that the site has none (tools loaded by the site's own JavaScript, or after consent, are invisible). If `page.status` is not `fetched`, an empty `technologies` means "not read", not "none". ### Price Pay per event, no platform usage billed on top: | Event | Price | When | |---|---|---| | Domain analyzed (DNS) | **$0.002** | the domain exists and its DNS was analyzed (status `ok`) | | Home page analyzed | **$0.003** more | the home page was fetched and analyzed (`page.status = "fetched"`); covers its scripts and GTM container | | Actor start | $0.00005 | once per run (Apify's standard start event) | Besides the tiny start fee, a full row costs $0.005; a DNS-only row (`fetchHomepage: false`) costs $0.002. **Nothing is charged** for invalid items, unknown domains (`not_found`), lookup errors, or for the page when it is `robots_disallowed`, `blocked`, `http_error` or `unreachable`. If your maximum cost per run is reached, the run stops cleanly at the first row it can no longer pay for. ### Input | Field | Type | Default | Description | |---|---|---|---| | `domains` | array of strings (1 to 1,000) | required | Domains (`apify.com`), URLs (`https://www.shopify.com/fr`) or e-mail addresses (`name@wordpress.org`). The domain is extracted, `www.` is removed, duplicates are merged. | | `includeSubdomainWww` | boolean | `true` | Also look up `www.` in DNS to detect hosting and CDN. | | `fetchHomepage` | boolean | `true` | Read the home page and its scripts (robots.txt first) to detect website technologies. `false`: no HTTP request to the site, DNS only. | ```json { "domains": ["apify.com", "https://www.shopify.com/fr", "someone@wordpress.org", "zendesk.com"], "includeSubdomainWww": true, "fetchHomepage": true } ``` Domains are normalized with IDNA 2008 (UTS 46): `BΓΌcher.de` becomes `xn--bcher-kva.de`. Subdomains are analyzed as given. ### Output One row per domain, in input order (after merging duplicates). Real run of 2026-10-01 on `webflow.com`, shortened (`saas` had 14 items and keeps 5). Three technologies come from the Google Tag Manager container (`source: "gtm"`), including the chat tool Qualified. Real values change over time. ```json { "input": "webflow.com", "domain": "webflow.com", "status": "ok", "emailProvider": { "name": "Google Workspace", "evidence": "MX aspmx.l.google.com" }, "mx": [ "aspmx.l.google.com", "alt1.aspmx.l.google.com", "alt2.aspmx.l.google.com", "aspmx2.googlemail.com", "aspmx3.googlemail.com" ], "spf": { "record": "v=spf1 include:_spf.google.com include:spf.mailjet.com include:mail.zendesk.com include:_spf.salesforce.com include:mailgun.org ?all", "includes": [ "_spf.google.com", "spf.mailjet.com", "mail.zendesk.com", "_spf.salesforce.com", "mailgun.org" ], "all": "?all" }, "dmarc": { "policy": "reject", "record": "v=DMARC1; p=reject; sp=none; rua=mailto:***@inbox.ondmarc.com,mailto:***@webflow.com,mailto:***@dmarc.mailgun.org,mailto:***@inbox.ondmarc.com; ruf=mailto:***@inbox.ondmarc.com,mailto:***@dmarc.mailgun.org,mailto:***@inbox.ondmarc.com; aspf=r; pct=100; fo=1; ri=3600" }, "saas": [ { "name": "Google Workspace", "category": "email", "evidence": "MX aspmx.l.google.com" }, { "name": "Salesforce", "category": "crm", "evidence": "SPF include:_spf.salesforce.com" }, { "name": "SendGrid", "category": "email-sending", "evidence": "CNAME s1._domainkey.webflow.com s1.domainkey.u2859722.wl223.sendgrid.net" }, { "name": "Stripe", "category": "payments", "evidence": "TXT stripe-verification=081188df8f2b18461958…" }, { "name": "Zendesk", "category": "support", "evidence": "SPF include:mail.zendesk.com" } ], "dnsProvider": { "name": "Amazon Route 53", "evidence": "NS ns-1078.awsdns-06.org" }, "hosting": null, "cdn": null, "nameservers": [ "ns-1078.awsdns-06.org", "ns-1722.awsdns-23.co.uk", "ns-344.awsdns-43.com", "ns-958.awsdns-55.net" ], "page": { "status": "fetched", "url": "https://webflow.com/", "httpStatus": 200 }, "technologies": [ { "name": "Cloudflare", "category": "cdn", "version": null, "source": "page", "evidence": "HEADER cf-ray: a43baf32dddb1fd3-IAD" }, { "name": "Google Tag Manager", "category": "tag-manager", "version": null, "source": "page", "evidence": "HTML https://www.googletagmanager.com/ns.html?id=GTM-55XXQM3F\" he" }, { "name": "jQuery", "category": "js-library", "version": "3.5.1", "source": "page", "evidence": "SCRIPT https://d3e54v103j8qbb.cloudfront.net/js/jquery-3.5.1.min.dc5e7f18c8.js?s…" }, { "name": "LinkedIn Insight Tag", "category": "advertising", "version": null, "source": "gtm", "evidence": "GTM GTM-55XXQM3F snap.licdn.com" }, { "name": "Meta Pixel", "category": "advertising", "version": null, "source": "gtm", "evidence": "GTM GTM-55XXQM3F connect.facebook.net/" }, { "name": "Qualified", "category": "chat", "version": null, "source": "gtm", "evidence": "GTM GTM-55XXQM3F js.qualified.com" }, { "name": "Webflow", "category": "cms", "version": null, "source": "page", "evidence": "META generator Webflow" } ], "failedLookups": [], "checkedAt": "2026-10-01T13:06:22Z", "error": null } ``` How to read it: `emailProvider` is Google Workspace because the MX hosts are Google's. The `saas` list shows Stripe and Zendesk from DNS (tokens, SPF): accounts, not proof of live use. Qualified is listed with `source: "gtm"`: it is configured in the site's tag manager container, which does not guarantee it is active on the home page. #### Fields - `input`: the item as given. E-mail addresses are masked (`***@x.com`). - `domain`: normalized domain; `null` when the status is `invalid`. - `status`: `ok`, `not_found` (the domain does not exist or has no records), `invalid` (not a domain), `error` (lookups failed and nothing was found). Only `ok` is billed. - `emailProvider`: `{name, evidence}`. `null` with an empty `mx` means the domain itself receives no mail (the company may use another domain: `notion.so` has no MX, its mail is on `notion.com`). `Unknown` means the MX host is not in our list: read `mx` and `saas`, since a mail gateway such as Proofpoint or Mimecast can sit in front of Google or Microsoft. `None (null MX)` means the domain declares it does not receive e-mail (RFC 7505). - `mx`: MX hosts sorted by priority, then name. - `spf`: `record`, `includes` (the `include:` targets of that record, no recursion), `all` (final `all` mechanism); `null` without SPF. - `dmarc`: `policy` (value of `p=`) and the `record`; `null` without DMARC. - `saas`: services the domain declares in DNS: `name`, `category` and `evidence` (`" "`). - `dnsProvider`, `hosting`, `cdn`: `{name, evidence}` or `null`. - `nameservers`: NS targets, sorted. - `failedLookups`: lookups that failed (`"MX x.com"`). A row with status `ok` can be partial: `mx = []` with no `MX x.com` here means "no MX"; with it, "MX unknown". - `page`: `status` is `fetched` (2xx page received and analyzed), `robots_disallowed` (robots.txt forbids the page, or answers 5xx), `blocked` (401, 403, 429, or an anti-bot challenge page: nothing is bypassed), `http_error` (other HTTP failure, too many redirects), `unreachable` (no usable answer, timeout, non-public address) or `not_fetched`. `url` is the last page URL requested, `httpStatus` its response code. - `technologies`: empty unless `page.status` is `fetched`. Each item: `name`, `category`, `version` (only for generators, jQuery file names and `server` headers, else `null`), `source` (`page`: the page HTML and headers; `script`: one of the site's own scripts; `gtm`: a Google Tag Manager container) and `evidence` (`page`: `HEADER name: value`, `COOKIE name`, `META generator ...`, `SCRIPT url`, `LINK url` or `HTML excerpt`; `script`: `SCRIPT