Website Technology Detector

Detect observable website technologies from public HTML and response headers. Categories include CMS, ecommerce, web frameworks, analytics, tag managers, CDN, hosting, payments, support, monitoring, and web servers.

Evidence, not black boxes

Every detection includes a category, confidence, and evidence source such as html_signature or a specific response header. Full response headers are excluded by default. Detection is best-effort: server-side or deliberately hidden technologies may not be observable.

The Actor blocks localhost, private IPs, private DNS answers, embedded credentials, and unsafe redirects. Provide urls, a deterministic maxWebsites, and timeout settings.

Quick start

{
  "urls": [
    "https://apify.com"
  ],
  "maxWebsites": 10,
  "timeoutSecs": 20,
  "includeHeaders": false
}

Run the public example first, then provide a bounded list of company websites. Keep includeHeaders off unless your downstream process truly needs the filtered header evidence.

Output

Each website row contains canonical and final URLs, fetch status, title, detected technologies grouped by category, confidence, evidence, counts, and an explicit error when a public page cannot be analyzed. The run summary records successes, failures, detections, and budget status.

Useful workflows include sales qualification, market research, migration planning, integration compatibility checks, public technology inventories, and routing leads by CMS, ecommerce platform, analytics, or payments provider.

API and automation

curl -X POST \
  "https://api.apify.com/v2/acts/gifted_wagon~website-technology-detector/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"urls":["https://apify.com"],"maxWebsites":1}'

In n8n or Make, map website URLs into bounded batches, filter detections by category and confidence, and retain evidence with every downstream record.

Pricing

The primary website-analyzed event starts at $0.0015 per successfully analyzed website. Only successful rows are charged; failed websites and the OUTPUT summary are uncharged. A small Actor-start event covers startup.

Responsible use

Use technology signals for lawful research, compatibility, sales qualification, and security inventory. Do not treat a detection as authorization to probe, exploit, or bypass a website.

FAQ and limitations

• Is detection guaranteed? No. Server-side, proxied, removed, or deliberately hidden technologies may not be observable.
• Does it scan for vulnerabilities? No. It reads public HTML and response signals; it is not a penetration-testing tool.
• Why include confidence and evidence? They make every detection reviewable instead of presenting a black-box claim.
• Can it access private networks? No. Local and private destinations and unsafe redirects are blocked.