vultr.com: what it tells AI crawlers

On 27 October 2026, vultr.com's robots.txt refused our fetcher (HTTP 403 or a bot challenge), so its policy could not be read.

Last verified 2026-10-28 03:59 UTC (daily run of 2026-10-27). Proof for that day.

Panel

top 10k (Tranco)

robots.txt

fetch-blocked (HTTP 403) · https://www.vultr.com/robots.txt
unchanged since 2026-10-26

Per AI bot, 2026-10-27

Other signals

robots.txt as recorded sha256 daeb368e8eeb85b1…

# Hello, human. If you're reading this, you should work at Vultr!
# https://www.vultr.com/jobs/

User-agent: *
Disallow: /_ajax/
Disallow: /_blocks/
Disallow: /_snippets/
Disallow: /debug/
Disallow: /promo/*
Disallow: /sedaily/
Disallow: /swedaily/
Disallow: /lastweek/
Disallow: /screaming/
Disallow: /morningbrief/
Disallow: /devweek/
Disallow: /devdiscuss/
Disallow: /techforge/
Disallow: /codenewbie/
Disallow: /techtarget/
Disallow: /gitcommit/
Disallow: /rss/
Disallow: /administer.vultr.com/
Disallow: /marketing-sales-files/
Disallow: /digitalocean-vs-vultr/

Sitemap: https://www.vultr.com/sitemap.xml
Sitemap: https://www.vultr.com/docs/doc_sitemap.xml

User-agent: GPTBot
Disallow: /docs/

robots.txt versions

Timeline of changes

Reconstructed history (Common Crawl)

From Common Crawl's robots.txt captures: what CCBot was served, one crawl per quarter. A separate series from the daily observations above; a 403 here means Common Crawl was refused, not this ledger.

Evidence

Every daily observation of vultr.com is a leaf in that day's Merkle tree. Proof of the robots.txt line for 2026-10-27: audit path (JSON), day root and OpenTimestamps proof (complete (bitcoin block 973493)).

API: https://infrarabbit.com/crawlers/api/v1/policy/vultr.com