Technology Stack Checker
Detect the technology behind a website: CMS or framework, web server, CDN and powered-by signals — all from one request.
How to read the result
- CMS / framework
- The content management system or framework behind the page, identified from markup and headers.
- CDN
- Any content delivery network or firewall detected in front of the origin.
- Server
- The web server software named in the response — or the CDN's, when one is in the path.
- X-Powered-By and HTTP version
- The runtime the site admits to, and which HTTP protocol version the connection negotiated.
Where this tool is wrong
Every check here reads one signal, and each has a blind spot worth knowing before you act on the answer.
- Everything here comes from a single request to the homepage. A large site can run several different stacks on different paths, and none of that is visible from one page.
- This detects what identifies itself. Analytics, tag managers, payment widgets and JavaScript libraries are not covered — this is infrastructure detection, not a full inventory.
- Server and runtime strings are self-reported and can be suppressed or falsified.
- A CDN in the path masks most of what is behind it. When one is detected, treat the server and runtime fields as describing the edge rather than the origin.
Common questions
Why is the CMS field empty?
Either the site is hand-built or uses a framework without a recognisable fingerprint, or its CMS markers have been deliberately stripped. Both are common; neither indicates a problem.
Does this see everything a commercial tech-lookup service sees?
No. Those crawl repeatedly and inspect scripts to catalogue hundreds of front-end products. This reads one response and reports the infrastructure layer — CMS, server, CDN — which is the part that matters for hosting questions.
Can I use this to check a competitor's setup?
For the infrastructure layer, yes — that information is published to every visitor. What you will not get is anything behind a login, anything that only loads on inner pages, or the origin details of a site behind a CDN.
Why does it detect the CDN but not the CMS?
Because a CDN identifies itself in response headers it controls, while a CMS is identified from markup the site owner can change. Hiding the CMS is easy and common; hiding the CDN is neither.