BuiltWith Official Technology Scraper

BuiltWith Official Technology Scraper — tech stack, tracking IDs, security

BuiltWith Official Technology Scraper finds out what any website is built with. Give it domains and it returns the technology stack (CMS, frameworks, analytics, ads, CDN, hosting, payments), the analytics and pixel IDs found on the pages, a security-header grade, public contacts and DNS or SSL details. Every response is structured JSON — ready to pass directly to an LLM, index into a vector store, or feed a lead-enrichment pipeline. No account, login or cookies are needed for any website. Run it on one domain or thousands, and get a clean row per website to filter, export or enrich.

Why use this website technology scraper?

• One result per domain with the same shape every time.
• Separate tables for technologies, contacts, infrastructure, security and tracking IDs.
• Starts without a proxy and switches to a stronger one by itself if a website refuses the request.
• Live output: rows appear in the table while the run is still going.

What data can you extract with a website technology checker?

Field	What it holds
domain, url, status_code	The site as analyzed and the page it finally loaded
title, description, language	Home page title, meta description and language
techs	Each technology: name, tag, categories, groups, version, confidence, detected_via, description, link
by_category, stack, signals	Technologies by category, a CMS / ecommerce / CDN / analytics summary, and yes/no signals such as is_ecommerce
tracking_ids	Google Analytics, Tag Manager, Ads, Facebook, TikTok, LinkedIn, Hotjar, Clarity, HubSpot, Pinterest IDs when present
security	https, score, grade, headers present and missing
contacts	Emails, phone numbers and social profile links
infrastructure	IP addresses, mail and name servers, SPF / DMARC, SSL certificate details
server, response_seconds, pages_scanned, scraped_at, error	Run details; error is null when everything worked

How to use the technology stack scraper

1. Log in at the Apify Console and open the Actor.
2. Add one or more domains under Websites to analyze.
3. Choose Home page only or Deep, and switch contacts or infrastructure on or off.
4. Click Start and watch the log: one line per finished website.
5. Open the Output tab for the overview and the per-section tables, then export to JSON, CSV or Excel.

Input

{
  "urls": ["shopify.com", "stripe.com", "allbirds.com"],
  "scanDepth": "home",
  "categories": [],
  "includeContacts": true,
  "includeInfrastructure": true,
  "maxDomains": 100,
  "proxyConfiguration": { "useApifyProxy": false }
}

Field	Meaning
urls	Domains or full web addresses; duplicates are removed.
maxDomains	Stop after this many websites. Free plan: up to 10 results per run.
scanDepth	home checks the home page; deep also checks up to 5 key pages.
categories	Keep only technologies from these categories or groups; empty keeps all.
includeContacts, includeInfrastructure	Turn the contact and infrastructure sections on or off.
proxyConfiguration	Optional; default is no proxy.

Output

Example for one website (shortened):

{
  "domain": "shopify.com",
  "url": "https://www.shopify.com/bd",
  "status_code": 200,
  "tech_count": 6,
  "techs": [
    { "name": "Cloudflare", "tag": "cdn", "categories": ["CDN"], "groups": ["Servers"],
      "version": null, "confidence": 100, "detected_via": ["header"],
      "link": "https://www.cloudflare.com" }
  ],
  "security": { "https": true, "score": 40, "grade": "D" },
  "error": null
}

Results are saved to the default table (one row per website). The same data is also split into the technologies, contacts, infrastructure, security and tracking_ids tables, and a short run summary is stored under RUN_SUMMARY.

Use via API or MCP

Start the Actor from the Apify API, the CLI or any Apify client, then read the dataset items as JSON, CSV or Excel. AI agents can find and run it through the Apify MCP server: claude mcp add --transport http apify "https://mcp.apify.com" — the agent finds this Actor with the server's search, details and call tools.

Best use cases

• Lead lists filtered by platform, for example every Shopify store in a domain list.
• Competitor stack research across analytics, ads and payment tools.
• Sales prospecting by CMS, CDN or marketing tool.
• Security header audits across many domains.

FAQ

Does it need a login? No. It reads what any visitor of a public website can see.

Why is a technology missing? Technologies that only show up after a full browser renders the page are not detected, so a few client-side-only tools can be absent.

What does a row with error set mean? The website was unreachable, refused the request, or did not return an HTML page. Those rows are not charged.

Can a website block it? Some do. The Actor then switches to a stronger proxy automatically; if the website still refuses, the row says so.

Are contacts guaranteed? No. Only emails, phones and social links that are visible in the pages are returned.

What if websites change their layout? Detection data is refreshed on every run, so new technologies are picked up without a new Actor version.

Support and feedback

Found a website that is analyzed wrongly, or need another field? Open an issue from the Issues tab on the Actor page and include the domain.

Legal

Data is collected only from public pages and public DNS records. You are responsible for using it in line with privacy and anti-spam laws and each website's terms.