Yeti conduct record
Naver · indexing. Not enough verified requests yet (6 of 50) for a verdict.
| Conduct | insufficient data |
|---|---|
| Verified requests | 6 (from Naver’s published ranges) |
| Forged claims | 0 — 0% of requests using this name were impersonators |
| robots.txt | insufficient data · 3 robots.txt fetches · 0 fetches of disallowed paths (/r/, /backup/, /admin-old/) |
| Rate | measured · busiest minute 1 requests (2026-10-20T06:52 UTC), all its addresses combined; no crawl rate is published here, so this is reported, not judged · measured since 2026-10-20 |
| Revalidation | 0 conditional requests (0% of verified) |
| Seen here | 2026-10-20 → 2026-11-10 |
| 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/Yeti (verify with crawlcheck-verify.mjs). Generated 2026-11-12 16:04 UTC; rebuilt every ten minutes.