What CMS is this website? Free CMS detector.

How it works

How the checker tells one platform from another.

Every platform leaves fingerprints in the pages it serves. WordPress loads files from /wp-content/ and /wp-includes/, Shopify stores declare their theme and shop in a small script, Wix serves images from static.wixstatic.com, Webflow marks each page with data-wf attributes, and Drupal, Joomla, Ghost and TYPO3 usually name themselves in a generator tag. The checker reads the site's public home page once, looks for patterns that only the platform's own pages produce, and reports the first platform it can confirm.

That last part matters. A page that merely links to wix.com, or loads a Shopify consent script, isn't a Wix site or a Shopify store, and a careless detector will say it is. The patterns here were tested against real sites before launch, including a site that loads another platform's scripts, so the answer is based on the site's own code rather than a mention of a brand.

The checker also reads the response headers that come back with the page. Headers are where hosting companies, CDNs and web servers identify themselves, for example Cloudflare's cf-ray, Kinsta's cache header or Vercel's request ID. Only the names of known services are shown; the raw headers and the page itself are never passed on.

What it detects

Platforms, builders, versions and hosting.

One check covers the whole stack, grouped the way a developer would describe it:

WordPress version

Is this WordPress site up to date?

For WordPress sites the checker finds the core version in three places: the generator tag in the page, the version number WordPress adds to its own stylesheets and scripts, and the site's RSS feed, which often still shows the version after a security plugin has removed it from the page. It then compares the result with the current release published by WordPress.org, so you can see at a glance whether a site is current or behind on updates.

An out-of-date WordPress core is one of the most common reasons sites get hacked, because security fixes ship in point releases. If a site you run is behind, update it from Dashboard, then Updates, after taking a backup. If the version is hidden everywhere, the checker says so rather than guessing; hiding it is a reasonable security setting.

Limits

What a CMS detector can't see.

The checker sees what any visitor's browser receives. A site behind Cloudflare or another CDN shows the CDN, not the hosting company behind it. Custom-built sites, headless storefronts and sites that bundle and rename all their files may show only a framework, or nothing recognisable at all, and admin-only plugins and server-side tools never appear on the front end. Some large sites show a bot check to every automated visit; when that happens the checker tells you instead of guessing, and it doesn't try to get around the protection.

Each check reads the home page once (plus the RSS feed for WordPress sites that hide their version) and returns only the detected names. Nothing is stored, and checks are rate-limited so the tool stays fast and fair.

Next step

Found the platform. Now what?

For WordPress and Shopify sites, the checker links straight to the detailed theme and plugin or theme and app detectors, so you can see exactly which theme a site uses. I build only on WordPress and Shopify: custom WordPress, WooCommerce and Shopify sites, Elementor layouts and plugins. If your own site runs on Wix, Squarespace or another builder and you want to move, I rebuild it on WordPress or Shopify, with a fixed quote after a free review of what you need.