Public signal checker
Website Technology Checker
Use this checker to understand which visible technologies a website may use. It reads public page signals only and turns them into neutral evidence, not a vendor inventory.
The check uses public live signals and does not make a security, malware, fraud or legal verdict.
Run a public signal check
- HTTP
- DNS
- TLS
- RDAP
- Archive
What this checker analyzes
- CMS and shop hints such as WordPress, WooCommerce, Shopify, Wix, Squarespace and Webflow.
- Frontend framework hints such as Next.js, Nuxt, Astro, React, Vue, Angular and Vite.
- Payment and consent tool signatures when they are visible in the homepage HTML or response headers.
Why it matters
- Technology clues help agencies and site owners plan migrations, maintenance and dependency reviews.
- Visible platform markers can explain why certain headers, scripts or third-party services appear in the report.
What the results mean
- Detected means a strong public marker was visible.
- Likely or Possible means the signal should be treated as a lead for manual review.
- Unavailable means the source did not expose enough information or the live check failed.
Limits of this check
- SiteTraceKit does not execute JavaScript, log into websites or inspect private admin areas.
- A hidden or heavily customized technology stack may not leave reliable public markers.
- The result is not a software bill of materials or a security verdict.
What should also be reviewed manually?
Review notable values in the context of the actual website, its subpages and connected services. A homepage check cannot prove the complete configuration, legal position or security posture.
FAQ
Can this identify every technology on a website?
No. It only uses public signals from the homepage, response headers, DNS and visible resource URLs.
Why does a result say Possible instead of Detected?
Some markers can be shared by different tools. Possible keeps the wording cautious until a human confirms the context.