How to use the website technology checker
- Enter the site's address and press Detect technologies. A bare domain is checked over HTTPS.
- Read the grouped results. Confident means a distinctive marker was found; likely means a heuristic such as class-name patterns.
- Expand your understanding with the evidence lines: an asset URL, a header or a snippet of HTML.
- Copy the report to share it or keep it with your competitor or migration notes.
Features
- Over 120 signatures across frameworks (Next.js, Nuxt, Astro, SvelteKit, Angular, Vue, React), CMSs (WordPress, Drupal, Shopify, Webflow, Wix, Ghost…), CSS frameworks, servers and hosting providers
- Version numbers where the markers expose them (WordPress, jQuery, nginx, Apache, PHP, Angular…)
- Analytics, tag managers, ads, captchas, payment SDKs and chat widgets
- Backend hints from headers and cookie names (never cookie values)
- Redirect-aware fetch with the same public-only safeguards as the website status checker
How detection works
VoltKit's server requests the page like a browser would and reads three things: the HTML (script and stylesheet URLs, meta generator tags, distinctive attributes and class names), the response headers (Server, X-Powered-By, CDN request IDs) and the names of cookies the server tries to set. Each known technology has a small set of markers; when one matches, the technology is listed with that marker as evidence.
Nothing on the page is executed. That keeps the check fast and safe, but it also means technologies that only appear after JavaScript runs (some single-page apps, tag managers loading other tags) can be missed.
What it cannot tell you
A reverse proxy or CDN can hide the origin server, bundlers strip library names, and a site can simply serve custom code. Treat the report as a floor, not a full inventory. Version numbers reflect the markers in the page, which may be older than the deployed version. Only public sites on standard ports can be analysed; private and internal addresses are refused.