DeployRadarBot
If you found DeployRadarBot in your server logs, this page explains exactly what it requested and why — and how to stop it.
What a single scan requests
| Request | Path | Why |
|---|---|---|
| 1 | /robots.txt | Read your crawler policy — the point of the tool |
| 1 | / | Baseline fetch with an ordinary browser user agent |
| 5 | / | One per AI crawler user agent, to detect edge-level blocking |
| 1 | / | Headless render, to compare against the raw HTML |
That is your robots.txt and your homepage — plus, during the render only, the JavaScript files your homepage itself loads. We have to fetch those: measuring what JavaScript adds to the page is the entire point of that check. Images, fonts, media and stylesheets are blocked.
Beyond that, no other pages are requested. We do not follow links, we do not crawl your sitemap, and we never submit forms. Requests are spaced 250ms apart.
Results are cached for 24 hours per domain, and each visitor is limited to 5 scans per hour, so repeat traffic from us is bounded. A site owner who has just changed something can force a fresh scan past that cache — worth knowing about, since it is the one way to see us twice in a day — and that is capped at 3 per visitor per 24 hours, on top of the hourly limit.
Why you may see GPTBot or ClaudeBot from our IP
This is the part worth reading carefully. Five of those requests deliberately send the user agent strings of GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot and meta-externalagent — from our IP address, not the operators’.
We are not pretending to be those crawlers. It is the only way to answer the question site owners actually have: your robots.txt says GPTBot is allowed, but is your CDN blocking it anyway? Comparing an ordinary browser fetch against those user agents reveals a user-agent rule that robots.txt alone cannot show.
We report the limits of this honestly. Because we cannot present those operators’ verified IPs, a successful fetch is reported as “no user-agent-level block detected” — never as “allowed”. If your bot management challenged us, that is expected and correct behaviour on your part; our report says so rather than calling your site broken. We never send Googlebot or Bingbot user agents.
How to block us
Add this to your robots.txt:
User-agent: DeployRadarBot
Disallow: /We honour it. When that rule is present we fetch robots.txt, see the rule, and stop — no page requests, no crawler probes, no rendering. A scan of your site will then report only what robots.txt says, and will state plainly that it stopped because you asked it to. A tool that audits robots.txt compliance has no business ignoring robots.txt.
Blocking by user agent at your CDN or WAF works too, and needs no trust in us. A blanket User-agent: * disallow does not stop us, deliberately: those rules are aimed at indexing crawlers, and site owners running a one-off diagnostic on their own site should not be defeated by their own file.
Contact
Questions, or a complaint about our behaviour on your site: hello@deployradar.dev. If we are causing you a problem, tell us and we will fix it.