Loading...

Website Tech Stack Detector

Discover technologies exposed by public HTML and HTTP headers, with evidence for each match.

Public HTTP/HTTPS page only. HTTPS is added for a bare domain. Up to 2 MiB of HTML.

Inspects one server-fetched page. JavaScript is not executed and linked assets are not downloaded. Hidden technologies may not be detected.
Fetching the public page and inspecting technology signals…
Enter a website URL to inspect its publicly visible technology signals.
Technologies detected
Categories detected
With explicit declarations

Technology report

Requested URL
Final URL

Explicit declarations and characteristic patterns are signals, not proof. Versions are reported by the page. Cookie values and raw HTML are omitted.

This page reached an inspection limit. Only the first 20,000 elements and first 128 KiB of each inline script were examined; some signals may be missing.

Detection applies to the final returned HTML page. A missing technology or version is not evidence of absence.
TechnologyCategoryReported versionSignal strengthEvidence

Follow VuiZ.Net on Google Search

Add VuiZ.Net as a preferred source on Google to find your favorite tools more easily.

  • Find your tools again
  • Discover new utilities
  • Support VuiZ.Net
Follow

Find the technologies a public web page reveals

Web pages can reveal their software through HTTP headers, generator metadata, characteristic markup and script, stylesheet or iframe references. This detector compares those signals with a built-in set of rules and lists the evidence behind each match.

Submit a public HTTP or HTTPS URL to inspect one page from the VuiZ server. Results can include CMS and commerce platforms, frameworks, JavaScript libraries, UI libraries, analytics, web servers, CDN and hosting services. This is an observation of the returned page, not a complete inventory of its infrastructure.

Key features

  • Embedded services and browser SDKs. Recognize booking and form embeds such as Calendly, Typeform and Tally, video players, marketing tools and monitoring SDKs. Iframe URLs are inspected without opening their contents. Firebase, Supabase, Clerk or Auth0 SDK references show a browser integration, not proof of a database, authentication setup or the embedded page’s full stack.
  • More technology families. Recognize signals for site builders such as Framer and Tilda, documentation generators such as Docusaurus and VitePress, frameworks such as Qwik and Blazor, common UI and chart libraries, analytics, chat widgets, payment SDKs and CAPTCHA integrations. Known npm/CDN package paths and literal script-loader references are also inspected.
  • Evidence for each detection. See the header name, generator declaration, markup attribute or resource marker behind a match. Regular article text and ordinary hyperlinks are not treated as technology evidence.
  • Reported versions only. Versions come from explicit product headers, generator metadata or framework attributes such as Angular ng-version and Qwik q:version. CDN package versions, asset query parameters and build hashes are not treated as confirmed runtime versions; conflicting declarations are marked separately.
  • Filter the report. Search technology names or select a category to focus on CMS, frameworks, analytics, server software or other detected components.
  • Export a snapshot. Copy or download the full JSON report, including the requested and final URLs, timestamp, response status and detection evidence. Filters affect the table only.

How to detect a website tech stack

Inspect public signals and review the evidence before drawing conclusions.

  1. Enter a public page URL. Paste an HTTP or HTTPS URL, or enter a domain to use HTTPS. Use Sample fills the WordPress.org homepage. Private addresses, credentials in URLs and ports other than 80 or 443 are not accepted.
  2. Run detection. Click Detect Technologies. The server retrieves the page and follows up to three validated redirects, without running JavaScript or downloading linked resources.
  3. Review the matches. Check each technology, category, reported version, signal strength and evidence. Use the name and category filters to narrow the table.
  4. Save the report. Choose Copy JSON or Download JSON to save the full snapshot. Use Reset to clear results and enter another page.

Usage tips

  • Scan a representative public page. A blog, shop and application on the same domain can use different technologies.
  • Unknown versions are normal. A hidden version or absent signature does not mean the software is missing, outdated or vulnerable.
  • A CDN or reverse proxy can hide the origin server. A Cloudflare or hosting header does not reveal the complete backend architecture.
  • The URL is sent to VuiZ, and the target receives a server-side HTTP request. Avoid submitting URLs containing private tokens. Cookie values and raw page HTML are not included in the report.

Frequently asked questions

Matches are based on recognizable public signals. Explicit declarations are marked separately from characteristic resource or markup patterns. Headers can be changed, assets can be copied and signals can be spoofed, so even a strong match is evidence rather than independent verification.
No. Databases, internal services and hidden infrastructure generally cannot be identified from a single public response. The detector does not infer them from a CMS or frontend framework and does not perform a vulnerability scan.
Bundling, renamed assets, removed metadata, consent requirements and bot protection can hide signals. The detector does not execute JavaScript, crawl other pages or fetch external scripts and stylesheets. A technology loaded only after interaction may therefore be absent.
No. A referenced script shows an integration signal, not successful execution or data collection. The Google tag can serve several Google products, so gtag.js alone is not labeled as Google Analytics. Consent and runtime configuration are not evaluated.
Each check retrieves one page with up to three redirects, a 2 MiB response-body limit and a 15-second processing budget. At most 20,000 elements and the first 128 KiB of each inline script are inspected; partial inspection is flagged. Checks are limited to six per minute per client and one per target hostname every ten seconds. Slow DNS resolution can exceed the processing budget.