No Signup Unlimited Usage Real Data 100% Free Privacy First Fast Results Export Reports Mobile Friendly

Website Technology & CMS Detector

Find out what a website is built with: CMS, e-commerce platform, JavaScript framework, CDN, analytics, tag managers, server and programming language, detected from the HTML, HTTP headers and cookies with version numbers and a confidence level for each match.

Fetching live data…

Quick answer

The Website Technology & CMS Detector shows what a website is built with. Enter a URL and the tool reads the page's HTML, HTTP headers and cookies, then matches them against more than 300 fingerprints. It names the CMS or shop platform, JavaScript framework, web server, CDN, analytics and tag managers, payment and chat widgets, with a version number where one is exposed and a confidence level for each match.

How it works

  1. Enter a page URL. The tool requests it once with a normal browser User-Agent, follows any redirects and records each hop.
  2. It collects the fingerprints a page gives away: <meta name="generator"> tags, script and stylesheet paths, inline script variables such as __NEXT_DATA__, cookie names, and headers such as Server, X-Powered-By and Via.
  3. Each piece of evidence is matched against our own signature list. Strong evidence (a generator tag or a vendor header) counts more than a weak one (a single path in the HTML), and several independent matches raise the confidence to 100%.
  4. Related technologies are added as implied: WooCommerce implies WordPress, and WordPress implies PHP and MySQL. They are labelled so you can tell them apart from technologies seen directly.

What you get

  • Headline — a one-line summary such as "Built with WordPress 6.5 + WooCommerce", followed by cards for the web server, CDN or host, and analytics.
  • Technologies by category — CMS, e-commerce, site builders (including Turkish platforms such as Ticimax, İdeasoft, T-Soft and ikas), JavaScript frameworks, web servers, languages, CDNs, hosting, security and WAF, caching, SEO plugins, analytics, advertising, cookie consent, live chat, payment, fonts, maps and video.
  • Version and confidence — the version is taken from the evidence itself (a generator tag, a jquery-3.7.1.min.js file name, an ng-version attribute). Open the evidence list under each entry to see exactly what matched.
  • Security notes — flags exposed version numbers that make targeted attacks easier: a CMS version in the generator tag, a PHP version in X-Powered-By, an exact server version, jQuery older than 3.5.0, or end-of-life AngularJS.
  • SEO notes — for example a JavaScript framework with almost no text in the raw HTML, two SEO plugins installed at once, or a heavy page builder worth measuring for speed.
  • Response details and export — final URL, status, redirects and revealing headers, plus a table for CSV and a JSON export.

Why it matters

Knowing the stack behind a site answers practical questions quickly. When you take over an SEO project, it tells you which CMS and SEO plugin control titles, canonicals and schema, so you know where to make fixes. In competitor research it shows which platforms and marketing tools similar businesses use, and in an audit it surfaces forgotten scripts or outdated libraries.

The same fingerprints help attackers too. Headers such as Server and X-Powered-By, or a generator tag with an exact version, tell an automated scanner which known vulnerabilities to try. The OWASP Web Security Testing Guide treats this kind of fingerprinting as the first step of an assessment. Hiding version numbers does not fix an outdated component, but it stops the site from advertising one.

How to read and act on the results

  1. Check the headline first. An unexpected platform can mean the page is served by a different system, such as a landing-page builder.
  2. Open the evidence for low-confidence entries. A single HTML match at 40-50% is a hint, not proof.
  3. Work through the security notes. Remove the generator tag, set expose_php = Off, hide the server version (server_tokens off in nginx, ServerTokens Prod in Apache) and update outdated libraries. Then run the Website Security Checker for a wider passive check and the HTTP Header Checker to review every header.
  4. Follow the SEO notes. If a client-side framework leaves the raw HTML almost empty, compare the raw and rendered page with the JavaScript Rendering Checker; if a heavy page builder or theme is found, measure it with Page Speed & Size Test. For competitor work, combine the stack with the Site Explorer to see how those sites perform.

Frequently asked questions

How accurate is technology detection?

It is as accurate as the fingerprints a page exposes. Clear traces such as a generator tag, a vendor header or a platform's own CDN are detected reliably. The tool reads one HTML response without running JavaScript, so scripts added later by a tag manager, server-side tools that leave no trace and deliberately hidden fingerprints can be missed. Each result shows its confidence and evidence.

Why is a technology marked as implied?

Some technologies cannot be seen from outside but follow from another one. A WooCommerce store runs on WordPress, and WordPress runs on PHP with a MySQL-compatible database. Implied entries are shown with a lower confidence and an "implied by" note instead of direct evidence.

Can I see the WordPress theme and plugins?

Popular themes and plugins that leave clear traces are detected, for example Elementor, Divi, WPBakery, Yoast SEO, Rank Math, WP Rocket, LiteSpeed Cache, Contact Form 7 and Wordfence. The tool does not probe plugin folders or guess URLs; it only reports what the page itself shows.

Is it safe and legal to check another website?

Yes. The tool makes one normal page request, like a visitor opening the page, and only reads what the server sends publicly. It does not log in, scan for files or test for vulnerabilities, and results are cached for six hours.

Learn & Resources

Guides, tips and tutorials hand-picked for this tool — go from running a check to actually fixing it.