Technology Stack Detector
Short answer
Detect the CMS, e-commerce platform, frameworks, hosting, analytics and marketing tools a website uses, grouped by category, and whether it uses a CDN.
What it does not do: It recognises technologies by known signatures in the HTML, headers and IP ranges, so bundled or hidden tools and sites behind a custom proxy may go undetected.
What It Does
Detects the technologies behind a URL — CMS, e-commerce platform, JavaScript frameworks and libraries, hosting, analytics, monitoring, marketing tools and chat widgets — from its HTML and response headers, and groups them by category. It also checks whether the site is served through a content delivery network (CDN).
Why It Matters
Knowing what a site runs on helps with competitor research, sales prospecting and migration planning — a Shopify store and a custom build call for different strategies. The CDN check shows whether the site is delivered from servers close to its visitors.
How It Works
-
Enter the URL and click Detect
-
We fetch the page and its response headers
-
Match the page against our technology signatures and look for CDN markers
-
Return the technologies by category and whether a CDN is in use
Sample input + output
url: https://developer.mozilla.org/en-US/
Technologies found: 3 (categories: 1).
Technologies
Technologies detected: 3 · Categories found: 1 · Signatures checked: 67
By category: Framework & libraries 3
Detected technologies:
Twitter Cards — Framework & libraries
Schema.org — Framework & libraries
PWA — Framework & libraries
Content delivery network (CDN)
This site delivers its content through Fastly.
CDN detected: Yes · Provider: Fastly
Detection method: Response header
Resolved IPs: 4 (151.101.1.91, 151.101.65.91, 151.101.129.91)
CDN in use OK How to read the result
- Two parts, no score
- The report has a technologies part and a CDN part. Neither is scored: finding few technologies, or no CDN, is information about the site, not a failed check. The headline gives the totals (3 technologies in 1 category in the sample, run on the MDN home page).
- Technologies detected (3) · Signatures checked (67)
- We compare the page's HTML, meta tags and some response headers with 67 known signatures. "Signatures checked" is how many technologies we can recognise, not how many we found. A framework compiled into anonymous script files leaves no signature, so a short list does not mean the site uses little.
- By category: Framework & libraries
- Categories are CMS, e-commerce, framework & libraries, hosting & CDN, analytics, monitoring, marketing, and chat & UX. Framework & libraries also holds markup the page declares, such as Open Graph, Twitter Cards and Schema.org. "PWA" means the page links a web app manifest; it does not test whether the site can be installed or works offline.
- Detected technologies
- Each line means the HTML or headers contain one marker typical of that tool: a script address, a generator meta tag, a class prefix or a header. One marker is enough, and some are broad, so a page that only mentions a product's name can match it. Treat the list as leads to confirm in the page source, not as proof.
- CDN detected (Yes) · Provider (Fastly) · Detection method
- A provider is recognised by its own response header (here Fastly's, and also those of CloudFront, Akamai, Vercel and Netlify) or, for one provider, by the site's addresses falling in its published ranges. Asset files on hosts such as cdn. or static. are listed under the result when the page loads any; the sample has none.
- Resolved IPs (4)
- The IPv4 addresses the domain resolved to when we checked; up to three are shown. Several addresses are normal for a CDN. A site behind a CDN we have no signature for, or behind its own proxy, shows "No" even though it uses one.
Who Uses This
-
Sales Engineer
Before a call, check the prospect's stack to know which integrations matter.
-
Agency Strategist
Review competitors' sites to see which platforms they build on.
-
Migration Lead
Confirm the current platform, tools and CDN before recommending a migration.
Common problems and how to fix them
-
The site could not be reached
Check that the address is public and not behind a login. Firewalls and bot protection sometimes refuse automated requests; our requests identify themselves as RankProofBot, so you can allow that user agent if you want the check to work.
-
A technology you use is missing
We read the HTML as the server sends it, so a tool that a tag manager or another script adds after the page loads is invisible here, as is code bundled under generic file names. Look for it in the page source; if it is not there, the check cannot see it either.
-
You would rather not advertise your stack
Remove the generator meta tag, version numbers in asset addresses and headers such as X-Powered-By. It makes the site harder to fingerprint but not safer by itself: keeping the software updated is what protects it.
<!-- remove from the template --> <meta name="generator" content="WordPress 6.6"> // WordPress (functions.php) remove_action('wp_head', 'wp_generator'); -
No CDN detected
For visitors far from your server, a CDN serves cached copies from nearby locations. Many hosts include one that you switch on in their settings. Then cache static files with long Cache-Control lifetimes, using file names that change with every new version.
# nginx: versioned static files (app.3f9a1c.css), cached for a year location ~* \.(css|js|woff2|svg|png|webp)$ { add_header Cache-Control "public, max-age=31536000, immutable"; } -
A CDN you use shows as "No"
We recognise six providers; behind another CDN or your own proxy the check cannot tell. Open the browser's developer tools, reload the page and look in the Network tab for the provider's cache headers on the main document.
Frequently Asked Questions
- How accurate is the detection?
- A detection fires when the page matches a known signature in its HTML, meta tags or response headers. There is no confidence percentage — a match is a match, though some signatures are more reliable than others.
- How is the CDN detected?
- From CDN-specific response headers and from the site's IP addresses, checked against a provider's published address ranges. A site behind a custom proxy may not be recognized.
- Can sites hide their stack?
- Partly. Removing headers hides the server type, and bundled JavaScript makes frameworks harder to spot. Most sites are still detectable through markup, asset paths and response headers.
- What categories are detected?
- CMS, e-commerce platforms, frameworks and libraries, hosting and CDN, analytics, monitoring, marketing tools, and chat and UX widgets.
Sources
The documentation this tool and the explanations on this page are based on.
- <meta name> HTML attribute — MDN Web Docs
- Web application manifest — MDN Web Docs
- CDN — MDN Web Docs
- Cache-Control header — MDN Web Docs