Overview
yisouspider is operated by Shenma Search and is used for Crawling mobile-oriented web content for Shenma Search.
Its documented identity is yisouspider. The robots.txt token is yisouspider.
It follows robots.txt rules addressed to yisouspider.
yisouspider 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.
Match the exact yisouspider token and corroborate it with Shenma-controlled documentation, source-network ownership, and consistent crawl behavior.
Identity
- User-Agent Pattern
-
yisouspider - Aliases
- Shenma spider; Yisou spider
- HTTP Agent Examples
-
yisouspider - Robots Token
- yisouspider
- Identity Type
- Observed
- Evidence Method
- Treat `yisouspider` 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
- Kind
- Crawler
- Family
- Shenma
- Purpose
- Mobile search indexing
Behavior and handling
- Common Use
- Crawling mobile-oriented web content for Shenma Search.
- Detection Notes
- Shenma's official webmaster guidance identifies yisouspider as its crawler and asks sites to permit search-engine crawling through robots.txt.
- Respects robots.txt
- Yes
- Spoofing Risk
- The token is easy to copy and currently lacks a published cryptographic identity mechanism; verify network and behavior.
- Risk
- Neutral
- Recommended Handling
- Depends
Rules and controls
- Robots.txt Snippet
-
User-agent: yisouspider Disallow: / - Apache Rule
-
RewriteCond %{HTTP_USER_AGENT} yisouspider [NC] RewriteRule .* - [F,L] - Nginx Rule
-
if ($http_user_agent ~* "yisouspider") { return 403; }
Relationships
- Operator
- Shenma Search Checked 2026-08-07
- Owner / parent organization
- UCWeb / Alibaba Group 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.