DuckDuckBot conduct record
DuckDuckGo · indexing. No rule broken in what was measured: no fetch of a path robots.txt disallows, though it never fetched robots.txt under its own name here; busiest minute 2 requests, all its addresses combined.
| Conduct | no violations observed |
|---|---|
| Verified requests | 133 (from DuckDuckGo’s published ranges) |
| Forged claims | 0 — 0% of requests using this name were impersonators |
| robots.txt | robots txt not fetched · 0 robots.txt fetches · 0 fetches of disallowed paths (/r/, /backup/, /admin-old/) |
| Rate | measured · busiest minute 2 requests (2026-10-10T21:21 UTC), all its addresses combined; no crawl rate is published here, so this is reported, not judged · measured since 2026-10-10 |
| Revalidation | 0 conditional requests (0% of verified) |
| Seen here | 2026-08-12 → 2026-11-09 |
| Other sites, 14 days | 0 visitor checks: 0 verified, 0 spoofed |
verified requests to paths this site's robots.txt disallows for every agent, including a group that names this one; a lower bound before 7 Oct 2026 (per-path map capped at 40 paths) the busiest minute of verified requests observed here since the counter started, all of the operator's addresses combined; a lower bound. This site publishes no crawl rate (its robots.txt has no Crawl-delay), so the rate is reported, never judged
Signed record for this agent: /api/v1/conduct/DuckDuckBot (verify with crawlcheck-verify.mjs). Generated 2026-11-09 23:48 UTC; rebuilt every ten minutes.