Vol. I · Thu, 19 Nov 2026Open 24 hours · Feeding: continuous · Please do not tap the glassPatrons☕ Keepers' coffee
Plate CXXIV0xB029C58AUNREAD
Kingdom Automata›Phylum HTTP›Order Fetchers›Family Link Unfurlers›Species ScourRSSBot
Specimen file · Link-Preview Petting Zoo

ScourRSSBot

Scrutator rivorum

What is ScourRSSBot?

The feed fetcher for Scour, a personalised content feed run by one developer. It checks the feeds its users add every 15 minutes, looks for feeds at common addresses and fetches new posts, to show its users links. Scour says it does not train AI models on what it fetches. It doesn’t follow robots.txt, because it counts itself as acting for its users; to opt out, email opt-out@scour.ing. It is operated by Scour and identifies itself as ScourRSSBot.

Temperament: diligent. Checks the feeds every fifteen minutes. Leaves no post unturned.

Operator
Scour
Conservation status
Has not read the rules
First seen
3 Oct 2026
Last seen
39 days ago
Visits today
0
This week
0
All time
5
Caught in the trap
Never

Nobody has adopted ScourRSSBot yet. Adopt ScourRSSBot: your name goes on a plaque on this page for a year.

ScourRSSBot's food bowl

the bowl, as bots see it

The bowl is empty.

5 of 5 tokens left today
§ I.

Identification

Its full user-agent string, exactly as it arrives at the gate:

User-Agent
$ ScourRSSBot/1.0 (+https://scour.ing/bot)

Scour publishes its IP addresses at https://scour.ing/ip-list and says they may change. The zoo doesn't check that list yet, so visits are filed by their user agent. Read Scour's documentation.

Identity check · logged visits, last 30 days
IdentitySigned by its operator, not yet checked here

Scour signs its requests, but the zoo doesn't check signatures yet, so every visit filed here is taken at its word for now.

§ II.

How to block ScourRSSBot

ScourRSSBot does not read robots.txt, so a polite sign is wasted on it. Refuse it at your web server or firewall instead. User agents are easy to fake, so pair this with rate limiting.

nginx.conf
# robots.txt will not stop ScourRSSBot. Block it at the server.
# nginx
if ($http_user_agent ~* "ScourRSSBot") {
    return 403;
}

The same thing on Apache:

# Apache (.htaccess)
RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} ScourRSSBot [NC]
RewriteRule .* - [F,L]
§ III.

Observed behaviour

Visits, last 30 dayspeak 1 / day
22 Oct 2026today
Diet · pages most often eaten

Nothing on record in the last 30 days.

Visiting hours
00h – 11h12h – 23h
robots.txt compliance
100.0%

Requested 0 disallowed pages out of 5 requests. Never read robots.txt.

Trap Room record
Clean

Has never followed the hidden link to /trap/. Either well trained or very lucky.

§ IV.

Where it comes from

The networks ScourRSSBot's visits came from:

Nothing on record in the last 30 days.

Networks and countries come from the visitor's IP address, looked up in a local copy of the DB-IP database. The addresses themselves are never stored.

§ V.

Keeper's field notes

3 Oct 2026First recorded at the gate. Entered in the register as Scrutator rivorum.
3 Oct 2026Visited 3 times in a single day. Keeper unable to establish why.
§ VI.

Questions site owners ask

Does ScourRSSBot respect robots.txt?

We can't say yet. It has not fetched robots.txt here, and it has not touched a disallowed page either.

Will blocking ScourRSSBot hurt my search rankings?

No. But links to your site will be shared without a title or preview image, which tends to get fewer clicks.

How often does ScourRSSBot visit?

Here, about 0 requests a day over the last week. Visits to your site depend on its size, how often it changes, and how many links point to it.

Also in Link-Preview Petting Zoo