VPNSmith
self-host-vpnINFO

90 of 100 Privacy Companies Have Never Named an AI Crawler in robots.txt (August 2026)

We read the robots.txt of 106 VPN, password manager, encrypted messaging and privacy-tool websites. Only ten have said anything at all about AI crawlers, and one addressed all eight. Full data, method and scanner published.

By Eric Gerard · Founder · VPNSmith - Self-host VPN & GDPR VPS specialist5 min readPhoto: Pexels

A site's robots.txt is the one place where a company states, in public and in writing, what it wants automated clients to do with its pages. So for an industry whose entire product is control over data, it is a fair question: has it said anything about AI crawlers on its own websites?

We read the robots.txt of 106 VPN providers, password managers, encrypted messengers, self-hosted tools and privacy-focused hosts on 17 August 2026 - the same list of domains we used for the HTTP security headers ranking.

robots.txt asks. It does not prevent.

Before any number means anything, this has to be said plainly: robots.txt is a convention. It is a text file that requests certain clients stay away, and a crawler that ignores it meets no obstacle at all - the pages are served to whoever asks for them. Compliant operators honour it; that is the whole mechanism.

A low waist-high wooden slat gate carrying a red and white PRIVATE PROPERTY NO TRESPASSING sign, with the planked walkway continuing past it between buildings toward open water and a distant shoreline.
A low waist-high wooden slat gate carrying a red and white PRIVATE PROPERTY NO TRESPASSING sign, with the planked walkway continuing past it between buildings toward open water and a distant shoreline.

The gate in the photograph is about waist high and the deck carries on behind it. That is the accurate mental model: the sign works on anyone who reads signs.

So a BLOCK in the table below does not mean a crawler was stopped. It means the operator wrote down what they wanted. That is exactly what makes the silence interesting - saying nothing costs nothing, and 90 sites still said nothing.

The method, in full

One unauthenticated GET of /robots.txt per domain, following the robots specification for group selection:

  1. a group whose User-agent: names the crawler wins over the wildcard * group;
  2. inside the winning group, Disallow: / is read as a block; anything else is read as access;
  3. no applicable group at all is recorded as -.

Four values appear in the data, and the difference between the first pair and the second is the entire point:

valuemeaning
ALLOW / BLOCKthe agent is named in the file - a decision was made
ALLOW* / BLOCK*inherited from the wildcard group - the site never mentioned this agent
-no applicable group
(empty)the request failed. Not a zero, not a "no position"

Our first version of the scanner collapsed those two pairs, and reported that Proton, Mullvad, DuckDuckGo and Nextcloud all allowed every AI crawler. They do not: they have simply never written the word GPTBot. Reading inherited permission as consent would have produced the exact opposite headline from the truth, so the distinction is preserved in every row.

The ten sites that took a position

sitenamedblocksallows
posteo.de8 of 8all eight
www.dashlane.com7GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, PerplexityBot, Google-Extended, CCBot
www.lastpass.com6GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, PerplexityBot, Google-Extended
www.hostinger.com6GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, PerplexityBot, Google-Extended
keepassxc.org5GPTBot, ClaudeBot, Google-Extended, Applebot-Extended, CCBot
standardnotes.com5GPTBot, ClaudeBot, Google-Extended, Applebot-Extended, CCBot
bitwarden.com5GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, CCBot
www.eff.org4GPTBot, ClaudeBot, Google-Extended, CCBot
exodus-privacy.eu.org1GPTBot
vultr.com1GPTBot

posteo.de is the only site in 106 that addressed all eight agents, and it blocks every one of them.

Two things in the data worth noticing

Nobody welcomes Apple. Applebot-Extended - Apple's opt-out token for training - is named by three sites and blocked by all three. It is the only one of the eight with zero explicit allows. Whether that reflects a judgement about Apple or simply that the operators who bother to name it are the ones who block everything, this dataset cannot say.

Password managers split down the middle on the same question. Five of the ten deciders are password managers, and they went opposite ways: Bitwarden, LastPass and Dashlane name AI crawlers and let them in; KeePassXC and Standard Notes name them and shut them out. Same product category, same year, opposite conclusions. We are not going to invent a reason for that - we are recording that the disagreement exists inside one category, which is more informative than an industry average.

Download the raw data

privacy-industry-ai-crawlers-2026.csv - one row per site, one column per agent, 106 rows.

  • 100 measured, 6 with empty fields because the request failed. A failed measurement is not a finding.
  • A homepage_redirects_to column flags the six domains whose homepage redirects elsewhere (openziti.ionetfoundry.io, vaultwarden.devvaultwarden.com, threema.chthreema.com, tutanota.comtuta.com, www.veracrypt.frveracrypt.io, uptimekuma.orguptimekuma.co). Note that /robots.txt and the homepage do not always behave the same way: openziti.io answers on its own /robots.txt (it has none) while redirecting its homepage to netfoundry.io, which does have one. Both rows are real measurements of different things, and that is why they differ.
  • Released into the public domain under PDDL 1.0. Reuse it, republish it, correct it. If you cite it, cite the date - robots.txt changes the day someone edits it.
  • The scanner is MIT-licensed and dependency-free. Point it at your own list and you will get the same kind of table.

We would rather be corrected than believed. If your site is in the data and the row is wrong - or if you have changed your robots.txt since 17 August - tell us and we will re-measure it.

★ Nuremberg GDPR datacenter · ✓ Dedicated IPv4 included · 200+ Mbps guaranteed

Self-host your VPN on your own VPS → ContaboFull root access · public IPv4 · pick your region

Frequently asked questions

Does blocking an AI crawler in robots.txt actually stop it?
No. robots.txt is a request, not an access control. It is a text file asking well-behaved clients to stay out, and a crawler that ignores it faces no technical obstacle - the pages are served to anyone who asks. Blocking in robots.txt is a statement of intent that compliant operators honour. If you need enforcement you need authentication, rate limiting or blocking at the edge, and none of that is what we measured here.
Is it better to allow or to block AI crawlers?
There is no right answer and this is not a ranking. Allowing them buys visibility in AI answers, which is where a growing share of product research happens. Blocking them keeps your material out of training corpora. Both are defensible and they trade off against each other. The finding here is not that anyone chose wrongly - it is that 90 of 100 sites in this industry have not visibly chosen at all.
What does ALLOW* mean in the data?
That the site never named that agent, so the crawler falls back to the wildcard User-agent group, which happens not to exclude it. It is inherited permission, not a decision. We keep it visually distinct from a plain ALLOW because conflating the two would have made this dataset say that the whole industry welcomes AI crawlers, when in fact most of it has said nothing. That distinction is the point of the dataset.
Why do six rows have empty fields?
Because those six requests failed - a connection error, a redirect we did not follow, or a host that refused an automated client. A failed measurement is not a finding. Writing it as a zero, or as 'no position', would invent data we do not have, so the fields are left empty and the sites are still listed.
Which AI user-agents did you check, and why those eight?
GPTBot, OAI-SearchBot and ChatGPT-User (OpenAI, respectively training, search indexing and user-triggered fetches - they are three separate decisions), ClaudeBot, PerplexityBot, Google-Extended, Applebot-Extended and CCBot. The last is Common Crawl, which is not an AI company but is the upstream source of many training corpora, so naming it is a distinct and deliberate choice.