Paste a URL and see the platform, theme, plugins, analytics, fonts, and hosting behind it, with the evidence for every claim.
Free, no login, no email. Nothing stored beyond a 24 hour cache. Markdown copy · API and MCP
Paste any URL
We fetch that one page the way a browser would, following redirects and reading the response headers along the way.
We match fingerprints
The raw HTML and headers are checked against known signals for platforms, themes, plugins, analytics tags, fonts, and hosting.
Read the evidence
Every finding shows the exact signal it matched and how sure we are. Copy the raw JSON if you want the result in a script.
We fetch the page once, the way a browser would, and read the raw HTML and the response headers. Platforms leave fingerprints there. Shopify injects a Shopify.theme object. Webflow stamps a data-wf-site attribute. Next.js embeds a __NEXT_DATA__ payload. Analytics snippets, font providers, and CDNs leave the same kind of trail. Every finding is listed with the exact signal it matched, so the result is something you can verify rather than something you have to trust.
Reading raw HTML has one real limitation, and you should know it before trusting any stack detector, including this one. Tech injected at runtime can be invisible. The usual culprit is Google Tag Manager: the HTML contains one GTM container, and the container loads half a dozen other tools after the page starts running. Those tools are not in the HTML, so a raw fetch cannot see them. When we find GTM we tell you, and that is your cue that the visible list may be the floor rather than the ceiling.
Every finding carries one of two labels. Detected means the signal is a fingerprint only that product produces. Likely means the signal is strong but shareable, like assets served from a CDN hostname a platform uses but does not own. Most detectors flatten those two into one confident list, which is how they end up claiming a site runs on a platform it merely borrows a CDN from. Keeping the labels separate, with the evidence printed next to each item, means the tool never overstates what it found. When a site blocks automated requests, we say that too, instead of reporting an empty stack as if it were a finding.
An agency inheriting a site wants to know what it is walking into before the kickoff call: the platform sets the migration cost, and the plugin list is a map of past decisions. A sales team wants to know whether a prospect runs on the platform their product integrates with. A marketer wants to see which analytics and pixels a competitor actually runs, not which ones they talk about. And checking your own site is worth a minute too, because the fingerprints we read are exactly what your site tells every visitor, every crawler, and every scraper about itself.
We fetch the page once, the same way a browser would, and read the raw HTML and the response headers. Platforms, plugins, analytics tools, and CDNs leave fingerprints in both. A data-wf-site attribute means Webflow. A Shopify.theme object means Shopify. A cf-ray header means Cloudflare. Every finding names the exact signal it matched, so you can check our work.
The same run this page does, as an HTTP endpoint and as the MCP tool detect_tech_stack. No account, no API key. Full reference.
curl -sS https://usesuperflow.ai/api/tools/tech-stack \
-H 'Content-Type: application/json' \
-d '{"url":"example.com"}'Returns { platformName, theme, apps[], fonts[], analytics[], hosting[], renderMode, url, status, fetchedAt }. 60 runs per hour per IP. Allow up to 30 seconds.
claude mcp add --transport http superflow https://usesuperflow.ai/api/mcpThen ask your agent for detect_tech_stack. Setup for Claude Desktop, Cursor and VS Code is on the reference page.
No login, no email, no ads. Same as this one.
Superflow agents check every page of every site you ship, on every change, against your own QA rules. They tell you when something breaks, changes, or quietly disappears.