RFC 9309
defines robots.txt — a file where a site
states rules for crawlers that choose to follow
them.
Signal, not control:
robots.txt is not access control: by itself it
does not block traffic, does not guarantee exclusion and
does not remove anything. This checker
consults and reports — it reads what
the origin says about our agent
(BTOVEN-Robots) and shows it, without ever
blocking the check you asked for.
What this tool does:
/robots.txt once per origin and
caches it for days — repeated checks (and every
other BTOVEN checker) reuse the same result
User-agent / Allow /
Disallow / Crawl-delay /
Sitemap)
Per RFC 9309 §2.2.1 crawlers must support robots.txt files of at least 500 KiB; an absent file means no restrictions.
Enter a domain (or URL) to inspect its robots.txt:
There is also an API that returns the same results in JSON format, its endpoint is: /api/lookup?url=example.com
You can find the OpenAPI specification and Swagger UI at /api-docs/ui/