Vendor dashboards need an account and show aggregate cache hit ratio. CacheProbe is an external, URL-level check that explains why a specific path is MISS, DYNAMIC, or BYPASS — and how to fix the cache key or headers.

You can. CacheProbe discovers a same-origin URL sample (robots, sitemaps, shallow crawl), then systematizes sequential Age checks, clean vs tracking-param URLs, multi-CDN status normalization, and a best-practice checklist into a report you can paste into a ticket.

Lighthouse is lab and client focused. It does not detect query-parameter fragmentation across CDN cache keys or normalize cf-cache-status, X-Cache, and x-vercel-cache into one multi-URL report.

Phase 1 is low-volume sequential diagnostic GETs only, after ownership verification, with hard page/asset/GET budgets. There is no stepped load generation in this release. Any capacity module later is gated and explicit. See the bot identity page for User-Agent details and rate posture.

No. Every finding includes evidence (status, Age, URLs, headers). Edge Health is transparent deductions from 100 — or marked Inconclusive when data is weak. No invented hit ratios.