Free tools

Website Technology Checker

What a website is built with, as far as the page admits. Every finding comes with the evidence that produced it and an honest confidence, because a generator tag naming a version and a stylesheet path that looks about right are not the same quality of fact.

We read the public page and the robots file, nothing else. The address is not saved and there is no list of checked sites.

What this checks

  • The content management system, using the same detector our compatibility checker has run against real sites for months — so the two pages cannot disagree about what your site runs.
  • Frontend frameworks and libraries: React, Next.js, Vue, Angular, Svelte, jQuery, Bootstrap, Tailwind.
  • Analytics and marketing tags, shop platforms, and payment providers the page loads.
  • CDN, server software and hosting clues from the response headers, which are the most reliable findings of all because a server sent them deliberately.

What this cannot tell you

  • Most of a stack is invisible from outside. The programming language, the database, the caching layer, the operating system — none of it announces itself, and tools that report them are inferring from header order and guesswork.
  • An absent technology is an undetected one, not a missing one. A site behind a CDN that rewrites its markup can hide almost everything.
  • Versions are shown only where a site publishes them. Most do not, and we would rather show a blank than a number we inferred.

Questions people ask

How accurate is this?

For anything that names itself — a generator tag, a vendor script, a server header — it is as accurate as the page is honest, which is very. For patterns, it is a reasoned guess and labelled as one. That is why every row carries a confidence rather than presenting everything as detected.

It found nothing. Is the site hiding something?

Usually it is a static site, or one behind a CDN that rewrites the markup and strips the paths. Both are ordinary and neither is suspicious. There is no technology this tool can see that the page did not choose to show.

How is this different from your compatibility checker?

The same CMS detection sits behind both. The compatibility checker answers one question — can we manage this site, and what would that involve. This one lists the whole stack it can see and answers nothing about us. Use that one if you are thinking of connecting your site; use this one if you are curious what something is built with.