CMS Detector: How to Find What CMS a Website Runs Before You Touch It
CodexFuse Team · 2026-10-27T10:04:32.068Z · 9 min read min read
Free CMS Detector: find what CMS a website runs, what None and Not found mean, and what to do after you know the platform.
A cms detector identifies the content management system a website runs on — WordPress, Shopify, Wix, Squarespace, Drupal, Joomla, or a custom-built platform with no CMS at all. Knowing the platform before you edit, migrate, quote, or secure a site saves hours of guessing, because every CMS has different logins, plugins, themes, and failure modes.
Not every detector works the same way. Some scan a site's live code for fingerprints; the free CodexFuse CMS Detector is a fast reference lookup against a table of 16 well-known sites. It is instant for those sites — and, by design, silent on anything outside the table. This guide shows you how to use it properly and read its three kinds of result.
What Is a CMS Detector?
A CMS detector is a tool that tells you which content management system powers a website, usually by checking HTML, meta generator tags, and script paths for platform fingerprints, or — as with the CodexFuse tool — by looking the hostname up in a reference table. The answer matters because a WordPress site, a Shopify store, and a custom-built site are maintained, backed up, and secured in completely different ways.
How Do You Use the CodexFuse CMS Detector?
Using the tool takes under a minute, with nothing to install. It asks for a hostname, not a full page address.
- Enter a hostname: type a hostname such as
wordpress.com— not a full URL with a page path, and not a search query. - Hit Detect CMS: the tool looks the hostname up in its built-in reference table of 16 sites.
- Read the one-line result: you get the CMS name,
None, orNot found— each means something different, as the next section explains. - Copy it if you need it: the one-click copy button gives you a line like "wordpress.com — CMS: WordPress" for notes, tickets, or client reports.
Check the hostname exactly as it appears in the address bar, minus the page path. Typing example.com/blog/post instead of example.com is the most common reason a lookup fails when the site itself is fine.
What Do the Results Actually Mean?
The CodexFuse tool returns only three kinds of answer, and confusing them leads to bad decisions. This table is the whole result vocabulary:
| Result | What it means | What to do next |
|---|---|---|
| A CMS name (e.g. WordPress) | The hostname is in the table and runs that CMS. | Plan work for that platform specifically. |
| None | The hostname is in the table but runs no CMS — it is custom-built. | Expect hand-rolled code, not plugins or themes. |
| Not found | The hostname is not in the 16-site table at all. | Use a live scanner instead; do not conclude anything about the site. |
Seven reference hostnames return a CMS: wordpress.com (WordPress), shopify.com (Shopify), wix.com (Wix), squarespace.com (Squarespace), drupal.org (Drupal), joomla.org (Joomla), and cloudflare.com (Contentful). Nine return None — google.com, facebook.com, github.com, stackoverflow.com, apple.com, microsoft.com, amazon.com, netflix.com, twitter.com — all custom-built, not broken.
The distinction between None and Not found is the one most people get wrong. None is a positive finding: the tool knows the site and knows it uses no CMS. Not found is an absence of information: the tool has no record of that hostname, and the site may well run WordPress or anything else.
When Is a Quick Lookup Enough — and When Isn't It?
It is not enough for an arbitrary client site, a competitor's store, or a site you are about to migrate. Those need a live cms detector that fetches the site and checks its HTML, meta tags, and script paths for fingerprints. Treating Not found as "no CMS" means scoping the wrong work and possibly hunting for an admin panel that does not exist.
Never present a Not found result to a client as a finding about their site. The honest wording is: "This quick lookup has no record of that hostname, so we need a live scan to identify its platform." That one sentence protects your credibility.
That is exactly where unmanaged hosting turns into update failures, plugin conflicts, and security gaps. Move it to CodexFuse and let a fully managed team handle hosting, updates, and backups on pay-as-you-go credits — no subscription, no server babysitting.
Get Started with CodexFuseWorked Example: A Designer Inherits Three Client Sites
Maya is a fictional freelance web designer in Manchester. A small agency hands her three client sites on a Friday afternoon with one instruction: "Tell us what each one runs by Monday, so we can price the maintenance." She has no logins yet and no access to any server. Here is what she does with the CodexFuse cms detector, and what each result actually tells her.
First she types wordpress.com as a control test; it returns WordPress. Then she records three reference cases in a handover note:
| Hostname checked | Tool result | Maya's conclusion |
|---|---|---|
| wordpress.com | WordPress | Control test passed; the tool works as expected. |
| shopify.com | Shopify | A Shopify store needs store, theme, and app work — not WordPress plugins. |
| google.com | None | Custom-built; no CMS admin to hunt for, and no plugin route in. |
What Should You Do After You Know the CMS?
- WordPress: budget for core, theme, and plugin updates, backups before every change, and a security routine. A WordPress site with no update habit is a site waiting for a bad week — see this WordPress maintenance checklist for what that routine actually contains.
- Shopify, Wix, or Squarespace: work inside the platform's own admin, themes, and app or extension limits. You cannot "just install a plugin" the way you would on WordPress, and migration means exporting content, not copying files.
- Drupal or Joomla: treat these as specialist platforms. Fewer generalist freelancers know them well, so factor specialist time into any quote rather than assuming a WordPress workflow fits.
- None (custom-built): ask who owns the code, where it is hosted, and how deploys happen. There is no plugin directory to fall back on, so every change is development work.
- Not found: run a live scan before scoping anything. Guessing the platform from a
Not foundis how migrations go wrong — a proper website migration checklist starts with verified facts, not assumptions.
If the site is WordPress on unmanaged hosting, the concrete CodexFuse move is: back everything up and record plugins and theme, move hosting, email, and backups to the managed platform, then spend credits only on services you use — no subscription, no lock-in. See this guide to bringing WordPress maintenance under control for the same sequence step by step.
Before you quote any site work, read the honest breakdown of what running a website really costs — the CMS you find here decides a large part of that number.
Common Mistakes People Make With a CMS Detector
- Reading "Not found" as "no CMS": it only means the hostname is outside the 16-site table. The site may run any CMS at all.
- Checking a full page URL instead of a hostname: page paths are not in the table, so they return
Not foundeven for sites the tool knows. - Ignoring what the CMS implies: finding WordPress and quoting generic work misses its update and backup routine — see what to do when a website is hacked.
- Skipping the live scan for real client work: a reference lookup is a starting point, not a site audit. For anything you will bill for, verify with a live fingerprint check.
Frequently Asked Questions
What is a CMS detector?
A CMS detector identifies the content management system a website runs on, such as WordPress or Shopify. Most scan a site's HTML for fingerprints; the CodexFuse tool instead looks the hostname up in a 16-site table, so it answers instantly for those sites.
Can the CodexFuse CMS Detector identify any website?
No. It can only return a result for the 16 hostnames in its reference table. Any other hostname returns Not found, which means "no record here," not "no CMS." For an arbitrary site, use a live scanner that reads the site's actual code.
What does "None" mean in a CMS detector result?
None means the site is in the reference table and is custom-built — it runs no content management system. Google, Facebook, GitHub, and Amazon are examples: they are hand-rolled platforms, not WordPress or Shopify sites.
Is the CodexFuse CMS Detector free?
Yes, the tool itself is free and unlimited, and it runs in your browser with no software to install. Note that the tool page asks you to log in to use it, so have a free CodexFuse account ready before you start a batch of lookups.
How do I copy a CMS detector result?
Use the tool's one-click copy button after a successful lookup. It copies a one-line summary such as "wordpress.com — CMS: WordPress," ready to paste into a client report, ticket, or handover note.
What should I do if the result is "Not found"?
Do not guess. Run a live scan that checks the site's HTML, meta tags, and script paths, and record the result as "unknown" until it answers. Scoping work from a Not found alone risks the wrong platform and price.
Found the CMS? Now Stop Babysitting the Site
A cms detector answers one question in seconds: what is this site built on? The harder question is who updates it, backs it up, and fixes it when it breaks. If your answer is "me, at midnight, again," the unmanaged setup — not the platform — is the problem.
Move your hosting, business email, security, and backups to CodexFuse today: a fully managed, all-in-one platform on pay-as-you-go credits, with no subscription and no lock-in. Start by moving the WordPress site you just identified, hand the maintenance to the managed team, and spend your time on the business the site exists to serve — not on the server underneath it.