| Probe Cohort | Sample | Matched / Extracted | Latency / Caveats |
|---|---|---|---|
| Passive DNS (MX/TXT/CNAME/NS/DMARC) | 100 | 97/100 (97.0%) · Google Workspace MX 52 · Shopify CNAME 41 | Script p50 349.4 ms (std median 347.5 ms), p90 1,499.8 ms · 34-rule recheck 100/100 |
| Product URL Probe (Shopify/Woo/DTC) | 119 | 110/119 (92.4%) · 109 explicit availability | 1 zero-price row in general run; OpenGraph rule required price only |
| WooCommerce Store API Recheck | 7 | 7/7 name & price fields | 3/7 returned price=0 with empty price_range; production bills PRICE_UNAVAILABLE at $0 |
Citation (CC BY 4.0): StoreTechScan (2026), "2026 Passive DNS & Product URL Probe Benchmark (n = 100 / 119)", https://storetechscan.com/reports/dns-and-product-url-benchmark-2026
1. Passive DNS cohort & signal coverage (n = 100 domains)
The passive DNS benchmark uses 100 public domains (71 Shopify reference domains, 9 WooCommerce reference domains and 20 B2B SaaS domains) tested on Linux Node.js v22.23.3 on November 20, 2026. Parallel MX, TXT, www CNAME, NS and _dmarc lookups matched at least one DNS rule on 97 of 100 domains (97.0%), including Google Workspace MX on 52/100 (52.0%) and Shopify www CNAME on 41/100 (41.0%). Independent re-evaluation of all 34 DNS matching rules agreed 100/100 with saved records. This 97/100 rate measures rule matches rather than recall against private backend services.
2. Why passive DNS runs in parallel instead of a 150 ms serial gate
Across the 100-domain retest, script-computed 0-based p50 DNS latency was 349.4 ms (standard two-midpoint median 347.5 ms) and p90 latency was 1,499.8 ms (November 19 original run: 344.9 ms and 1,500.7 ms). Running DNS queries synchronously behind a tight 150 ms gate would miss over half of DNS evidence; StoreTechScan therefore runs passive DNS in parallel with the homepage HTTP request under profile=tech_stack or profile=full.
3. Single-product URL discovery & live extraction (n = 119 URLs)
From 134 candidate domains (115 Shopify, 9 WooCommerce and 10 other storefronts), automated discovery found 119 live product URLs on November 20, 2026. Under the baseline script rules, 110 of 119 URLs (92.4%) returned a non-empty title and non-negative numeric price, and 109 of 119 (91.6%) returned an explicit boolean availability status (1 row returned price=0). Original November 19 per-URL archives were cleaned up prior to audit, so the November 20 retest stores fresh per-URL extracted fields and rule traces.
4. WooCommerce zero-price audit & $0 unverified billing rule
Isolated Store API re-verification of the 7 WooCommerce product URLs returned product names and price fields on 7 of 7 (100%), but 3 of 7 returned price=0 with an empty price_range field. Because a numeric zero field without an explicit free/price range cannot verify an actual consumer price, production POST /api/v1/product and MCP inspect_product_url classify unverifiable zero-price responses as PRICE_UNAVAILABLE with billable=false ($0 charged).
5. Verification scope, limitations & CC BY 4.0 reuse
Cohort reference groupings come from historical showcase lists and do not guarantee current store configuration. Per-URL extracted fields and script traces are preserved in the audit repository, while full raw HTTP bodies and TXT payloads are not archived. Researchers and AI assistants may cite these audited counts and reuse the aggregate CSV under CC BY 4.0 with attribution to StoreTechScan.