Skip to main content
Domains → Tech Stack detects what your site is built with — CMS, frameworks, analytics, CDN, payment providers, and more.

​
Running a detection

Click Refresh to run a detection. The button shows a spinner while it works, and a progress indicator tracks the job. When a run has completed, the header shows Last updated with the exact date and time. Detection doesn’t run on a schedule. It happens once as part of a project’s initial collection, and after that only when you click Refresh.

​
Results

A summary line reads 47 technologies detected on example.com, followed by one card per category. Each technology in a card shows: Confidence is worth reading before acting on a result. A technology detected at 100% left an unambiguous fingerprint; one at 40% was inferred from weaker signals and may be wrong. Version is usually only available when the technology exposes it — in a meta tag, a script path, or a response header. Its absence doesn’t mean the technology isn’t there.

​
What it’s useful for

On your own domain, it’s a quick inventory: an unexpected analytics script, a CMS version you thought you’d upgraded, or a tag left over from an old vendor. Exposed version numbers are also worth noting — if Surnex can read your CMS version from the page, so can anyone. On a competitor, the stack explains capability. A site on a headless framework with a CDN will be hard to beat on speed; one on an aging CMS with several tag managers probably won’t be. Knowing what a competitor’s site can do is context for web vitals comparisons.
This page only analyzes your project’s domain. There’s no field for another domain here.

​
Failures

A failed run shows a red banner: “Analysis failed: … Click Refresh to retry.” Most failures are the site being unreachable at detection time, or blocking automated requests. Retrying usually resolves it.

​
Detection limits

Detection reads what the page exposes to a visitor, so:
  • Server-side technology is largely invisible. Databases, queues, and back-end languages leave no reliable trace unless a header reveals them.
  • A CDN or proxy can mask the origin. You may see the CDN and nothing behind it.
  • Absence isn’t proof. A technology loaded conditionally, after consent, or only on other pages won’t be detected from one page load.
Read the results as “these are definitely present”, not “this is everything”.