Running a detection
Click Refresh to run a detection. Each detection spends a research lookup, so it asks first: the confirm says it detects the site’s technologies again, that it uses 1 research lookup, and how many you have left this month. Click Refresh in the confirm to start. 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 reads47 technologies detected on example.com, followed by one card per category — CDN, Web servers, JavaScript frameworks and so on, as the data source classifies them.
Each technology in a card shows its name, and beneath it the broader type of technology the category belongs to.
The data source reports which technologies are present, not their versions or how confident each detection is, so neither is shown.
What it’s useful for
On your own domain, it’s a quick inventory: an unexpected analytics script, a CMS you thought you’d migrated away from, or a tag left over from an old vendor. 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.