Overview
SnowHaze Search is a search crawler from SnowHaze used for search indexing, URL discovery, page rendering, result freshness, and search-quality checks.
Its primary user-agent pattern is SnowHaze Search.
SnowHaze Search is Unverified at the identity-evidence level. The listed identity remains useful for detection, but this record does not currently contain authoritative evidence sufficient to authenticate the identity claim.
Robots.txt behavior is not currently confirmed.
SnowHaze Search should be monitored first, then rate-limited or blocked if the crawl rate, paths, or behavior are unwanted.
Identity
- User-Agent Pattern
-
SnowHaze Search - HTTP Agent Examples
-
SnowHaze Search - Robots Token
- SnowHaze Search
- Identity Type
- Observed
- Evidence Method
- Treat `SnowHaze Search` as an identity signal only. Confirm it with current operator documentation, cryptographic verification, forward-confirmed reverse DNS, source-network ownership, or other authoritative evidence before trusting the claimed identity.
Classification
- Type
- Search engine crawler
- Kind
- Search engine crawler
- Family
- SnowHaze
- Purpose
- Search indexing
Behavior and handling
- Common Use
- SnowHaze Search is used for search indexing, URL discovery, page rendering, result freshness, and search-quality checks.
- Detection Notes
- SnowHaze Search traffic is primarily detected by the `SnowHaze Search` user-agent pattern. Compare source IPs, reverse DNS, request paths, and crawl cadence with SnowHaze infrastructure before trusting the traffic.
- Respects robots.txt
- Unknown
- Spoofing Risk
- SnowHaze Search has medium spoofing risk because user-agent strings can be copied; pair the match with DNS, IP, behavior, or operator evidence.
- Risk
- Neutral
- Recommended Handling
- Monitor
Rules and controls
- Robots.txt Snippet
-
# robots.txt behavior is unconfirmed. Do not rely on this rule without verification.
Relationships
- Operator
- SnowHaze Checked 2026-08-07
Relationships without an Evidence link are normalized from the canonical directory record. They should not be interpreted as independent proof of physical presence or request origin.