Technology Detector

A technology stack is the CMS, framework, and libraries a site appears to use, often guessed from HTML, cookies, or headers. Real detection needs that response. This card shows a stack without fetching the URL.

The three stacks are WordPress with PHP 8.1, Nginx 1.24.0, Google Analytics GA4, and Cloudflare; Shopify with Ruby on Rails, Meta Pixel, and Fastly; and Contentful with Next.js 14.1, Vercel, and Plausible. Your URL does not choose among them.

CMS is one of the values Technology Detector puts on screen. The content system, such as WordPress or Shopify. The sample draws WordPress 6.4.2, Shopify, or Contentful. A custom site can still be labeled WordPress.

Read Framework on its own before you mix it with the other rows. The language or UI framework. The draw is PHP 8.1, Ruby on Rails, or Next.js 14.1. Those versions are not read from a header.

Server answers a narrower question than the headline number. The software that answered. The draw is Nginx 1.24.0, Cloudflare Server, or Vercel. Server software has to be confirmed from a real response.

Treat Analytics as a label with a specific job. The tag used for measurement. The draw is GA4, Meta Pixel, or Plausible. A missing tag on the live page can still show up here.

The CDN line is worth a full stop. The network in front of the origin. The draw is Cloudflare, Fastly, or Vercel Edge Network. CDN claims need headers or DNS, not this card.

A second click can change WordPress into Shopify. The site did not replatform. Confirm a stack from the live HTML, cookies, and headers, or ask the owner.

If you remember one sequence from Technology Detector, remember the fields in the order they change a decision. CMS matters because The content system, such as WordPress or Shopify. In practice, The sample draws WordPress 6.4.2, Shopify, or Contentful. The mistake to avoid is this: A custom site can still be labeled WordPress. Framework matters because The language or UI framework. In practice, The draw is PHP 8.1, Ruby on Rails, or Next.js 14.1. The mistake to avoid is this: Those versions are not read from a header. Server matters because The software that answered. In practice, The draw is Nginx 1.24.0, Cloudflare Server, or Vercel. The mistake to avoid is this: Server software has to be confirmed from a real response. Analytics matters because The tag used for measurement. In practice, The draw is GA4, Meta Pixel, or Plausible. The mistake to avoid is this: A missing tag on the live page can still show up here. CDN matters because The network in front of the origin. In practice, The draw is Cloudflare, Fastly, or Vercel Edge Network. The mistake to avoid is this: CDN claims need headers or DNS, not this card. After that, the checks are simple. You ran the detector twice. You did not quote WordPress 6.4.2 as fact. You did not plan a migration from one draw. Analytics and CDN labels stayed out of the contract. Live HTML or headers are the source for the stack.

The worked example for Technology Detector, read as one scene, is this. Type https://example.com. You might see WordPress 6.4.2, PHP 8.1, Nginx 1.24.0, GA4, and Cloudflare. Run it again and you might see Shopify and Fastly. example.com did not change platforms. View the live page source and response headers before you write a migration plan.

Final notes for Technology Detector, written as decisions rather than as a table. When CMS is in front of you, decide using this: The content system, such as WordPress or Shopify. A custom site can still be labeled WordPress. When Framework is in front of you, decide using this: The language or UI framework. Those versions are not read from a header. When Server is in front of you, decide using this: The software that answered. Server software has to be confirmed from a real response. When Analytics is in front of you, decide using this: The tag used for measurement. A missing tag on the live page can still show up here. When CDN is in front of you, decide using this: The network in front of the origin. CDN claims need headers or DNS, not this card. Then apply the checks without skipping one. You ran the detector twice. You did not quote WordPress 6.4.2 as fact. You did not plan a migration from one draw. Analytics and CDN labels stayed out of the contract. Live HTML or headers are the source for the stack.

Keep Technology Detector as this step only. When the job moves on, the HTML Source Viewer is the next page: HTML Source Viewer asks for a URL and then shows a block of HTML labeled as that site’s source. The Header Checker covers a different piece of the same work: Header Checker asks for a URL and lists response headers, including a few security header names.