Detect Any Website's Technology Stack

How It Works

Why this matters

Knowing what a site is built with answers questions that would otherwise take a conversation. Before a migration, it tells you what you are migrating from. Before a pitch, it tells you whether a prospect is on a platform your product integrates with. During competitive research, it shows which analytics, ad networks and support tools a competitor pays for — a rough but honest read on where their budget goes. Detection works from public signals: response headers, script sources, markup patterns and cookie names, all of which any visitor's browser already receives.

Common mistakes

• Reading absence as proof. A tool that isn't detected may simply be loaded later, proxied through a first-party domain, or server-side — detection finds what a page announces, not everything it uses.
• Checking a single page. Marketing pages and application pages often run entirely different stacks; the homepage rarely represents the product.
• Confusing a CDN with a host. Cloudflare in front of a site tells you nothing about where the origin server actually lives.
• Assuming a detected version number is current. Version strings frequently come from cached assets or generator tags that were never updated after an upgrade.

Recommended Tools

Frequently Asked Questions