Tech Stack Detector

Load a URL in headless Chromium and identify the CSS frameworks, JS frameworks, analytics, CDNs, CMS, and hosting platform used to build the site.

Page is fully rendered before analysis. May take 10–15 s.

Monitor this automatically

NetTests can run this check on a schedule, preserve historical results, compare changes over time, and alert you the moment something breaks.

Start monitoring free → See all monitoring products

Frequently Asked Questions

How does the Tech Stack Detector identify technologies?

It loads the URL in headless Chromium, then analyses: HyperText Markup Language (HTML) meta tags (generator, powered-by), JavaScript (JS) global variables (window.jQuery, window.__NEXT_DATA__, etc.), loaded script and Cascading Style Sheets (CSS) filenames, response headers (X-Powered-By, Server), and known Document Object Model (DOM) patterns. The result covers JS frameworks, CSS frameworks, analytics, Content Delivery Networks (CDNs), Content Management System (CMS) platforms, and hosting providers.

What kinds of technologies are detected?

React, Vue, Angular, Next.js, Nuxt, Svelte (JavaScript (JS) frameworks) — Tailwind CSS, Bootstrap, Material User Interface (UI) (Cascading Style Sheets (CSS)/UI frameworks) — Google Analytics, Segment, Hotjar (analytics) — Cloudflare, Fastly, AWS CloudFront (Content Delivery Networks (CDNs)) — WordPress, Drupal, Ghost, Shopify (Content Management System (CMS)/e-commerce) — Vercel, Netlify, GitHub Pages (hosting). Detection depends on the technology leaving identifiable fingerprints in the page.

Can sites hide their tech stack?

Yes — production sites often obscure fingerprints: removing generator meta tags, renaming or hashing asset files, stripping X-Powered-By headers, and avoiding framework-specific class name patterns. Security-conscious sites do this to reduce attack surface. A 'not detected' result doesn't mean a technology isn't used — it means no recognizable fingerprint was found.