How does probeo detect the technology a site runs on?

Probeo names the technology behind each page: where it’s served from, what built it and which third-party tools it loads. On a site assembled over years, the stack is rarely what anyone remembers. A tag manager, a second analytics tool or a page left on an old platform shows up here page by page.

What probeo checks

For every page, probeo records:

• CDN. Such as Cloudflare, Amazon CloudFront, Fastly, Akamai, Vercel or Netlify.
• Hosting. Such as Shopify, Webflow, WP Engine, Kinsta, Google Cloud, AWS or Heroku.
• Server. The name and version the Server header gives, when it gives one.
• Server-side frameworks. The ones the headers announce, such as PHP, Express, ASP.NET, Ruby on Rails or Next.js.
• Platform and front end. What the page’s HTML shows it was built with, such as WordPress, Shopify, Drupal, Webflow, Next.js or React, with a confidence score. A page with no recognizable framework is recorded as “static / no framework”.
• CSS and JavaScript libraries. Such as Tailwind CSS, Bootstrap, Alpine.js or HTMX.
• Tools. Third-party scripts for analytics, tag management, consent, chat, A/B testing, payments, forms, video and more, such as Google Tag Manager, Hotjar, OneTrust, Intercom or Stripe.

How probeo checks it

Each detection matches a known fingerprint: a response header the platform sets, a path its files are served from, or a script the tool loads. Headers identify the CDN, hosting, server and server-side frameworks. The page’s HTML identifies the platform, the front end, the libraries and the tools.

The front-end confidence reflects the evidence. Platforms that leave an unmistakable mark, such as Next.js or WordPress, score highest. A page that shows only generic React or Vue markers scores lower.

What this does not cover

Detection reports what it finds evidence for. A tool loaded only after a visitor interacts, or a platform configured to hide its headers, can go undetected, so an empty result isn’t proof of absence.

Stack detection records facts, not problems. It doesn’t flag outdated versions or known vulnerabilities. Headers that give away versions are reported separately, under Security headers.

Common questions

Why does one page show a different stack from the rest?

Sections of a site are often served by different systems: a blog on one platform, a store on another, landing pages from a third. Probeo checks each page on its own, so those differences show.

Can probeo tell which version of a framework I run?

Only where the server announces it. The Server header’s version is recorded when present; framework versions are not.

Does probeo find tools loaded by a tag manager?

It finds the ones present in the page’s HTML as the browser renders it. A tool injected later, after a click or a consent choice, may not be.