CacheProbeCacheProbe bot & probe traffic
How to recognize CacheProbe requests, allowlist them if needed, and contact us about abuse.
https://cacheprobe.com/bot
What is this traffic?
CacheProbe runs production-safe, low-volume diagnostic GETs after domain ownership is verified. We discover same-origin URLs (robots.txt, sitemaps, shallow link crawl), sample HTML pages, and probe linked static assets. We do not run stepped load tests in Phase 1.
User-Agent strings
Audits: CacheProbe-Audit/1.0 (+https://cacheprobe.com/bot; test-id=<uuid>)
Ownership checks: CacheProbe-Verify/1.0 (+https://cacheprobe.com/bot)
Custom header
Audits also send X-CacheProbe-Test-ID: <uuid> matching the test-id in the User-Agent.
What we crawl
After ownership: robots.txt (we honor Disallow for CacheProbe/* and *), XML sitemaps, and a shallow same-origin HTML link crawl. We sample a capped set of pages and assets — not your entire site. No headless browser, no form posts, no cache purges.
Rate posture
Probes inside one audit are sequential (not parallel floods), with a hard GET budget per run. Free tier caps audits per account and per site per UTC day, with a short cooldown between runs and one concurrent audit per user.
Contact / abuse
Email support@cacheprobe.com with the request time, target hostname, and Cloudflare/ray or edge request id if available.
Blocking or allowlisting
You may block the CacheProbe User-Agent or challenge it at your WAF. Prefer allowlisting by UA or header if you want audits to succeed. Disallow paths in robots.txt for User-agent: * or CacheProbe. Do not treat us as a browser client.