CMS & Tech Detector

Free, no signup. Inspect a public page for visible CMS, framework, CDN, ecommerce, analytics, JavaScript, and font fingerprints — with the exact evidence that fired.

Built by Patrick Stox

The HAR is parsed locally and is not uploaded. Request bodies, cookies, headers, and query values are not retained by tag inventory.

Checks run from our server; we fetch the URL you enter and don't keep the results. We fetch the URL you enter; the detector runs in your browser. Optional HAR parsing stays in this browser tab. Anonymous run-level outcome counters may be used for aggregate research; URLs, domains, IPs, and identifiers are never included, and no statistic is released below 100 runs.

Feedback
Report a bug

Found something broken in Tech Stack Checker? Let us know what happened — this goes straight to a private triage queue, not a public list.

What will be sent 
 No tool inputs, uploads, pasted source, complete results, query parameters, or URL fragments are attached automatically. You can edit or remove the selected passage above. Browser and anti-abuse metadata is processed for spam prevention. 
  
 
  
 
 
  
 
 
  
 
Sample report
Illustrative example — deterministic supported signatures
For HTML containing <meta name="generator" content="WordPress"> and asset paths under /wp-content/, the detector reports:
WordPress high confidence · CMS
Evidence: the generator fingerprint and WordPress asset-path fingerprint both matched.
A single supported fingerprint would be medium confidence. No match would produce an explicit “no signatures matched” message, not a claim that the page uses no technology.
 
 
 
How to use it
  1. Enter a public page URL, ideally a representative page rather than a login screen.
  2. Choose Detect stack and review each technology, category, confidence, and evidence string.
  3. Confirm important detections in source, response headers, or the platform itself before acting on them.
  4. Check more than one template when a site may use different technology by section.
 
 
     
 Local data 
Saved targets, named lists, and recent check summaries remain only in this browser.
 
   
 
      
How to read the result
  • High confidence means more than one signature for that technology matched.
  • Medium confidence means one supported signature matched.
  • Evidence names the signature rules that fired; it should be reviewed before treating a detection as fact.
  • No signatures matched means only that the current raw HTML and selected headers lacked a known signal.
 
Data sources & freshness
The server fetches public HTML and a selected response-header map. In the browser, the detector lowercases those values and compares them to a curated JSON signature list covering HTML substrings, generator metadata, headers, and supported cookie names. Matches are grouped by technology and sorted by category and name.
 
Features
  • CMSA content management system (CMS) is software that lets users create, manage, and publish digital content — like blog posts and pages — without writing raw code. WordPress, Drupal, and Joomla are the most common open-source CMS platforms., framework, CDN, ecommerce, analytics, JavaScript, and font categories.
  • Exact evidence for every detection.
  • Two transparent confidence levels based on match count.
  • Browser-side matching after the public fetch.
 
Limitations
The checker does not render JavaScript, scan a whole site, identify private infrastructure, verify versions, or test vulnerabilities. Proxies, tag managers, cached markup, and removed or spoofed fingerprints can cause false negatives or false positives.
 
Frequently asked questions
How does a technology detector identify a CMS or framework?
It matches public fingerprints in raw HTML and selected response headers against a maintained signature list. The report shows the exact signal that matched so you can judge it.
Why did the detector miss a technology I know the site uses?
A site can remove generator tags, proxy assets, rename paths, render signals with JavaScript, or hide origin headers behind a CDN. No match means no supported public signature was observed, not that the technology is absent.
Can a tech-stack detection be wrong?
Yes. Public strings can be shared, stale, or spoofed. One matching signal is medium confidence; multiple supported signals raise confidence, but neither is proof of the complete production stack.
Is this a vulnerability scanner?
No. It does not test versions, vulnerabilities, ports, authentication, or application behavior. It only reports supported public fingerprints.
 
Explore more
ToolHTTP Status & Redirect CheckerToolHTTP Header CheckerToolDNS CheckerArticleRedirect LoopsArticleWooCommerce SEO
 
 
 
Feature requests for Tech Stack Checker
 

Upvote what you want most. New ideas can be submitted from the floating Feedback menu;
      requests appear here once approved, and the most-wanted rise to the top.

   
Loading…
  
  ➕ Request a feature   
New requests are reviewed before they appear here.
 
     
  
  
 
 
 
 
   
         
 
Common issues & how to fix them
  
     
  •  Information CMS fingerprint is publicly visible Fix: If CMS disclosure is unintended, remove generator metadata and public version markers while keeping required assets functional. 
  •  Information Framework fingerprint is publicly visible Fix: If framework disclosure creates risk, suppress version-specific headers and signatures and keep the framework fully patched. 
  •  Information Analytics or tag-manager fingerprint is visible Fix: Audit every detected analytics and tag-manager script, remove unused tags, and gate nonessential tracking behind consent where required. 
  •  Warnings Server technology is disclosed in headers Fix: Remove or generalize Server and X-Powered-By headers at the origin or proxy, and patch the disclosed software. 
  •  Warnings Technology fingerprints conflict Fix: Inspect the conflicting headers, markup, and assets, then remove stale signatures so the reported stack matches production. 
    •