Website Technology Evidence API

Identify technology signals in public website HTML and headers with inspectable evidence. Small original ruleset, no paid lookup keys or browser.

Quick start

{
  "urls": [
    "https://www.python.org/"
  ]
}

Run the Actor; download the default dataset as JSON, CSV or Excel. Check the OUTPUT record for source failures and partial completion. Example sources can change or become unavailable.

Behavior and limitations

Examines only server-returned UTF-8 HTML asset URLs, generator meta tags, selected element IDs and HTTP headers. Each detected signal includes its matched evidence. The original bounded rule set covers WordPress, WooCommerce, Shopify, Next.js, jQuery, Bootstrap, Google Tag Manager, Google Analytics, Webflow, Wix, Squarespace, HubSpot, Drupal, Joomla, Hugo, Gatsby, Cloudflare, Vercel and Express. Names represent observed signatures, not proof of active use or ownership. False positives and missed tools are possible. No detection of hidden infrastructure, version inference, vulnerability scanning, active ports or JavaScript execution. An accessible HTML page with no matching signals returns an empty technologies list and is a billable observation. This is not a comprehensive BuiltWith/Wappalyzer replacement or a full website audit.

Each row includes its source URL and UTC observedAt timestamp. Successful sources continue when another source fails; OUTPUT.errors describes failures. If every source fails, the run fails with diagnostic output. Budget-limited output reports PARTIAL_BUDGET and complete=false. Nothing is inferred deleted or available from a missing row.

Pricing

$0.002 per successful website observation ($2 per 1,000), plus a $0.005 Actor-start event for the default 256 MB run. Failed sources incur no result event; the start event can still apply. Higher memory can increase the number of start events under Apify's rules. Check the effective Store pricing before running.

Access and resource bounds

Maximum 20 input targets, queried sequentially; five redirects; 2 MiB decoded response; approximately 100 seconds fetch budget. Public HTTP(S), ports 80/443 only. DNS addresses are validated and pinned per connection; embedded credentials and private addresses are rejected. Website HTML respects robots.txt: 404/410 allow access, disallow/block/unavailable policies produce source errors. Published RDAP API endpoints follow registry policies and notices; each domain query is paced with a one-second delay. They do not require a website robots endpoint. No proxy, bypass, external API key, paid upstream service or browser is used. Respect source terms and do not use registry data for spam or high-volume harvesting. Some registries or sites block automated clients; those targets are not bypassed.

API and automation

POST https://api.apify.com/v2/actors/soilair~website-technology-evidence-api/runs with your own Apify authorization header and the example JSON. Poll the run ID and retrieve its defaultDatasetId. Configure schedules in Apify Console if needed; this Actor does not create schedules or call other Actors.

Data and support

Inputs and outputs remain in your Apify run storage under the platform's retention settings. Requests go only to public input targets and redirects/robots policies, plus the official IANA bootstrap and its registry endpoints for RDAP. No separate analytics or customer-data endpoint is used. Do not supply secrets. Developed with AI assistance and verified using fixtures and public-source smoke runs; arbitrary sites are not guaranteed compatible. Send a run ID and expected behavior through the issue tab without credentials.