What your tech stack tells us
We detect the CMS, framework, server and CDN from headers and markup, so every fix can point at the right settings screen.
Step by step, with screenshots: What Shopify theme is this? How to identify any store's theme →
Check your own site
Runs this check and the other 192, free, in about 45 seconds.
Or run only this check with the free WordPress theme & plugin detector or the free Tech stack & CMS detector.
What it is
A website's tech stack is the set of technologies it runs on: the CMS or framework, the web server, the hosting or CDN, and the analytics, tag managers and JavaScript libraries it loads. getReport detects them from response headers, HTML markup, script and file paths and generator tags.
Knowing the stack tells you where each fix in the report belongs, for example a WordPress plugin setting, a Shopify theme file or a Cloudflare switch, and helps your developer see old libraries or leftover trackers at a glance. The same information is visible to anyone, which is why version numbers in headers are better removed.
OK looks like this: nothing to fix; use the list to find the right settings screen for the other findings and check that nothing unexpected runs on the page.
What a passing site looks like
- Technology stack: passesinfo onlyeffort S
Technology stack
Why it matters. Knowing the CMS, framework, CDN and analytics behind a page helps you and your developer find the right settings for the fixes in this report.
- Nothing to fix; use this list to find the right settings panel for the other findings.
Questions people ask
Should I hide which technologies my site uses?
Hide version numbers, not the technology. A header such as x-powered-by: PHP/8.1.2 or a generator tag with the exact WordPress version tells attackers which known flaws to try, so remove those. Hiding that a site runs WordPress or Shopify gains little, because file paths give it away, and keeping the software updated matters far more.
Why does the report still show a technology I removed?
The report lists what the page loaded when it was checked, so a cached page, a plugin that still prints its script on some templates, or a tag manager that loads it can keep it visible. Clear the page cache, check the page source for the file name, then run the check again with a fresh result.
Why does the report show my tech stack?
So each fix can point at the right place. The same finding is solved in a plugin setting on WordPress, a theme file on Shopify or a switch on Cloudflare, and knowing the stack tells you and your developer where to look. It also shows old JavaScript libraries and leftover trackers at a glance. Detection is passive: getReport only reads what the page and its headers reveal to any visitor.