Website Technology Detector (Wappalyzer Alternative)

Website Technology Detector finds out what any website is built with. Enter a list of websites and get each site's tech stack: CMS, ecommerce platform, analytics and advertising tools, payment providers, CDN, JavaScript frameworks, web server, and more, with versions where the site reveals them. It is a bulk Wappalyzer alternative for lead generation, sales research, and competitor analysis.

What can this tool do?

• Detect more than 6,700 technologies from the open-source Wappalyzer fingerprint database, plus our own maintained rules for modern frameworks and payment providers (Next.js app router, Nuxt, VitePress, Creem, Lemon Squeezy, Paddle, Stripe Checkout, Polar, Clerk, Framer).
• Identify the CMS (WordPress, Drupal, Webflow, Wix …) and ecommerce platform (Shopify, WooCommerce, Magento …).
• List analytics, advertising, tag manager, payment, live chat, and marketing tools.
• Report versions when the website exposes them (for example WordPress 7.2).
• Read HTTP headers, cookies, meta tags, script URLs, page HTML, the site's own JavaScript files, and DNS records (email provider and DNS host).
• Show the evidence behind every detection, and keep weak signals (like a host that only appears in a Content-Security-Policy header) out of the summary columns.
• Fill ready-made summary columns (cms, ecommerce, cdn, analytics …) for easy filtering in Excel or Google Sheets.
• Analyse thousands of websites in one run; sites that fail to load or block the request are listed with the reason and not charged.

What data does it return?

One row per website. Example values from a real run of the default input:

Field	wordpress.org	shopify.com	apify.com
url	https://wordpress.org/	https://www.shopify.com/	https://apify.com/
finalUrl	https://wordpress.org/	https://www.shopify.com/	https://apify.com/
statusCode	200	200	200
cms	WordPress	null	null
ecommerce	null	Shopify	null
cdn	null	Cloudflare	Amazon CloudFront
frameworks	[]	["Tailwind CSS"]	["Next.js", "React", "styled-components"]
analytics	[]	[]	[]
advertising	[]	[]	[]
payment	[]	[]	[]
technologyNames	["Google Font API", "Google Tag Manager", "Gutenberg", "HSTS", "MySQL", "Nginx", "Open Graph", "PHP", …] (13)	["Cart Functionality", "Cloudflare", "Google Workspace", "HSTS", "HTTP/3", "Open Graph", "Priority Hints", "Shopify", …] (9)	["Amazon CloudFront", "Amazon Route 53", "Amazon Web Services", "Google Workspace", "HSTS", "HTTP/3", "Next.js", "Open Graph", …] (13)
technologies	[{"name": "WordPress", "categories": ["CMS", "Blogs"], "version": "7.2", "confidence": 100, "evidence": ["dom", "header: link", "html", "inline script", "meta: generator", "script URL"]}, …]	[{"name": "Cloudflare", "categories": ["CDN"], "version": null, "confidence": 100, "evidence": ["header: cf-cache-status", "header: cf-ray", "header: server"]}, …]	[{"name": "Algolia", "categories": ["Search engines"], "version": null, "confidence": 25, "evidence": ["header: content-security-policy"]}, …]
error	null	null	null
detectedAt	2026-09-24T20:16:35.063Z	2026-09-24T20:16:35.063Z	2026-09-24T20:16:35.063Z

Each entry in technologies also has evidence, for example ["script URL", "header: x-nextjs-prerender"] or ["implied by Next.js"]. Summary columns and technologyNames only include confident detections (confidence 50 or more).

Every row has the same fields, so CSV and Excel exports stay tidy. The Technologies with versions view shows one line per technology.

How to use it

1. Enter websites, one per line (domains or full URLs).
2. Optionally pick categories to keep, for example only Ecommerce and Payment processors.
3. Click Start, then download the results as CSV, Excel, or JSON, or read them through the API.

Common uses

• Build lead lists: find every Shopify or WooCommerce store in a list of domains.
• Sales research: see which analytics, chat, or payment tools a prospect already uses.
• Competitor and market analysis: compare the stacks of the top sites in a niche.
• Agency audits: check a client's CMS and plugin versions before a project.

Pricing

Pay per website: $3.00 per 1,000 websites, plus $0.005 per run. Websites that cannot be loaded or that block the request are listed with the reason and not charged. Set a maximum cost per run in the run options.

Use it through the API, AI agents, and integrations

Call it from your code with the Apify API, schedule it, or connect it to Make, Zapier, n8n, or an AI agent through Apify's MCP server.

Is it legal?

This tool loads each website's public home page once, the way a browser does, and reads technical signals such as headers and script URLs. It does not log in, bypass access controls, or collect personal information. Technology fingerprints come from the open-source webappanalyzer project (GPL-3.0). You are responsible for how you use the data.

FAQ

Why is a technology I know about missing? The tool reads the page without running JavaScript, so tools that only appear after scripts run, or that load on inner pages, can be missed. Enter the exact page you care about (for example a checkout or blog page) to analyse it directly.

A website returned HTTP 403. What can I do? Some websites block cloud servers. The row still shows what the block page reveals (often the CDN or firewall), and it is not charged. Turn on the Proxy option and run those sites again; this helps for some sites, while heavily protected ones may still refuse automated requests.

Why is a technology in technologies but not in the summary columns? Some signals are weak. For example, a Content-Security-Policy header often still lists services a site no longer uses (like *.paypal.com), so a technology seen only there gets confidence 25 and the evidence header: content-security-policy, and it is left out of payment, analytics and the other summary columns.

How accurate is it? On our test set of 27 websites with known stacks (Next.js, Nuxt, Astro, SvelteKit, WordPress, Shopify, Wix, Webflow, Framer, Laravel, Hugo and more), the latest cloud run found 46 of 46 expected technologies with 0 false positives out of 54 checks; 1 site blocked the request with a bot check. Real-world sites vary, so treat results as strong hints, not proof.

What does confidence mean? 100 means a definite signal was found. Lower values mean a weaker signal, for example a technology implied by another one.

Feedback

Found a bug, a wrong detection, or need a field added? Open an issue on the Issues tab. We usually respond within 24 hours.