ByteDance Bytespider
risk.is_crawler
- Method
- Ranges Published IP ranges
- Format
- Documentation page, parsed
- Refresh
- Every hour. If a refresh fails, entries expire after 24 hours instead of being trusted forever.
Bot signals — Search & SEO crawler
Toutiao Search crawler subnets from the public About Bytespider document. Does not establish Doubao or TikTok AI coverage.
01 — Verification
Only from what ByteDance Bytespider publishes about itself. No third-party blocklists, no behavioural guesses. Live address counts change with every publication, so check the official file for the current list.
risk.is_crawler
02 — In the response
A lookup of a ByteDance Bytespider address sets risk.is_crawler. The flags come with geolocation and network data in the same response, for Pro API keys.
The response says which kind of bot an address belongs to, not which operator. Pair it with the user agent: a request that claims to be ByteDance Bytespider but doesn't match is unverified.
{
// … location and network fields …
"risk": {
"is_ai": false,
"is_crawler": true,
"is_scanner": false
}
}
03 — Questions
ByteDance Bytespider publishes its addresses at https://zhanzhang.toutiao.com/docs/intro/26899. IPAPI.GR reads that publication directly, not a third-party copy.
IPAPI.GR re-fetches it every hour. If a refresh fails, the previous entries expire after at most 24 hours instead of being trusted forever.
A matching address sets risk.is_crawler in the lookup response. The risk flags are returned for Pro API keys.
From the blog
Pro: 40,000,000 requests a day with is_ai, is_crawler and is_scanner in every lookup.