Skip to content
Devtoolry

Website Technology Checker

Find out what any website is built with: CMS, ecommerce platform, JavaScript framework, analytics, CDN, hosting and web server, detected from its HTML and headers.

Something not working, or missing a feature? Send feedback

About the Website Technology Checker

The Website Technology Checker shows what a site is built with. It loads one page and matches its HTML, response headers and cookie names against about 100 fingerprints: CMS and site builders (WordPress, Shopify, Webflow, Wix), JavaScript frameworks (Next.js, Nuxt, React), analytics and tag managers, ad and chat scripts, payment providers, the CDN, the hosting platform and the web server. Each result shows the evidence it was detected from, so you can verify it.

Our server requests the URLs you enter, like a crawler: it reads the response without running the page's scripts, and the analysis runs in your browser. The URLs and results are not stored.

How to use the Website Technology Checker

  1. Enter the address of any page of the site; the home page usually reveals the most.
  2. Press Detect technology and read the list, grouped by category.
  3. Hover a product to see the evidence (a header, a script path or a meta tag).
  4. For a WordPress site, open the WordPress Theme Detector from the result to see the theme and plugins.

Works well with the Website Technology Checker

Frequently asked questions

How does technology detection work?

Every product leaves traces: WordPress loads files from /wp-content/, Next.js from /_next/static/, Cloudflare adds a cf-ray header, Shopify serves assets from cdn.shopify.com. The checker looks for those traces in the page and its headers. It is the same method browser extensions like Wappalyzer use, without installing anything.

Why is something missing or wrong?

Sites can remove version tags, rename folders, put everything behind a CDN or build the page with JavaScript after it loads, which hides many signals. Detection is a best guess; check the evidence shown for each result, and try another page of the site.

Can it see the backend database or programming language?

Only when the site reveals it, for example through an X-Powered-By header or a session cookie name such as PHPSESSID. Well-configured servers hide this on purpose.