// per-site profile
what detects you on stackedqueries.github.io
stackedqueries.github.io is defended by a detection vendor being profiled. below: the layers it enforces and the tool config the matrix predicts survives it.
enforced detection layers
not yet measured: enforced layers on stackedqueries.github.io
this entry is in the catalog but carries no scored capability yet. the matrix updates as the benchmark self-heals, so check back or see the capability matrix.
notes
The xray-scanner client probe page driven headless via ?json for fingerprint/coherence/stealthScore (the collectViaXray adapter, WP6.5). NO expectedVendor, deliberately: this is our own page on GitHub Pages and it is fronted by no bot defense whatsoever. It previously claimed `browserscan`, which is not a vendor the catalog defines (it is another detector target), a dangling reference that stamped a false `vendor:browserscan` marker onto every run and made this page look defended. Found by the KAN-206 canary-target validation. SIGNALS (WP3.10, verified live 2026-07-24): the ?json view renders the full RunResult into a single <pre>, so every field is one jsonPath away. stealthScore/coherenceScore are 0-100; detectabilityRaw is unbounded (lower is better). fingerprint/fpIdLong are the identity-stability inputs, K trials yielding K distinct values means a fresh identity per launch, 1 means a stable one. leaks/hardFails are stored whole (arrays of {key,category,verdict,severity,botDetectionTell,layer}); splitting them per-leak would need `each`, which iterates DOM nodes and cannot iterate inside JSON.
questions
- what detects you on stackedqueries.github.io?
- stackedqueries.github.io's detection vendor is being profiled.
- which config survives stackedqueries.github.io?
- no enforced layers are scored yet, so no prediction is available.