b2KIT

Website Technology Checker

Detect technologies, frameworks, CMS, analytics, and libraries used on web pages from HTML analysis.

Tested tool guide Tested browser tools Checked August 16, 2026

What Website Technology Checker does, with a checked example

This tool scans HTML source you paste in and matches it against known signatures for CMS platforms, JavaScript frameworks, analytics services, and libraries: a WordPress generator meta tag, a Shopify CDN path, a gtag.js script, a jQuery filename, and similar markers. It reports each match with a category and, where the markup states one, a version number. The common surprise is that it only sees what's in the HTML you supply - content injected later by client-side JavaScript, or anything only visible in HTTP response headers, won't be detected at all.

Worked example

A concrete input and expected output from the current implementation.

Input

<head>
<meta name="generator" content="WordPress 6.4">
<script src="https://www.googletagmanager.com/gtag/js?id=UA-12345678-1"></script>
<script src="https://code.jquery.com/jquery-3.6.0.min.js"></script>
</head>

Expected output

CMS: WordPress 6.4 (meta generator tag)
Analytics: Google Analytics / gtag.js, tracking ID UA-12345678-1 (script src)
JS Library: jQuery 3.6.0 (script src filename)

Each detection is read directly off the pasted markup: the generator meta tag states the WordPress version literally, the googletagmanager.com/gtag/js path identifies Google's tag, and the jquery-3.6.0.min.js filename carries its own version number.

How the result is produced

1

Signature matching

The tool runs the pasted HTML against a list of known fingerprints - meta tag names and content, script and link src/href patterns, HTML comments, id/class naming conventions, and inline script snippets - and reports every rule that matches, grouped by category (CMS, analytics, framework, library).

2

Paste, don't fetch

You provide raw HTML rather than a live URL. Since the tool runs client-side, fetching another site's markup from the browser is generally blocked by cross-origin restrictions unless that site opts in, so the reliable path is pasting output from 'view source' or a downloaded HTML file.

Good uses

  • Viewing a competitor's landing page source and pasting it in to see what CMS and analytics stack they're running
  • Confirming that a tag manager snippet or plugin script actually landed in the rendered HTML after a deploy or migration
  • Checking which JS library versions a third-party or vendor page loads before integrating with or embedding it

Limits and checks

  • Anything a JavaScript framework inserts after the initial page load - client-rendered React/Vue apps, dynamically injected analytics tags - won't appear in plain view-source HTML, so those stacks can go undetected
  • Version numbers only surface when the markup itself states one, like a filename or generator tag; minified or renamed assets with no visible version string won't yield a version
  • A matched script src or class name shows the resource was referenced, not that it's actively used - leftover, commented-out, or conditionally loaded tags can still trigger a match

Common questions

Can I enter a URL instead of pasting HTML?

If the tool only accepts pasted markup, that's likely because a browser-side script can't reliably pull another site's raw HTML across origins without that site's cooperation. Use your browser's 'view source' or save-page-as output and paste that in instead.

Does it tell me the server, CDN, or hosting provider?

No. That kind of detection normally relies on HTTP response headers (like Server or CDN headers), which aren't part of the HTML document body, so a tool limited to HTML analysis can't confirm them - a CDN domain in a script src is a hint at best, not proof.

References and verification

The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools