See what any website is built on.
Enter a website to see its CMS, ecommerce platform, framework, analytics tools and hosting, with the evidence behind each one. No account needed.
- CMS and its version
- Ecommerce platform
- Frameworks and libraries
- Analytics and tag tools
- CDN, hosting and server
What you get
One check. The whole stack, with proof.
The detector reads the homepage the way a browser receives it and lists every technology it can see, grouped by what it does, next to the header, tag or file that gave it away.
cms detector · example.com
done
- cmsWordPress 6.6
- ecommerceWooCommerce 9.3
- frameworkjQuery
- analytics and tagsGoogle Analytics 4, Google Tag Manager
- cdn and hostingCloudflare
- serverNginx, PHP 8.2
8 technologies foundfrom headers and HTML
Why it matters
The platform shapes what you can fix.
Titles, redirects, sitemaps and page speed all work differently on WordPress, Shopify or a custom build. Knowing the stack first saves you from advice that does not apply.
Audits
Know what you are auditing
The CMS decides which SEO settings exist and where they live, so an audit starts with knowing which one runs the site.
Competitors
See what rivals build on
Check the sites that outrank you and see which platforms, frameworks and analytics tools they chose.
Planning
Scope work before you quote
A migration, a redesign or a tracking setup is sized very differently on Webflow than on Magento. Check before you estimate.
Who it's for
Built for the people who work on other people's sites.
01
SEO specialists
Learn the CMS and hosting before an audit, so your recommendations match what the platform can actually do.
02
Agencies and freelancers
Size up a prospect's site on the first call and quote for the platform they really use.
03
Developers
See which framework, CDN and server sit behind a site you admire or a site you are about to take over.
04
Marketers
Find out which analytics and tag tools competitors run, and which store platform powers their shop.
How it works
From address to stack in seconds.
01
Enter a website
Type a domain or paste any address from the site. The detector checks its homepage.
02
We read the homepage
One request, like a browser makes, then its headers, cookies, generator tag, script and stylesheet paths and HTML are matched against our own list of tells.
03
Check the evidence
Every technology comes with what gave it away, so you can judge each match yourself.
FAQ
Questions, answered.
A CMS detector looks at a website from the outside and works out which content management system runs it, such as WordPress, Webflow or Shopify. This one also reports the site's ecommerce platform, framework, analytics tools, CDN, hosting and web server.
Enter the site's address above. The detector reads the homepage and matches it against known tells: a generator meta tag, file paths like /wp-content/ on WordPress, cookies a platform sets, and headers it sends. Doing this by hand means reading the page source and response headers yourself.
Yes. You can run 10 checks a day without an account. It uses no paid data provider, only a direct read of the site's public homepage.
Yes, in most cases. WordPress leaves clear tells: theme and plugin files under /wp-content/, core files under /wp-includes/, and a link to its REST API. When the site still shows its generator tag, the WordPress version is reported too. Some sites remove these tells on purpose, and then the detector cannot see them.
More than 60, in six groups: CMSs such as WordPress, Drupal, Webflow, Wix, Squarespace and Ghost; stores such as Shopify, WooCommerce, Magento and BigCommerce; frameworks such as Next.js, Nuxt, Astro and Angular; analytics and tag tools such as Google Analytics 4, Google Tag Manager, PostHog and Hotjar; CDNs and hosts such as Cloudflare, Vercel, Netlify and CloudFront; and servers such as Nginx, Apache and LiteSpeed.
Custom-built sites have no CMS to find. Sites on a headless CMS often show no trace of it in their HTML, and some sites strip the tells or sit behind a bot check that hides the real page. In all of these cases the result is honestly empty rather than a guess.
Only the homepage's HTML and headers are read, and its scripts are not run. Tools that load later, such as tags added through Google Tag Manager, are missed, and other pages on the site may use tools the homepage does not.
Each match shows its evidence, so you can check it. Most tells are specific to one platform. A weaker tell is marked as likely. A tell can still mislead, for example a file left behind after a migration, so treat the result as strong evidence rather than proof.
Yes. The detector works on any public website. It reads only what the site sends to every visitor, so the owner's setup is not touched.
Free SEO tools