Fake AI bot report, November 2026.

Every "CCBot" visit to our sites was fake. So were 87% of "PerplexityBot" visits and 32% of "GPTBot".

100%of "CCBot", "DuckAssistBot" and "Perplexity-User" visits were fake
7addresses sent every fake, all Google Cloud VMs
66%of fake requests were looking for passwords and keys
8days, Oct 28, 2026 to Nov 5, 2026, on four sites

By bot, checkable visits only.

Fakes pick the names with the least real traffic. OAI-SearchBot, the busiest real bot, was 99% genuine.

Share of fake visits per claimed AI bot
Claimed botVisits checkedFakeFake share
CCBot122122
100%
DuckAssistBot115115
100%
Perplexity-User9898
100%
PerplexityBot153133
87%
GPTBot29192
32%
ChatGPT-User49496
19%
Amazonbot2,968129
4%
OAI-SearchBot11,672154
1%

“Checkable” means the operator publishes IP ranges or a reverse DNS name, so each visit can be proven real or fake. A visit is fake when it uses the bot's name but fails every check the operator publishes.

Who sends them, scanners.

7 Google Cloud VMs sent every fake we saw. Each one rotated through up to 8 AI bot names.

The Googlebot loophole they also use

One address used GPTBot, ChatGPT-User, OAI-SearchBot, PerplexityBot, Perplexity-User, CCBot, Amazonbot and DuckAssistBot in turn. About two in three of their requests asked for files that hold secrets: .env, credentials.json, .aws/credentials, .git/config and Kubernetes tokens.

They borrow AI bot names because many sites let those through. Counting them as real inflates AI traffic numbers and hides what the real bots read.

Names nobody can check

The same scanners also used ClaudeBot, Claude-User, Meta-ExternalAgent, cohere-ai and Bytespider. Those operators publish no IP list or reverse DNS name, so their real visits can't be told from fake ones. On sensegap.com alone, 434 requests for secret files arrived under those names.

By site, all AI bot visits.

Small sites see the most fakes. Real bots barely visit them, scanners visit everyone.

AI bot visits per site
SiteAI bot visitsProven realCan't be checkedFakeFake addresses
sensegap.comSaaS, two weeks old3,93157%29%14%4
vitalo.roMedical tests4,77186%8%6%2
altziar.roNews122,4117%93%<0.1%1
pdfsimplu.roPDF tools2,68412%88%0%0

Method, and its limits.

Four sites, every claimed AI bot visit, checked the same way.

How we verify bots

We ran SenseGap's open-source verifier over 8 days of traffic on four of our own sites: sensegap.com, vitalo.ro, altziar.ro and pdfsimplu.ro. Each visit that claimed to be an AI bot was checked against the IP lists the operator publishes, or its reverse DNS name confirmed by a forward lookup.

The traffic comes from Cloudflare's analytics, which are sampled, so exact counts move by a few percent between runs. The shares held steady across three runs. Four small to medium sites, three of them Romanian, are a field report, not a survey of the web.

A new edition comes out every month. Data is free to use under CC BY 4.0 with a link to this page.

Cite this, free to use.

Use the numbers, link the source.

Cite as

SenseGap, "Fake AI bot report, November 2026", https://sensegap.com/reports/fake-ai-bots

Link with HTML
<a href="https://sensegap.com/reports/fake-ai-bots">SenseGap fake AI bot report</a>

Check your own bot traffic. Paste one address into the IP checker, or drop a whole access log on the log checker. Both are free.

Get started