Evidence-based public inspection
Website Technology Detector
Inspect public headers and HTML markers for supported website technologies and see the evidence behind every finding.
Only public HTTP(S) URLs are allowed. Private, loopback, link-local, and metadata destinations are blocked and every redirect destination is revalidated.
How to use the website technology detector
- STEP 1Enter a public HTTP or HTTPS URL.
- STEP 2Fetch up to ten safe redirect hops and inspect the final HTML.
- STEP 3Review evidence and export the report as JSON.
About this tool
Follow a safe public redirect chain and match response evidence against supported CMS, framework, CDN, analytics, and builder signatures.
Detection is signature-based and intentionally does not infer technologies without observable evidence.
Only the first 1 MB of final HTML is inspected to bound resource use.
Frequently asked questions
How are technologies detected?
The inspector checks response headers, generator metadata, asset URLs, and distinctive public HTML markers against a documented signature set.
Does no result mean no technology is used?
No. Sites can hide, rename, proxy, bundle, or remove signatures, and the detector intentionally avoids unsupported guesses.
Can I scan private or local systems?
No. Loopback, private, link-local, metadata, and other unsafe destinations are blocked, including redirect destinations.