What CMS is this website using?

We send one ordinary request to the site’s home page, just like a visitor would. Then we read the response headers, the HTML, and the scripts the page loads. Every platform leaves its own fingerprints, from file paths to telltale attributes and script vendors. Each fingerprint has a weight. A match in the headers counts for more than one in the HTML, because headers are harder to fake. The platform with the highest score wins. Other notable technologies on the page are listed separately

Look in three places: the page source, the response headers, and the admin login address. In the source, look for file paths like /wp-content/ or /bitrix/ and the generator meta tag. But no single clue is proof. The meta tag is often removed during setup. The admin page can be moved. And a familiar path can linger on a site that switched platforms long ago, or on a copied template that kept its folders. The answer comes from all the clues together

556 CMSs, ecommerce platforms, website builders, and frameworks from around the world. From WordPress, Shopify, and 1C-Bitrix to niche platforms like HostCMS and Moguta.CMS. In the results, each platform name links to its official website

The result is based on fingerprints, so it’s an answer, not a guarantee. Most sites leave plenty of clues, and they all point the same way. Edge cases do happen. A site may still carry traces of the platform it moved from. A website builder on a custom domain may hide its markers. A heavily customized theme can mask the usual paths. If a result surprises you, check the page source. The detector reports exactly what it found there

Yes, the part that identifies the platform. It lives in cmslens, an open-source library: the table of 556 platforms with their fingerprints and weights, the page parser, and the tests are on GitHub under the MIT license. You can see exactly why the detector gave its answer, and if it got your site wrong, you can send a fix there

There are three possible reasons, and each has its own label. “Custom-built” means we found no fingerprints of any known platform. The site is hand-coded or built with a framework that leaves no trace. “Behind a firewall” means a service like Cloudflare stands in front of the site, and we couldn’t get to the HTML. “Couldn’t reach” means the domain didn’t respond. There may be a typo in the address, the site may be down, or it may block outside requests

Yes. The page lists the latest checked domains and the platforms found, and yours will appear there too. Nothing else is shown. Not who ran the check, and not where from