Website Technology Detector: CMS, Frameworks, Analytics, CDN avatar

Website Technology Detector: CMS, Frameworks, Analytics, CDN

Pricing

from $16.00 / 1,000 page scans

Go to Apify Store
Website Technology Detector: CMS, Frameworks, Analytics, CDN

Website Technology Detector: CMS, Frameworks, Analytics, CDN

Detects the CMS, JavaScript frameworks, analytics, CDN and libraries a web page URL uses, from its HTML, headers and cookies. Returns each technology with a confidence score and the evidence found, plus the server header. For sales teams, developers, market researchers and agencies.

Pricing

from $16.00 / 1,000 page scans

Rating

0.0

(0)

Developer

Broke to Built

Broke to Built

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

1

Monthly active users

14 days ago

Last modified

Features

Limited permissions

Share

Website Technology Detector

Send a URL, get the technologies the site is built with (CMS, JS frameworks, analytics, tag managers, CDN, server), each with a confidence score and the evidence found.

You give itYou get backYou pay (Free plan)
One URL or a list of up to 50Server and powered-by headers, and per technology: name, category, confidence, evidence$0.02 per page

Pay per result only: no subscription, no start fee. Paid Apify plans get Store discounts on the price above.

Example: try it in one click

The input form is already filled in with this example. Press Start and you get the output below.

{
"url": "https://www.cloudflare.com",
"urls": []
}

Real output from that exact input (run on 2026-09-24; long arrays shortened to a few entries and long text cut for display):

[
{
"url": "https://www.cloudflare.com",
"statusCode": 200,
"server": "cloudflare",
"poweredBy": null,
"technologies": [
{
"name": "Tailwind CSS",
"category": "UI Framework",
"confidence": 0.7,
"evidence": "html: class=\"relative z-10 mx-auto flex h-[54px] w-full max-w-full items-center justif"
},
{
"name": "Google Tag Manager",
"category": "Tag Manager",
"confidence": 0.9,
"evidence": "html: googletagmanager.com/gtm.js"
}
]
}
]

Find out what any website is built with — CMS, JS frameworks, analytics, CDNs, and servers — from a single URL.

Live on the Apify Store — run it instantly or call it as an agent tool via Apify MCP.

What you get

  • CMS & site builders — WordPress, Shopify, Wix, Squarespace, Drupal, Joomla, Webflow, Ghost, HubSpot, and more.
  • JS frameworks & libraries — React, Vue, Angular, Next.js, Nuxt, Svelte, Gatsby, jQuery, Alpine, Lodash.
  • UI frameworks — Bootstrap, Tailwind CSS, Font Awesome.
  • Analytics & tag managers — Google Analytics, Google Tag Manager, Facebook Pixel, Hotjar, Segment, Mixpanel, Plausible, Matomo.
  • Infra — Cloudflare, Fastly, CloudFront, Akamai, Vercel, Netlify, GitHub Pages, Nginx, Apache, IIS, LiteSpeed, Express, PHP, ASP.NET, Rails.

Every detection comes with a confidence score and the exact evidence (HTML snippet, header, or cookie) that triggered it — no black boxes.

Detection runs purely on HTML + response-header signatures (meta generator tags, script sources, global vars, class prefixes, cookies, Server / X-Powered-By / X-Generator headers). Single URL or bulk, your choice.

Input

{
"url": "https://www.cloudflare.com",
"maxUrls": 50
}

Or scan many at once:

{
"urls": ["https://wordpress.org", "https://vercel.com", "https://www.shopify.com"]
}

Output

One dataset item per URL:

{
"url": "https://www.cloudflare.com",
"finalUrl": "https://www.cloudflare.com/",
"statusCode": 200,
"server": "cloudflare",
"poweredBy": null,
"technologies": [
{ "name": "Cloudflare", "category": "CDN", "confidence": 0.9, "evidence": "header server: cloudflare" },
{ "name": "Next.js", "category": "JavaScript Framework", "confidence": 0.95, "evidence": "html: /_next/static/" },
{ "name": "React", "category": "JavaScript Framework", "confidence": 0.8, "evidence": "html: data-reactroot" }
]
}

Pricing

$0.02 per page scanned — billed as the page-scanned event. Bulk runs are capped by maxUrls, which is also your budget cap. For long domain lists with pasted-text input and tiered volume pricing, see our Bulk Tech Stack Detector ($0.01 per domain on the Free plan, down to $0.0067 on paid plans).

Limits

  • Default run settings: 4096 MB memory, 3600 s timeout. Change them per run under Options if a large input needs more.
  • Time: the prefilled example finished in 1 s on 2026-10-31; run time grows with the number of inputs.

FAQ

How do I find out what a website is built with? Pass the URL — detected CMS, JS frameworks, UI libraries, analytics, and infrastructure come back as one JSON record, each with a confidence score and the exact evidence (HTML snippet, header, or cookie) that triggered it.

Can it detect WordPress themes or plugins? It detects WordPress itself (and 40+ other technologies); theme/plugin enumeration is a different, heavier job. What you get here is the stack layer: CMS, framework, analytics, CDN, server.

Why do results include the evidence string? No black boxes — "header server: cloudflare" or "html: /_next/static/" lets you audit any detection in seconds instead of taking a boolean on faith.

Does it run JavaScript? No — detection runs on HTML and response-header signatures, which is what keeps it $0.02 and fast. Purely runtime-injected tech can be missed; declared and asset-based tech (the vast majority) is caught.

Can I scan a list of sites? Yes — pass an array in urls (capped by maxUrls), one record per site.

For AI agents

This Actor is built to be called by software, not just by people.

  • Mount it directly as an MCP tool — no Store search, no ranking, just this one tool: https://mcp.apify.com/?actors=eliai/webpage-tech-detector
  • Or call it over HTTP and get the results in the same request: POST https://api.apify.com/v2/acts/eliai~webpage-tech-detector/run-sync-get-dataset-items
  • Costs are predictable before you call. Pricing is pay-per-event (see Pricing above), so an agent can budget a run in advance instead of discovering the bill afterwards.
  • Send only the field you mean. If you pass the bulk field, it is used on its own; the single-value field is a fallback, never merged into your request. You are charged for the items you sent and nothing else.

Who uses it

  • Sales teams qualifying prospects by the CMS or analytics a website runs
  • Developers checking which JS framework and CDN a site uses before scoping work
  • Market researchers counting technology adoption across a list of sites
  • Agencies identifying a client's stack during onboarding without admin access
  • Security analysts identifying server software exposed on a target site

Changelog

  • 2026-11-01: Page text only: the "Try it" block is now headed Example and a Limits section. Code, output and price are unchanged.
  • 2026-09-24: New summary at the top of this page: what you send, what you get, the price, and a real output from the prefilled example.