Enter a website URL.
How this tool works
Fetching. Your browser sends the URL to a CORS proxy (cors-anywhere.com, crossorigin.me, or allorigins.win), which fetches the target page’s HTML. This avoids same-origin restrictions. If one proxy fails, the tool tries another. On Cloudflare errors (e.g. 526), it retries over HTTP.
Detection. The HTML is parsed client-side. Technologies are inferred from:
- Signatures — regex patterns for known tech (WordPress, React, Shopify, Google Analytics, etc.)
- Domain matching — script, stylesheet, and iframe hostnames (e.g. googletagmanager.com → Google Tag Manager)
- CDN URLs — libraries and versions from jsDelivr, unpkg, cdnjs, and filename patterns (e.g. jquery-3.6.0.min.js)
Analysis. The tool also extracts page info, meta tags, forms, headings, JSON-LD, video embeds, fonts, render-blocking scripts, accessibility hints, and third-party stats — all from the HTML returned by the proxy.
Limitations. HTTP headers (Server, X-Powered-By, cookies, security headers) are not available because the proxy returns the HTML body. Other resources (robots.txt, sitemap.xml, manifest.json, humans.txt, security.txt, ads.txt) require extra HTTP requests and are not fetched by this client-side implementation.