No signup · No email · Completely free forever
Find out what CMS a website is using — the publishing system that powers the site — and other public components, whether that is a CMS or framework, ecommerce, CDN, or server software. We match technology fingerprints in the page’s HTML, CSS, headers, scripts, and meta tags. Custom, headless, or heavily customized sites can be missed.
Paste a hostname or a full URL. We fetch the homepage and match technology fingerprints to identify the website CMS and other public components. Results are not a guarantee — hidden or custom platforms may not appear.
1 target per run · 10 domains per day.
Use a CMS detector when you need the public CMS — and the other visible components — behind any site. There are several ways to find the CMS; this tool helps you quickly find it from public fingerprints. To see what CMS is this site using, start with the form above, then read the CMS card and the technologies used on the homepage.
example.com). One target per run.Chrome extension
Install the free Karma Domains add-on to see domain age and Karma Metric on SERPs — and run Checks from the popup.
A CMS detector answers a public-source question: which content management system, if any, leaves fingerprints on the website. It is not a backend audit and not a vulnerability scan. You can instantly identify many popular platforms from those traces, but you still see only what the homepage exposes — not a complete inventory of the server.
We fetch the homepage and compare it with a library of technology fingerprints in site elements: HTML patterns, CSS, HTTP headers, script URLs, meta tags (for example a generator tag), and sometimes a favicon. Matches are grouped by category so you see the CMS first, then the rest of the public components. A locked-down or heavily stripped front end can look empty even when a CMS sits behind it.
The CMS is the publishing system. Popular CMS platforms include Shopify, Webflow, Drupal and Joomla, and Wix and Magento, plus builders like WordPress or Squarespace when their fingerprints are visible. Fingerprints can also match other CMSs like Joomla when traces are public. The same page may also run a JavaScript framework, an analytics tag, a CDN, and a web server. Those are useful context; they are not the same thing as the CMS. WordPress’s popularity means it appears often in public fingerprints, but that does not mean every site runs it. A custom or headless build can still be missed, and a visible library does not, by itself, prove which CMS sits behind the page.
Custom builds, headless setups, and sites that strip default paths, generator tags, or a distinctive favicon often leave too few traces. A miss is not proof that no CMS is used — only that we did not see a public fingerprint. Sites that use CMS software can still hide the usual traces.
We do not log into the admin, inventory every installed add-on, scan for vulnerabilities, or export a bulk CSV of thousands of sites. A dedicated theme report, if we ship one later, is a separate page. The check is a single-page read: useful when you want a public-source view of the homepage, not a substitute for a logged-in audit.
The CMS matched from public fingerprints, when one is visible, plus other detected components grouped by category (ecommerce, CDN, server, and so on).
We fetch the homepage and match technology fingerprints in HTML, headers, scripts, and meta tags. We do not claim a complete inventory of hidden or custom software.
The site may be custom or headless, the usual traces may have been removed, or the homepage may have failed to load. Other component rows can still appear.
Yes. Fingerprints can miss hardened or heavily customized sites, and they only see what the homepage exposes. Treat the result as a public-source clue, not a certified audit. If traces are thin, look at the other categories in the result — they can still reveal related components in scripts or headers even when the CMS card is empty.
If a plugin is visible, it appears with the other public components. When the CMS is WordPress, fingerprints may also show which plugins are powering a WordPress website using a public theme. A full theme report is not this page’s job; a separate theme page may come later.
This page answers what CMS the site is using. For a category-by-category stack across the site, use Website Built With Checker. Hosting Checker answers who the hosting provider is. IP Lookup answers which addresses and networks it uses.
No signup for the free tier. Limits match other Karma landing-tools: 1 target per run and the shared free daily domain limit of 10 per day.
Yes — the free Karma Domains add-on on the Chrome Web Store shows domain age and Karma Metric on SERPs and runs Checks from the popup.
Alongside this free check, the full list of expired domains from 49 lists across 32 platforms (auctions, drops and buy-now listings) is on the Karma.Domains homepage, updated hourly.
See domain age and Karma Metric on SERPs — and run WHOIS, name lookups, and other Checks from the popup. Free on the Chrome Web Store.