Vol. I · Sun, 22 Nov 2026Open 24 hours · Feeding: continuous · Please do not tap the glassPatrons☕ Keepers' coffee
Plate CCXXII0x75C51104OBEYED
Kingdom Automata›Phylum HTTP›Order Scanners›Family Unidentified›Species CryptoOutreachBot
Specimen file · The Feral Pit

CryptoOutreachBot

Incertae sedis

What is CryptoOutreachBot?

A self-declared bot that is not in the keepers' catalogue yet. It calls itself “CryptoOutreachBot”. It is operated by Unknown and identifies itself as CryptoOutreachBot.

Temperament: unknown. Recently arrived. The keepers are still taking notes.

Operator
Unknown
Conservation status
Respects robots.txt
First seen
8 Oct 2026
Last seen
1 days ago
Visits today
0
This week
4,425
All time
10,644
Caught in the trap
Never

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

CryptoOutreachBot's food bowl

the bowl, as bots see it

2 snacks are waiting. Last time, Barkrowler stole the Lightly Salted Query Strings, 22 h ago.

5 of 5 tokens left today
§ I.

Identification

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

User-Agent
$ Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0 Safari/537.36 CryptoOutreachBot/1.0

There is no operator to verify against. This name is what software calls itself when nobody gave it one.

Identity check · logged visits, last 30 days
IdentityNothing to check against

No operator stands behind this name, so there is nothing to check its visits against.

§ II.

How to block CryptoOutreachBot

Add these two lines to the robots.txt file at the root of your site. Well-behaved crawlers read it before they crawl, so the change applies from CryptoOutreachBot's next visit. Nothing else on your site needs to change.

robots.txt
# Block CryptoOutreachBot from the whole site
User-agent: CryptoOutreachBot
Disallow: /

Or let it visit but keep it away from part of the site:

# Let it in, but keep it out of one room
User-agent: CryptoOutreachBot
Allow: /
Disallow: /members/
§ III.

Observed behaviour

Visits, last 30 dayspeak 1,000 / day, 14 Nov 2026
24 Oct 2026today
Diet · pages most often eaten
/leaderboard1,026
/915
/trap-room458
/badge458
/contact458
Visiting hours
00h – 11h12h – 23h

Most active around 23:00. After dark, like a burglar.

robots.txt compliance
100.0%

Requested 0 disallowed pages out of 10,644 requests. Read robots.txt 459 times.

Trap Room record
Clean

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

§ IV.

Where it comes from

Scripts and scanners run from wherever their owners rent a server. These are the networks behind the visits on file:

Networks · 1 on file, last 30 days
LeaseWeb Netherlands B.V. AS60781100%
Countries
Netherlands NL100%

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

21 Nov 202601:30. Arrived without announcement. Consumed /bots/dotbot and /bots/censysinspect. Departed.
21 Nov 2026Observed reading robots.txt in full. Complied with every word.
14 Nov 2026Visited 1,000 times in a single day. Keeper unable to establish why.
8 Oct 2026First recorded at the gate. Entered in the register as Incertae sedis.
§ VI.

Questions site owners ask

Does CryptoOutreachBot respect robots.txt?

Yes. In 10,644 requests observed here it has read robots.txt and never fetched a disallowed page.

Will blocking CryptoOutreachBot hurt my search rankings?

No. Nothing respectable will miss it.

How often does CryptoOutreachBot visit?

Here, about 632 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 The Feral Pit