Bot intelligence record
Scour RSS Bot
Usually allowScour RSS Bot is a feed fetcher from Scour used for RSS or Atom feed polling, syndication refresh, subscription delivery; it appears in server logs as `scour.ing`.
User-Agent Pattern
Scourscour.ing
User-agent strings are identification signals, not proof of identity. Confirm important allow, block, or rate-limit decisions with logs, DNS or IP evidence, request behavior, or operator documentation when available.
Robots.txt Snippet
Click snippet to copyUser-agent: scour.ing
Disallow: /Click the snippet to copy it, or highlight the text manually.
Handling Guidance
DependsThis bot is usually safe to allow when the request source is verified and the traffic matches your site policy.
Scour RSS Bot is used for RSS or Atom feed polling, syndication refresh, subscription delivery, and content update checks.
Record Details
Verified fields- Operator
- Scour
- Family
- Scour
- Type
- Feed
- Purpose
- Feed Fetch
- Identity type
- Verified Bot
- Confidence
- Medium
- Last verified
- 2026-06-23
- Last checked
- 2026-06-23
- Source type
- Documented
- Verification
- Verify Scour RSS Bot by matching `scour.ing` to Scour evidence, then checking reverse DNS, source-network ownership, signed request data, or published crawler documentation when available.
- Spoofing risk
- Scour RSS Bot has medium spoofing risk because user-agent strings can be copied; pair the match with DNS, IP, behavior, or operator evidence.
Notes
- Scour RSS Bot is a feed fetcher from Scour used for RSS or Atom feed polling, syndication refresh, subscription delivery, and content update checks.
- Its primary user-agent pattern is
scour.ing; related patterns includeScour/1.0 (+https://scour.ing/bot); a representative HTTP user-agent isScourRSSBot/1.0 (+https://scour.ing/bot) Scour/1.0 (+https://scour.ing/bot) ScourBot/1.0 (+https://scour.ing/bot). - Scour RSS Bot is verified with Medium confidence. The identity type is Verified Bot, and the evidence basis is a public crawler reference or source-linked documentation.
- Scour RSS Bot is marked as not reliably governed by robots.txt directives; use server-side rules if the traffic should be restricted.
- Scour RSS Bot can usually be allowed after confirming the source and monitoring request volume.
Evidence and Source
- Verify Scour RSS Bot by matching `scour.ing` to Scour evidence, then checking reverse DNS, source-network ownership, signed request data, or published crawler documentation when available.
- Scour RSS Bot traffic is primarily detected by the `scour.ing` user-agent pattern; related patterns include `Scour/1.0 (+https://scour.ing/bot)`; a representative HTTP user-agent is `ScourRSSBot/1.0 (+https://scour.ing/bot) Scour/1.0 (+https://scour.ing/bot) ScourBot/1.0 (+https://scour.ing/bot)`. Compare source IPs, reverse DNS, request paths, and crawl cadence with Scour infrastructure before trusting the traffic.
- Scour RSS Bot is used for RSS or Atom feed polling, syndication refresh, subscription delivery, and content update checks.
- Scour RSS Bot has medium spoofing risk because user-agent strings can be copied; pair the match with DNS, IP, behavior, or operator evidence.
Use This Signal In Edge
Botcrawl EdgeUse Edge to match live requests, detect related datacenter traffic, and apply allow, block, rate-limit, or log rules.