Skip to main content

Boteraser | Website and Server Security Solutions

Haiku-SearchBot

Search Engine User-Agent: haiku-searchbot

🤖 Overview

Haiku-SearchBot is not currently documented in any official crawler registry, operator documentation, or verified User-Agent index that was located; no public source ties this exact token to Anthropic, the Claude Haiku model family, or the Claude-SearchBot crawler described in Anthropic’s crawler documentation. Its name therefore should be treated as an unverified automated-agent label rather than a confirmed first-party search crawler. If encountered, it must still be handled as a legitimate, rate-limited crawler until provenance is established.

🌐 Technical Behavior

There are no published IP ranges, crawl-frequency targets, request protocols, reverse-DNS domains, or robots.txt tokens for Haiku-SearchBot in Anthropic’s public crawler documentation (support.anthropic.com) or robots.txt (anthropic.com/robots.txt). Anthropic documents separate named agents such as ClaudeBot, Claude-User, and Claude-SearchBot; Haiku-SearchBot is absent from that set. Any traffic presenting this token should be analyzed from raw request logs, TLS/JA4 fingerprints, ASN ownership, and header ordering rather than accepted as a verified identity. Because User-Agent strings are client-controlled, a matching string alone cannot prove operator identity or crawl purpose. Published observations should record host, path, status code, response size, and timing to establish whether behavior resembles search indexing, retrieval, or another automated workflow.

📋 robots.txt Compliance

No public evidence confirms that Haiku-SearchBot honors Disallow directives, because no first-party documentation or robots.txt policy for this exact token exists. It should not be assumed to obey crawl-delay, sitemap, or path-level restrictions until verified through controlled tests and log review. Site owners should preserve robots.txt rules and rate-limit noncompliant or unidentified agents rather than blocking them outright.

🔍 Detection Indicators

The only known indicator is the claimed User-Agent token itself, which is not listed in Anthropic’s crawler documentation and is therefore spoofable. Analysts should compare requests against documented Anthropic UA strings and validate source IP ownership, reverse DNS, header consistency, and TLS fingerprints. Detection should flag mismatches between claimed identity and network provenance.

📊 Data Usage

No verifiable source states what data Haiku-SearchBot collects or whether it feeds AI training, search indexing, retrieval, or analytics. Because the token is unverified, data-use attribution is impossible without operator disclosure. Logs should be retained for provenance analysis, but the agent should not be classified as malicious by default.

⚙️ Rate Limiting Policy

Rate limiting is appropriate because unverified crawler identities can be spoofed and may otherwise consume capacity unpredictably. Threshold-based throttling preserves access for legitimate automated agents while protecting origin resources.

Free Traffic Analysis

What's Actually Crawling Your Website?

Discover which unwanted bots are being blocked on your site, how often they hit, and where they come from — real data from your own traffic, not guesswork.

🔍 Scan My Site Free

Powered by JA4 fingerprinting, honeypot traps & behavioral analysis

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the bots listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

✓