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.
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.
Sample report
Illustrative example — deterministic supported signatures
For HTML containing <meta name="generator" content="WordPress"> and asset paths under /wp-content/, the detector reports:
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
- Enter a public page URL, ideally a representative page rather than a login screen.
- Choose Detect stack and review each technology, category, confidence, and evidence string.
- Confirm important detections in source, response headers, or the platform itself before acting on them.
- Check more than one template when a site may use different technology by section.
Site passport Local context for this saved site
Local data
Saved targets, named lists, and recent check summaries remain only in this browser.
Visible fingerprints
Tag inventory evidence
Rate this tool
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.
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.
You won't be emailed about that request anymore.
Loading…
➕ Request a feature
New requests are reviewed before they appear here.
À propos de l’outil
Inspectez une page publique pour repérer les empreintes visibles du CMS, du framework, du CDN, de l’e-commerce, de l’analytics, du JavaScript et des polices. Saisissez une URL publique, lancez la détection et examinez la preuve exacte qui a déclenché chaque résultat.
Fonctionnalités
- Catégories CMS, framework, CDN, e-commerce, analytics, JavaScript et polices.
- Preuve exacte pour chaque détection et deux niveaux de confiance transparents.
- Comparaison dans le navigateur après la récupération publique, sans téléversement du HAR local.
Fonctionnement
Le serveur récupère le HTML public et une sélection d’en-têtes. Le navigateur met ces valeurs en minuscules et les compare à une liste JSON de signatures entretenue, puis regroupe les correspondances par technologie, catégorie et nom.
Limites
- L’outil ne rend pas le JavaScript, ne parcourt pas tout un site, ne vérifie pas les versions et ne teste pas les vulnérabilités.
- Les proxys, gestionnaires de balises, caches et empreintes supprimées ou usurpées peuvent produire des faux positifs ou négatifs.
Questions fréquentes
Comment un détecteur identifie-t-il un CMS ou un framework ?
Il compare les empreintes publiques du HTML brut et des en-têtes sélectionnés à une liste de signatures maintenue. Le rapport montre le signal exact qui correspond.
Pourquoi une technologie connue peut-elle ne pas être détectée ?
Un site peut retirer les balises de générateur, mandater ses ressources, renommer ses chemins, rendre ses signaux avec JavaScript ou masquer les en-têtes d’origine derrière un CDN.
Une détection peut-elle être erronée ?
Oui. Les chaînes publiques peuvent être partagées, obsolètes ou usurpées. Plusieurs signaux pris en charge augmentent la confiance, sans prouver toute la pile de production.
Est-ce un scanner de vulnérabilités ?
Non. Il ne teste ni versions, ni vulnérabilités, ni ports, ni authentification, ni comportement applicatif ; il signale uniquement les empreintes publiques prises en charge.