Tech Stack & Buying Signal Enrichment
Pricing
from $10.00 / 1,000 domain scanneds
Detect what any website is built with: CMS, ecommerce, payments, analytics, tag managers, CDN, hosting, ATS, email and JavaScript frameworks, with evidence for every detection. Get a vendor_change record when a site swaps a tool. Pay per domain scanned, no subscription.
Domains or URLs to analyse. Bare hosts (example.com), full URLs, IDN and ports are all accepted. Duplicates are removed.
[ "allbirds.com", "hubspot.com"]Alternative to the list above: paste domains separated by newlines, commas, semicolons or spaces. Merged with 'Domains'.
Public URL of a plain-text or CSV-first-column file, one domain per line. Fetched once at start-up (max 50 MB).
Hard cap on domains processed this run. 0 means no cap. A safety net for oversized inputs.
Parallel domain scans. 20 is a good default; raise for large lists on 2 GB or more of memory.
Per-HTTP-request timeout. A site that does not answer in time is cut off rather than holding up the run; DNS and TLS still run, and the row bills as domain_scanned if they detect anything, otherwise as domain_failed.
TXT / MX / NS / CNAME / SOA records. Free (no bandwidth) and the source of email-provider and SaaS-verification signals. Keep this on.
One extra TXT query for _dmarc.. 'This company publishes a DMARC policy' is a free signal that they run real, managed email. Needs DNS lookups to be on.
Certificate issuer, validity, SAN count, wildcard, TLS version. Free and useful for CDN/hosting attribution.
Two extra small requests per domain. Adds robots-based detections, sitemap hints and some ATS signals.
Approximate JavaScript-variable detections by searching inline script text, capped at 50 confidence and tagged as inlineJs evidence. Turn off for maximum precision.
Drop detections below this score. Set to 51 to exclude every inline-JS heuristic result.
Leave empty for the full stack. Filtering affects the output only; detection always runs in full so implied technologies stay correct.
[]Launch headless Chromium to evaluate real JavaScript globals, DOM selectors and XHR hosts. Detects client-rendered tools that HTML alone cannot see. Billed as domain_rendered on top of domain_scanned.
Parallel browser contexts. Each one needs about 1 GB of run memory on top of the first GB, so a run is capped at 1 render on 2 GB, 2 on 3 GB and 3 on 4 GB — a higher value here is clamped to what the run memory allows and the run log says so.
The browser's budget for one page: loading it and reading it, together. Separate from 'Request timeout', which bounds a single HTTP request — a browser loading a heavy page needs far longer than a plain fetch. A page that runs out stays on Tier 1 with renderSkipped: "render_failed" and nothing extra is charged. Heavy pages behind a proxy need 20–40 seconds.
Which bytes the browser refuses to download. 'default' blocks images, media and fonts — none of them carry a technology fingerprint, and they are most of a page's weight. 'aggressive' also blocks stylesheets, which is faster still but turns off stylesheet-based detections. 'none' downloads everything and is for debugging a render that looks wrong.
Compare each domain against your last scan and emit a vendor_change record when the stack differs. The first scan of a domain never produces a change.
Named key-value store holding your scan history. Use different names to keep separate tracking sets.
Named dataset that collects every vendor_change record, run after run — your change feed. It is created the first time a change is confirmed. This run's own dataset keeps exactly one row per domain, so the two never mix.
A technology must score at least this to count as added or removed. Higher than the output floor on purpose, so low-confidence noise never bills you for a change.
A technology must be seen in its new state this many scans in a row before it counts as a change and is billed. Ad-heavy sites load a different set of tags on every visit, and 2 is enough to tell that apart from a real move: the row shows the candidate under changes.pending meanwhile, and nothing is charged. Set to 1 to bill on the first scan that sees a difference.
Empty the snapshot store before this run starts. Every domain then looks like a first scan, so no vendor_change is emitted and nothing is billed for one. This is how you honour a deletion request or start a tracking set over.
Compute changes but leave the stored history untouched, and charge nothing. Useful for testing and for costing a large run before you pay for it.
Not needed for normal use: we fetch your own target domains and expect no anti-bot. Enable the default datacenter proxy if a target blocks Apify IPs, or supply your own proxy URLs. Residential proxies are NOT supported: this Actor's per-event price includes the bandwidth, and a run configured with the RESIDENTIAL group stops immediately with an explanation rather than scanning. Datacenter proxy usage is included in the event price and is never billed to you on top.
{ "useApifyProxy": false}