- Home
- Free tools
- Website tech stack checker
Website tech stack checker
Find out what a site is built with: CMS, JavaScript framework, web server, CDN, analytics, ads and more. Detection uses the response headers, cookies and HTML only, and flags versions that should not be exposed.
How to use it
- Enter a page address.
- Read the table of detected technologies, grouped by category, with the evidence for each.
- If you own the site, check the fix list for exposed versions and outdated components.
What it checks
- CMS and website builders (WordPress, Shopify, Wix and others)
- JavaScript frameworks and libraries, with versions where visible
- Web server, language and CDN or hosting signals
- Analytics, tag managers, ad and marketing tools
- Payments, chat widgets, captcha, cookie consent
- Exposed server, PHP or WordPress versions and old jQuery
Limits
- Detects technology from signatures in the HTML, headers and file paths. It can miss tools that leave no trace, or misreport hidden ones.
- Does not detect server-side software or plugins that never appear in the page.
- Version numbers are shown only when the site exposes them.
Public pages only, one page at one point in time. See the methodology and terms.
Frequently asked questions
How does the detection work?
It matches known patterns in the response headers, cookie names, script and stylesheet addresses and the HTML of the first response. It does not run JavaScript, so technologies added later in the browser may not appear.
Why is nothing detected?
Some sites are hand-built, use a custom stack, load everything with JavaScript after the first response, or hide their headers behind a CDN. Absence of a signal is not proof of absence.
Can the result be wrong?
Yes. Signals can be removed or faked, and some patterns are shared between products. Treat it as a good guess, and the evidence column shows why each item was listed.
Why does it matter if my versions are visible?
Version numbers let attackers look up known vulnerabilities for your exact software. Hiding them is cheap, but the real fix is keeping software updated.
Is it OK to check someone else's site?
Yes. It makes one normal page request, the same as a visitor, and reads only public information.
Does it detect hosting providers?
Only when a header or cookie reveals them (for example Cloudflare, Vercel or Netlify). Many hosts leave no visible trace.