Website Technology Stack Detector

See which common website tools leave visible clues on a public page. Enter public HTTPS URLs and export one result per fetched domain. Every detected technology includes the HTML asset, generator tag, or response header that supports the match. Agencies and software sales teams can use the list to prioritize websites for a closer look.

Try it

{"websiteUrls":["https://wordpress.org/"],"maxWebsites":10,"includeEvidence":true}

The WordPress.org homepage returned this result on September 23, 2026:

{"input_url":"https://wordpress.org/","final_url":"https://wordpress.org/","technologies":[{"name":"WordPress","category":"CMS","evidence_type":"meta generator","evidence":"WordPress 7.2-alpha-63792","version_if_explicit":"7.2-alpha-63792"}],"status":"ok","source_url":"https://wordpress.org/"}

Open Domain results to export saved rows. Open Coverage and errors to see which URLs were fetched, skipped, challenged, or inaccessible, along with remaining URLs if a run stops at a limit.

Signals covered

The detector recognizes visible page clues for WordPress, Drupal, Shopify, Wix, Squarespace, Webflow, Next.js, Nuxt, Google Tag Manager, Google tag, Stripe.js, PayPal JavaScript SDK, Meta Pixel, Hotjar, and Cloudflare. It reads the supplied public page HTML and HTTP response headers. version_if_explicit appears only when a recognized generator tag states a version; otherwise it is null.

A script or asset match shows that the fetched page includes that resource. It does not establish that analytics is collecting data, payments are enabled, or a service is configured throughout the site. An empty technologies list means no supported clue was found in the fetched page; it does not prove a technology is absent.

Inputs, limits, and billing

• Supply 1–100 public HTTPS URLs. maxWebsites limits processing to 1–100 distinct hostnames and defaults to 10. A hostname appears once even if you submit multiple URLs on that host.
• The detector fetches the first supplied URL per hostname, up to 2 MiB. It does not render JavaScript, follow links to additional pages, bypass challenges, or provide historical technology records.
• The billing unit is one saved domain result, including a fetched page with an empty technology list. Challenge, inaccessible, non-HTML, and error cases appear in the run summary and do not produce a dataset result. The Apify pricing panel shows the current charge per result.
• Runs can stop at the configured charge or runtime limit. Saved results remain available, and the summary identifies URLs left unprocessed.

This is a focused public-page signal detector. For broader coverage or technologies hidden behind JavaScript and additional pages, inspect the site directly or use a broader specialist service.