`Baiduspider-video`

Baidu's English FAQ lists Baiduspider-video as the video-search user-agent and says it does not support the rules currently. The Chinese FAQ at https://help.baidu.com/question?prod_id=99&class=476&id=2996 lists this token and does not say that. This check still reports the RFC 9309 decision for a group that names Baiduspider-video. The English FAQ says blocking Baiduspider blocks all crawling from Baidu. This check matches the whole token and does not treat Baiduspider as a prefix.

robots.txt token: Baiduspider-video
Operator: Baidu
Kind: search
robots.txt: does_not_follow. The vendor says this crawler does not follow robots.txt rules.
HTTP user-agent: The English FAQ names this robots.txt token and does not publish a full HTTP user-agent string.
IP list: None on the cited page. The FAQ does not publish an IP list for this token. The verification section is about Baiduspider hostnames ending in .baidu.com or .baidu.jp. Botcard does not copy the example addresses.
Source: FAQs of Baiduspider. Retrieved 2026-10-18.

JSON

curl -s https://whosthatbot.com/v1/crawlers/baiduspider-video

Check this token

tools/call with name check_robots is the same check at POST /mcp. The pasted file disallows Baiduspider-video on /docs and allows *. The call does not fetch a host.

curl -s https://whosthatbot.com/mcp -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"check_robots","arguments":{"robots_txt":"User-agent: Baiduspider-video\nDisallow: /\n\nUser-agent: *\nAllow: /\n","path":"/docs","ids":["baiduspider-video"]}}}'

That call returns fetched_target false. This row is disallow via group Baiduspider-video, rule Disallow: /.