SirdataBot
risk.is_crawler
- Method
- Ranges Published IP ranges
- Official file
- Format
- Plain-text address list
- Refresh
- Every 10 minutes. If a refresh fails, entries expire after 24 hours instead of being trusted forever.
Bot signals — Search & SEO crawler
SirdataBot IP addresses
Contextual page categorization crawler origins. Operator recommends refreshing every ten minutes.
01 — Verification
How IPAPI.GR verifies SirdataBot.
Only from what SirdataBot 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.
02 — In the response
What a match looks like.
A lookup of a SirdataBot 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 SirdataBot but doesn't match is unverified.
{
// … location and network fields …
"risk": {
"is_ai": false,
"is_crawler": true,
"is_scanner": false
}
}
03 — Questions
About SirdataBot.
Where does SirdataBot publish its IP addresses?
SirdataBot publishes its addresses at https://proxies-list.sirdata.fr/. IPAPI.GR reads that publication directly, not a third-party copy.
How often is the SirdataBot list refreshed?
IPAPI.GR re-fetches it every 10 minutes. If a refresh fails, the previous entries expire after at most 24 hours instead of being trusted forever.
Which risk flag does SirdataBot set?
A matching address sets risk.is_crawler in the lookup response. The risk flags are returned for Pro API keys.
From the blog
Go deeper.
Related operators
Verify SirdataBot on every request.
Pro: 40,000,000 requests a day with is_ai, is_crawler and is_scanner in every lookup.