Free tool · No signup

Website technology detector

Find out what a website is built with — CMS, JavaScript libraries, server, CDN, analytics, CRM, payments and automation tools — and how up to date it looks.

No signup · Results in ~40 seconds · Nothing stored except the shareable report

What we check and why

How detection works

Every website leaves fingerprints: response headers, script and stylesheet paths, cookie names, meta generator tags, JavaScript globals and the hosts the page contacts. We collect them from a plain HTTP fetch and from a real browser visit and match them against known patterns. Each technology is reported with its category, a version where one is exposed and a confidence level.

Content management systems and site builders: WordPress, Drupal, Joomla, TYPO3, Wix, Squarespace, Webflow, Shopify and more.
Frameworks and libraries: React, Next.js, Vue, Nuxt, Angular, Svelte, jQuery and Bootstrap.
Web servers, hosting and CDNs such as Cloudflare, Fastly, CloudFront or Bunny.
Analytics and tag managers, advertising pixels, CRM and email marketing tools.
Payments, online booking and automation hooks such as Zapier, Make or n8n webhooks.

Why your stack matters

Knowing what your site runs on is the first step for any improvement project. A developer quoting for changes, an IT provider checking for security updates or a consultant planning an automation all start with this inventory. For many small firms nobody has a written record of it, especially after an agency relationship has ended.

The detector also highlights modernization signals: jQuery older than version 3, Bootstrap older than 4, an exposed PHP version, HTTP/1.1 only, no modern image formats, legacy analytics or a long list of visible plugins. The Modernization Score summarises them, where 100 means the site looks modern.

Limits

Detection is based on what the site exposes publicly. Well-configured sites hide versions, and server-side tools that leave no trace in the page cannot be seen. A missing technology does not prove it is absent, and an exposed version number should be confirmed in your admin panel before you act on it.

Use the result as a starting inventory: confirm it with whoever maintains the site, note licence renewals and owners, and keep the list with your other IT documentation so the next person does not have to rediscover it.

Common findings on firm websites

On small professional-services sites we typically find WordPress with a commercial theme and a page builder, a handful of plugins, Google Analytics or Tag Manager, Google Fonts, an embedded map and a contact form plugin. None of that is a problem in itself. The useful questions are whether each component is still maintained, who updates it, and whether every third-party service on the list is still needed and covered by your privacy policy.

Frequently asked questions

Can I check which CMS a competitor uses?

Yes. The detector reads only public information that any browser receives. It works on any public website.

Why is a version number shown as a risk?

Publicly exposed versions make it easier for automated attacks to target known vulnerabilities. Hiding the version is not a fix in itself, but keeping software updated and not advertising it is good practice.

Is jQuery bad?

Not in itself, but versions before 3.5 have known security issues, and many modern sites no longer need it. An old jQuery often indicates an old theme that has not been updated.

How do you detect automation tools?

We look for webhook URLs, embedded forms and scripts from services such as Zapier, Make and n8n in the page and its network requests. Automations that run entirely on servers are not visible.