Website Technology Detector

See what a website is built with: CMS, framework, web server, CDN, hosting, analytics, payments and more. One page request per site and no browser, so 1,000 sites take minutes. Every rule comes from the vendor's own documentation.

What it does

• One request per site: robots.txt is read first (once per site) and obeyed 1. Then the page is fetched with GET, following redirects. Headers, cookie names, <meta name="generator">, script and stylesheet URLs, and page markup are matched against 45 technologies.
• Evidence you can check:
  • matchedBy names the kind of signal, for example header server or meta generator;
  • documentation links the vendor page the rule was written from;
  • versions are given where the signal carries one (nginx/1.27.0 gives 1.27.0).
• Clean-room rules: written from vendor documentation only; no third-party fingerprint database. A script re-checks every cited quote live.
• No personal data: the output never contains header values, cookie values, tracking IDs or page text, only technology names.
• Safety: only http and https. Private, loopback, link-local and cloud metadata addresses are refused 2, including after DNS and on every redirect.

Quick start

The prefilled input checks two GOV.UK sites:

{
  "urls": [
    "https://www.gov.uk/",
    "https://www.nationalarchives.gov.uk/"
  ]
}

The first row, from the run on 4 October 2026:

{
  "index": 0,
  "url": "https://www.gov.uk/",
  "finalUrl": "https://www.gov.uk/",
  "status": 200,
  "technologies": [
    {
      "name": "Fastly",
      "category": "CDN",
      "version": null,
      "matchedBy": [
        "header x-served-by"
      ],
      "documentation": "https://www.fastly.com/documentation/reference/http/http-headers/X-Served-By/"
    },
    {
      "name": "GOV.UK Frontend",
      "category": "Design system",
      "version": null,
      "matchedBy": [
        "page HTML"
      ],
      "documentation": "https://design-system.service.gov.uk/get-started/production/"
    },
    {
      "name": "nginx",
      "category": "Web server",
      "version": null,
      "matchedBy": [
        "header server"
      ],
      "documentation": "https://nginx.org/en/docs/http/ngx_http_core_module.html"
    }
  ],
  "categories": [
    "CDN",
    "Design system",
    "Web server"
  ],
  "technologyCount": 3,
  "error": null
}

Input

Field	Default	Meaning
urls	(required)	Sites or page URLs, up to 1,000; example.org means https://example.org/
timeoutSecs	20	Per site
maxConcurrency	5	Sites at once (1–10)

Output

One row per site, with index giving its position in urls.

Field	Meaning
technologies	[{name, category, version, matchedBy, documentation}]
categories, technologyCount	Summary
finalUrl, status	After redirects
error	Why a site couldn't be checked (robots.txt, timeout, HTTP error, blocked address)

What it recognises

• Advertising: Google AdSense, Google Publisher Tag, Meta Pixel
• Analytics: Cloudflare Web Analytics, Google tag (gtag.js), Matomo
• CDN: Amazon CloudFront, Azure Front Door, Cloudflare, Fastly
• CMS: Ghost, WordPress
• Consent management: Cookiebot
• Design system: GOV.UK Frontend
• E-commerce: Shopify
• Error monitoring: Sentry
• Fonts: Adobe Fonts, Font Awesome, Google Fonts
• Hosting: Vercel
• JavaScript framework: Gatsby, Next.js
• JavaScript library: jQuery
• Live chat: Intercom
• Maps: Google Maps JavaScript API, Leaflet, Mapbox GL JS
• Marketing: HubSpot
• Payments: PayPal JavaScript SDK, Stripe.js
• Programming language: PHP
• Security: Cloudflare Turnstile, Google reCAPTCHA, hCaptcha
• Static site generator: Astro, Hugo
• Tag manager: Google Tag Manager
• UI framework: Bootstrap, Tailwind CSS (browser build)
• Video: YouTube embedded player
• Web framework: ASP.NET, Express
• Web server: Apache HTTP Server, Kestrel, nginx

Use from code

curl -X POST "https://api.apify.com/v2/acts/landlordtools~website-tech-detector/run-sync-get-dataset-items?token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"urls": ["https://www.gov.uk/"]}'

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: 'YOUR_API_TOKEN' });
const run = await client.actor('landlordtools/website-tech-detector').call({ urls: ['example.org'] });
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items[0].technologies.map((t) => t.name));

Use with AI agents

Agents can call it through Apify's MCP server (https://mcp.apify.com).

Accuracy

Tested on 4 October 2026 against sites the vendors themselves list as built with their product. The declared technology was found on 79 of 98 sites that answered (Astro 71 of 84, Next.js 3 of 4, Gatsby 5 of 10). The details are in tests/benchmark/.

Limits

• One page, no JavaScript: technologies added only after the page loads in a browser aren't seen.
• Sites can hide or change signals, so a missing technology isn't proof it's absent.
• Sites whose robots.txt disallows the page (or returns a server error) aren't checked.

Integrations

Power Platform, OpenAPI, Excel and Google Sheets files are in integrations/README.md. Apify's Zapier, Make and n8n apps work too.

Pricing

Pay per event: $4 per 1,000 results ($0.004 each), plus Apify's minimal start fee. A result is one website checked. Sites that can't be checked are free, and the run stops at your spending limit 4.

Related Actors

• Sitemap URL Extractor: list every page on a site.
• Link and Citation Checker: check links and quotes.

Sources

1. RFC 9309: Robots Exclusion Protocol. Accessed 4 October 2026.
2. IANA IPv4 Special-Purpose Address Registry. Accessed 4 October 2026.
3. IANA IPv6 Special-Purpose Address Registry. Accessed 4 October 2026.
4. Apify: pay-per-event pricing. Accessed 4 October 2026.