Bot intelligence record
yacybot
Review firstUse the yacybot identifier to separate YaCy search indexing or content discovery traffic from normal visitor requests in server logs.
- Operator
- YaCy
- Family
- YaCy
- Type
- Search
- Source type
- Official
- Last checked
- 2026-05-20
User-Agent Pattern
YaCyyacybot
User-agent strings are identification signals, not proof of identity. Confirm important allow, block, or rate-limit decisions with logs, DNS or IP evidence, request behavior, or operator documentation when available.
Robots.txt Snippet
Click snippet to copyUser-agent: yacybot Disallow: /Click the snippet to copy it, or highlight the text manually.
Handling Guidance
DependsUse this record as bot intelligence, then verify the request source and behavior before allowing, blocking, or rate limiting.
Search indexing, content discovery, rendering, or search-result freshness checks.
Record Details
Structured data- Operator
- YaCy
- Family
- YaCy
- Type
- Search
- Purpose
- Indexing
- Identity type
- Official Documented
- Confidence
- High
- Last verified
- 2026-04-01
- Last checked
- 2026-05-20
- Source type
- Official
- Verification
- Official YaCy bot documentation; verify by user-agent and behavior, but note that crawlers are run by YaCy users rather than a single central service.
- Spoofing risk
- User-agent strings for yacybot can be spoofed. Treat user-agent detection as a classification signal, then verify with published IP ranges, reverse DNS, signatures, operator documentation, or published operator documentation, IP ranges, reverse DNS, signatures, or other verified identity signals before allow-listing.
Notes
yacybot is listed in the Botcrawl directory as a search crawler from YaCy. The primary identifier for log review is yacybot.
Identification
- User-agent pattern:
yacybot - Family: YaCy
- Type: Search
- Kind: Crawler
Common use
Search indexing, content discovery, rendering, or search-result freshness checks.
Verification and handling
Official YaCy bot documentation; verify by user-agent and behavior, but note that crawlers are run by YaCy users rather than a single central service.
Directory guidance marks the risk level as Neutral and the blocking decision as Depends. Do not rely on the user-agent string alone because user-agent strings can be copied or spoofed.
Robots.txt handling: Yes.
Evidence and Source
- Official YaCy bot documentation; verify by user-agent and behavior, but note that crawlers are run by YaCy users rather than a single central service.
- Match `yacybot` as a case-insensitive substring in HTTP user-agent logs. Review bot_aliases for alternate names or product labels. Do not treat a user-agent match alone as proof of identity for allow-listing.
- Search indexing, content discovery, rendering, or search-result freshness checks.
- User-agent strings for yacybot can be spoofed. Treat user-agent detection as a classification signal, then verify with published IP ranges, reverse DNS, signatures, operator documentation, or published operator documentation, IP ranges, reverse DNS, signatures, or other verified identity signals before allow-listing.
Monitor This Bot In Edge
Botcrawl EdgeUse Botcrawl Edge to see matching traffic, create allow or block rules, and control this bot across connected sites.