Bytespider
ByteDance · No operator statement
What it does
ByteDance says nothing: there is no documentation page, no published user-agent string and no compliance statement. What is known about Bytespider comes from access logs like the observed section below.
The facts
| Operator | ByteDance |
| robots.txt token | Bytespider |
| Appears in access logs | Yes |
| User-agent string | Not published by the operator |
| robots.txt | No statement published. ByteDance publishes no compliance claim to hold it to. Independent bot databases report it does not honor robots.txt directives; that is their claim, not ByteDance's. |
| IP list | Not published |
| Documentation | None exists. Searched 4 Aug 2026. |
Allow or block it in robots.txt
To block Bytespider entirely:
User-agent: Bytespider Disallow: /
To allow it everywhere:
User-agent: Bytespider Allow: /
Verify a request is really Bytespider
No published IP list or verification method exists.
ByteDance publishes no documentation page for Bytespider at all (searched 2026-08-04). Every other crawler in this index has an operator page to cite; this one's entry is defined by that absence. The user-agent string seen in access logs carries a spider-feedback@bytedance.com contact address, which is the only operator-published artifact, and it is inside the request itself.
Observed on this property
| First seen here | 26 Aug 2026 |
| Most recent | 13 Sep 2026 |
| Requests, last 30 days | 68 |
| Requests, all time | 68 |
| robots.txt fetches | 1 |
User-agent string it sent here:
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:132.5) Gecko/20100101 Firefox/132.5; compatible; Bytespider; +https://zhanzhang.toutiao.com/
Most requested paths:
/@fs/root/.config/hcloud/cli.toml(2)/proc/self/environ/(2)/(1)/.aider.conf.yml(1)/ai.json(1)/api/.env(1)/api-keys.json(1)/api/keys.json(1)