Security
What Is This Website Built With?
Detect the CMS, frameworks, analytics and server software behind a website.
Problem: You inherited a website and nobody can tell you what it runs on.
We analyse response headers, generator tags, script paths and known fingerprints to identify the technology stack a site is using.
What we'll check
- CMS or site builder
- JavaScript framework
- Analytics and tag managers
- Server software and CDN
- Version disclosure in headers or markup
Why this matters
- Knowing the stack tells you who can maintain the site and what it costs to change.
- Publicly disclosed versions tell attackers exactly which exploits to try.
- A stack of overlapping page builders and plugins is usually the root cause of slow pages.
- Before a migration or acquisition, you need to know what you are taking on.
Reduce what you disclose
- Remove version numbers from
ServerandX-Powered-Byheaders. - Strip the CMS generator meta tag.
- Remove version query strings appended to asset URLs.
- Keep everything patched — obscurity is not a substitute for updates.
Detection limits
Detection is based on public fingerprints. A site behind a CDN, or one that renders on the server with no telltale markers, may reveal little. An empty result is not proof that nothing is running.
Frequently asked questions
- Is it legal to check what a website uses?
- Yes. This only reads information the site publishes to every visitor.
- Why did detection find nothing?
- Some stacks leave no public fingerprint, especially behind a CDN or reverse proxy.