What Checkly does
Checkly runs synthetic monitoring against web applications by executing automated API checks, browser checks, and Playwright test suites that its customers configure to verify functionality and performance. Its API and multistep checks identify themselves with the user agent "Checkly/1.0 (https://www.checklyhq.com)", while browser checks use "Checkly, https://www.checklyhq.com". All traffic originates from fixed IP addresses that Checkly publishes as IPv4 and IPv6 lists, updated infrequently (every 6 months or less). Checkly is also registered with Cloudflare as a verified bot in the Monitoring & Analytics category.
How to control Checkly
Target Checkly in your robots.txt with the Checkly token. Rules apply per bot, so you can allow this one while blocking others, or the reverse.
Allow Checkly
User-agent: Checkly
Allow: /Block Checkly
User-agent: Checkly
Disallow: /Checkly publishes its fixed IPv4 and IPv6 source addresses through documented endpoints, updated roughly every six months or less, and is registered with Cloudflare as a verified bot, but its documentation does not describe robots.txt support.
How to identify Checkly
Temso identifies Checklytraffic by matching the request's User-Agent header against this pattern. User-agent strings can be spoofed, so treat a match as an indication, not proof.
ChecklyCheckly FAQ
What is Checkly?
Checkly is a synthetic monitoring service that runs automated API checks, browser checks, and Playwright test suites against web applications to verify that they work and perform as expected. Its requests come from fixed, published IP addresses and carry a Checkly user agent string.
How do I block Checkly?
Checkly's documentation does not describe robots.txt support; its checks run against URLs configured by a Checkly customer rather than by autonomous crawling. The documented way to control this traffic is at the network level: Checkly publishes its fixed IPv4 and IPv6 addresses, so you can block or allow those ranges in your firewall.
About Operational Bots
Monitoring, security scanning, link previews, webhooks, and feed fetchers: the utility traffic that keeps integrations and shared links working.
Most of this traffic is service-critical or user-triggered. Webhooks and previews don't follow robots.txt, and blocking them tends to break things you rely on.
