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

Chrome-Lighthouse

Incertae sedis

What is Chrome-Lighthouse?

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

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

Operator
Unknown
Conservation status
Respects robots.txt
First seen
22 Nov 2026
Last seen
6 h ago
Visits today
8
This week
8
All time
8
Caught in the trap
Never

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

Chrome-Lighthouse'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
$ Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/136.0.0.0 Safari/537.36 Chrome-Lighthouse

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 Chrome-Lighthouse

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 Chrome-Lighthouse's next visit. Nothing else on your site needs to change.

robots.txt
# Block Chrome-Lighthouse from the whole site
User-agent: Chrome-Lighthouse
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: Chrome-Lighthouse
Allow: /
Disallow: /members/
§ III.

Observed behaviour

Visits, last 30 dayspeak 8 / day, 22 Nov 2026
24 Oct 2026today
Diet · pages most often eaten
/4
/.well-known/ai-catalog.json1
/.well-known/ard.json1
/robots.txt1
/llms.txt1
Visiting hours
00h – 11h12h – 23h

Most active around 03:00. The keepers are asleep. It knows.

robots.txt compliance
100.0%

Requested 0 disallowed pages out of 8 requests. Read robots.txt 1 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
Google LLC AS15169100%
Countries
United States US100%

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

22 Nov 2026Visited 8 times in a single day. Keeper unable to establish why.
22 Nov 202603:08. Arrived without announcement. Consumed /.well-known/ai-catalog.json and /.well-known/ard.json. Departed.
22 Nov 2026Observed reading robots.txt in full. Complied with every word.
22 Nov 2026First recorded at the gate. Entered in the register as Incertae sedis.
§ VI.

Questions site owners ask

Does Chrome-Lighthouse respect robots.txt?

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

Will blocking Chrome-Lighthouse hurt my search rankings?

No. Nothing respectable will miss it.

How often does Chrome-Lighthouse visit?

Here, about 1 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