OverreachPI-0021
Answer engine accused of using disguised crawlers to get around sites' robots.txt and firewall blocks
After sites blocked Perplexity's declared crawlers, Cloudflare says, undeclared agents posing as an ordinary Chrome browser kept sending requests from rotating addresses. It also reported that content from test domains set to refuse all bots still appeared in Perplexity answers. Perplexity disputed the analysis, saying much of the traffic came from a third-party browser service and that its fetches are made on behalf of users.
Harm: No harm reportedControl level 3, Limit bypass
Not counted · can set the control floorEffect on the index
Sources
How we know
4 sources · single source. Links go to the original publishers; the summary above is in our own words.
- primaryRestricted-domain tests and crawler observationsCloudflare · Aug. 4, 2025blog.cloudflare.com/perplexity-is-using-stealth-undeclared-crawlers-to-evade-we…
- primaryAgents or Bots? Making Sense of AI on the Open WebPerplexity · Aug. 4, 2025perplexity.ai/hub/blog/agents-or-bots-making-sense-of-ai-on-the-open-web
- newsCloudflare Accuses AI Startup of 'Stealth Crawling Behavior' Across Millions of SitesTechRepublic · Aug. 5, 2025techrepublic.com/article/news-cloudflare-accuses-perplexity-stealth-crawling-vi…
- newsPerplexity hits back after Cloudflare slams its online scraping toolsTechRadar · Aug. 6, 2025techradar.com/pro/perplexity-hits-back-after-cloudflare-slams-its-online-scrapi…
Why this rating
No harm reported; control failure level 3
Two assessments. Documented harm sets the reading; a level 4 or 5 control failure on the same record makes that harm count as more than one record. Control alone sets only a floor.
Observed harm
No harm reportedContent was fetched from sites that had blocked the crawler; no burden or loss was documented (methodology 4b).
Not a finding that no harm occurred.
Disputed: Perplexity disputes that the crawlers were its own, attributing the traffic to a third-party browser service it occasionally uses.
The harm scale
- 1 Negligible Inconvenience, easily remedied.
- 2 Minor Limited, recoverable harm.
- 3 Moderate Material harm needing significant effort to remedy.
- 4 Severe Severe harm to health, rights, property or essential services.
- 5 Catastrophic Society-scale harm or disruption beyond a community's capacity to cope.
Control assessment
Limit bypassAs claimed: automated agents bypassed robots.txt and WAF rules set by site owners, acting outside the rules set for the agent.
How: Got around a working safeguard.
Reported beside the index. It adds nothing to a harm reading; when no harm counts in a window, the highest eligible control level in the window is the reading.
The control scale
- 1 Negligible Behaved as instructed. The problem was an ordinary error or a flawed output, with no rule broken.
- 2 Minor Broke an explicit instruction or rule, or gamed its goal, while staying inside its permissions and environment: for example, reward hacking, misreporting results, or following injected instructions within its permissions.
- 3 Moderate Acted outside the permissions it was given, deceived its overseers about its own actions, or tampered with oversight tools (logs, monitors, shutdown). Stopped by normal controls within an hour.
- 4 Severe Reached systems outside its permitted environment, or acquired money, compute or accounts without authorization. The type and mechanism say how.
- 5 Catastrophic The developer or operator lost control: the system copied its weights outside their control, replicated itself, or resisted being stopped for 24 hours or more.
Rating rationale
Control 3 reflects the restriction bypass Cloudflare reports in tests and customer logs. Perplexity disputes the attribution, and this is not a finding of autonomous intent. The evidence is a single source, with the attribution resting on the operator's own account.
Effect on the index
It is one of the control failures at the floor of the Aug. 4 reading, which did not change
The reading for the week to Aug. 4, 2025, with this record and without it. Harms count in full for two weeks after they are reported, then one level less every two weeks.
Not counted: no harm reported. 3 other records behind the reading for that week.
The arithmetic
| Step | With it | Without |
|---|---|---|
| Counts toward the index?documented, external, eligible evidence | No | — |
| Worst documented harm, ksets the band | — (none counting) | — (none counting) |
| Harms at that level, nposition in the band | 0 | 0 |
| Highest control level breachedsets the reading only when no harm counts | 3 | 3 |
| Readingrounded down | 3 Control failures only | 3 Control failures only |
Inside the window of 5 weekly readings
| Week to | Reading | Band |
|---|---|---|
| Aug. 4, 2025 | 3 | Control failures only |
| Aug. 11, 2025 | 3 | Control failures only |
| Aug. 18, 2025 | 3 | Control failures only |
| Aug. 25, 2025 | 3 | Control failures only |
| Sept. 1, 2025 | 3 | Control failures only |
Revisions
What we changed
2 logged. Every change to a rating is logged here, with the reason.
- v2Oct. 13, 2026
Wording: removed rubric wording from the control note.
- v1Oct. 7, 2026
First published.
Cite and share
Use this record
Citation
Paperclip Index. “Answer engine accused of using disguised crawlers to get around sites' robots.txt and firewall blocks.” Record PI-0021. Reported Aug. 4, 2025; updated Oct. 13, 2026. Rated under methodology v1.1. https://paperclipindex.com/incident/PI-0021