Website Technology Detector

Detect the full technology stack of any website — CMS, e-commerce platforms, payment processors, JavaScript frameworks, analytics tools, CDNs, security, and hosting infrastructure.

Powered by the Wappalyzer engine with enhanced payment processor detection that goes beyond standard Wappalyzer: scans /cart and /checkout pages, and uses custom regex patterns for Stripe, PayPal, Klarna, Apple Pay, Google Pay, Square, Afterpay, Shop Pay, and Braintree.

Key Features

• Bulk scanning — process hundreds or thousands of domains in one run
• Deep payment detection — scans /cart + /checkout pages, not just the homepage
• Anti-bot bypass — browser-like headers with Chrome/Safari UA rotation, HTTPS/HTTP fallback
• Structured output — technologies pre-categorized into columns (CMS, E-commerce, Payment, Analytics, CDN, Security, Hosting)
• Proxy support — works with Apify residential proxies for geo-restricted or protected sites
• Fast — concurrent scanning with configurable parallelism (up to 50 threads)

Use Cases

• Lead generation: Find e-commerce stores using specific payment processors (Stripe, PayPal, Klarna)
• Competitive analysis: See what technology stack your competitors use
• Market research: Analyze CMS and e-commerce platform market share across an industry
• Sales prospecting: Target businesses using outdated or specific technologies
• Security auditing: Identify technology versions for vulnerability assessment

Input

Parameter	Type	Default	Description
domains	array	required	List of domains to scan (e.g. ["shopify.com", "amazon.com"])
deepScan	boolean	true	Scan /cart and /checkout pages for payment processor detection
concurrency	integer	10	Parallel scans (1-50)
timeout	integer	15	Seconds per domain
proxyConfiguration	object	none	Apify proxy settings

Example Input

{
    "domains": [
        "shopify.com",
        "wordpress.org",
        "stripe.com",
        "amazon.com",
        "etsy.com"
    ],
    "deepScan": true,
    "concurrency": 10,
    "timeout": 15
}

Output

Each domain produces a structured result in the dataset:

{
    "url": "https://shopify.com",
    "domain": "shopify.com",
    "tech_count": 18,
    "technology_names": ["Cloudflare", "Google Analytics", "React", "Shopify", "Stripe", ...],
    "cms": "Shopify",
    "ecommerce": "Shopify",
    "payment_processors": "Stripe, Shop Pay",
    "js_frameworks": "React",
    "analytics": "Google Analytics, Segment",
    "cdn": "Cloudflare",
    "security": "HSTS, Cloudflare Bot Management",
    "hosting": "Cloudflare",
    "other": "HTTP/3, webpack",
    "technologies_by_category": {
        "Ecommerce": ["Shopify"],
        "Payment processors": ["Stripe", "Shop Pay"],
        "CDN": ["Cloudflare"],
        "...": "..."
    },
    "status": "success",
    "scanned_at": "2026-02-28T12:00:00+00:00"
}

Output Fields

Field	Description
domain	Normalized domain name
tech_count	Total number of detected technologies
cms	Content management systems (WordPress, Joomla, Drupal, etc.)
ecommerce	E-commerce platforms (Shopify, WooCommerce, Magento, etc.)
payment_processors	Payment systems (Stripe, PayPal, Klarna, Apple Pay, etc.)
js_frameworks	JavaScript frameworks and libraries (React, Vue, jQuery, etc.)
analytics	Analytics & marketing (Google Analytics, Hotjar, Segment, etc.)
cdn	Content delivery networks (Cloudflare, Fastly, Akamai, etc.)
security	Security features (HSTS, Cloudflare Bot Management, etc.)
hosting	Hosting infrastructure (AWS, Nginx, Apache, etc.)
other	Everything else (HTTP/3, fonts, miscellaneous)
technology_names	Full list of all detected technology names
technologies_by_category	Detailed breakdown by Wappalyzer category

How It Works

1. Fetches homepage with realistic browser headers (Chrome 124 User-Agent, Sec-Fetch headers)
2. If blocked, retries with Safari UA and HTTP fallback
3. Runs Wappalyzer analysis on HTML + HTTP headers
4. Applies custom regex patterns for payment processors often missed by standard Wappalyzer
5. If deep scan enabled: fetches /cart and /checkout pages for additional payment detection
6. Categorizes all technologies into structured columns for easy analysis

Tips

• Large lists (1000+ domains): Use concurrency 20-30 with Apify residential proxies for best speed and reliability
• Payment processor research: Keep deepScan enabled — it catches 30-40% more payment processors
• Export: Results are in Apify Dataset — export to CSV, JSON, or Excel with one click
• Filtering: Use the "Overview" tab to quickly see payment processors and CMS across all domains

Cost Estimation

This actor uses minimal compute resources (no browser needed — pure HTTP requests). Typical costs:

Domains	Estimated Time	Estimated Cost
100	~30 sec	~$0.01
1,000	~3 min	~$0.05
10,000	~20 min	~$0.40

Costs depend on Apify plan and proxy usage. Estimates based on concurrency=10 without proxies.

Limitations

• JavaScript-only sites: Some modern SPAs render content entirely in JavaScript. This actor analyzes static HTML + HTTP headers (same as Wappalyzer browser extension's initial scan). Headless browser rendering is not included to keep costs low and speed high.
• Anti-bot systems: Most sites work fine with the built-in UA rotation. For heavily protected sites, use Apify residential proxies.
• Rate limiting: Some hosting providers may rate-limit rapid requests. If you see many errors, reduce concurrency or add proxies.