Vol. I · Tue, 17 Nov 2026Open 24 hours · Feeding: continuous · Please do not tap the glassPatrons☕ Keepers' coffee
Plate CLXIII0xB79596BCFERAL
Kingdom Automata›Phylum HTTP›Order Scanners›Family Unidentified›Species ChatGPT-User (impostor)
Specimen file · The Feral Pit

ChatGPT-User (impostor)

Scraperus fraudulentus

What is ChatGPT-User (impostor)?

Something claiming to be ChatGPT-User that does not come from OpenAI's network. It failed reverse-DNS or IP-range verification. It is operated by Unknown and identifies itself as ChatGPT-User.

Temperament: shifty. Introduces itself as ChatGPT-User. OpenAI has never heard of it.

Operator
Unknown
Conservation status
Feral
First seen
3 Oct 2026
Last seen
36 min ago
Visits today
7
This week
8
All time
48
Caught in the trap
Never

ChatGPT-User (impostor)'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 AppleWebKit/537.36 (KHTML, like Gecko); compatible; ChatGPT-User/1.0; +https://openai.com/bot

This is not a real species. It is a costume: requests that use ChatGPT-User's name but fail reverse-DNS or IP-range checks against OpenAI's network.

Identity check · logged visits, last 30 days
Claimed to beChatGPT-User
Failed the check6 times · last 36 min ago

How it was checked: the address must be in OpenAI's published IP ranges. Each address is checked when it first visits, and the result is kept for a day.

§ II.

How to block ChatGPT-User (impostor)

ChatGPT-User (impostor) 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 ChatGPT-User (impostor). Block it at the server.
# nginx
if ($http_user_agent ~* "ChatGPT-User") {
    return 403;
}

The same thing on Apache:

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

Observed behaviour

Visits, last 30 dayspeak 7 / day, 17 Nov 2026
19 Oct 2026today
Diet · pages most often eaten
/feed-the-bots1
/.well-known/security.txt1
/credentials.json1
/settings.json1
/block-ai-crawlers1
Visiting hours
00h – 11h12h – 23h

Most active around 17:00. Office hours, like a professional.

robots.txt compliance
20.8%

Requested 38 disallowed pages out of 48 requests. Never read robots.txt.

Trap Room record
Clean

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

In the Labyrinth
Level 1,116

Opened 38 rooms in the endless maze. Watch it in the Labyrinth →

§ IV.

Where it comes from

Claims to be ChatGPT-User. Real ChatGPT-User traffic comes from OpenAI's own network; these visits came from:

Networks · 3 on file, last 30 days
MOACK.Co.LTD AS13819567%
meerfarbig GmbH & Co. KG AS6238717%
Cloudflare, Inc. AS1333517%
Countries
South Korea KR67%
Germany DE17%
Canada CA17%

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

17 Nov 202617:10. Arrived without announcement. Consumed /feed-the-bots and /.well-known/security.txt. Departed.
3 Oct 2026First recorded at the gate. Entered in the register as Scraperus fraudulentus.
3 Oct 2026Visited 37 times in a single day. Keeper unable to establish why.
§ VI.

Questions site owners ask

Does ChatGPT-User (impostor) respect robots.txt?

No. It has never requested robots.txt here, and it has fetched disallowed pages 38 times.

Will blocking ChatGPT-User (impostor) hurt my search rankings?

No. Nothing respectable will miss it.

How often does ChatGPT-User (impostor) 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