---
title: "Cloudflare Browser Rendering profile | Agent Ready Crawlers"
description: "Cloudflare Browser Rendering from Cloudflare: no robots.txt token, task agent purpose and what a site can check; no exact user-agent string is published."
canonical: https://agentreadycrawlers.com/crawlers/cloudflare-browser-rendering
site: "Agent Ready Crawlers"
last_updated: 2026-11-04
section: "Crawlers"
---

# Cloudflare Browser Rendering profile | Agent Ready Crawlers

> Cloudflare Browser Rendering from Cloudflare: no robots.txt token, task agent purpose and what a site can check; no exact user-agent string is published.

Source: https://agentreadycrawlers.com/crawlers/cloudflare-browser-rendering
Site: Agent Ready Crawlers
Last reviewed: 2026-11-04

Browsing agent from Cloudflare

# Cloudflare Browser Rendering

In short

Cloudflare Browser Rendering is Cloudflare's browsing agent. Cloudflare Browser Rendering has no robots.txt token, so robots.txt cannot address it and the crawl cannot measure a block rate. It signs requests with Web Bot Auth, so a signature can be checked. Cloudflare documents the automatic request headers; robots.txt handling is up to the customer's script.

Operator

Cloudflare Vendor profile: [Cloudflare](https://agentreadycrawlers.com/vendors/cloudflare/)

Purpose

Task agent [All task agent rows](https://agentreadycrawlers.com/crawlers/purpose/task-agent/). A browsing agent that clicks, fills forms and finishes a job for a person.

User-agent string

No exact string is published. What the operator or a third party says: Sends signed Web Bot Auth headers

robots.txt token

None. No robots.txt line can address this agent.

Respects robots.txt

No statement

Cloudflare documents the automatic request headers; robots.txt handling is up to the customer's script. [Source](https://developers.cloudflare.com/browser-rendering/reference/automatic-request-headers/), read 2026-11-04.

Verification

Web Bot Auth signature

Requests carry an HTTP message signature that can be checked against the operator's published key directory. [Documentation](https://developers.cloudflare.com/browser-rendering/reference/automatic-request-headers/), read 2026-11-04.

IP ranges

Not published.

Rate behaviour

Set by the customer.

Block rate

None: the agent has no token, so a robots.txt block rate does not exist.

Documentation

[blog.cloudflare.com](https://blog.cloudflare.com/signed-agents/), read 2026-11-04.

Note. Classed as a signed agent since 2025-08-28; always given bot score 1 for Bot Management customers, per Cloudflare.

## Allow and refuse lines

This agent has no robots.txt token, so there are no lines to copy. Verify its signature in your WAF or edge rules instead, then allow or refuse the verified identity.

Refusing or allowing in robots.txt states a preference. For this row the operator or its documentation says robots.txt may not govern the fetch, so enforcement belongs in your WAF.

## Cloudflare in the Verification Ledger

Signs Browser Rendering traffic. [All operators](https://agentreadycrawlers.com/verification/).

IP lists

publishes nothing

Reverse DNS

publishes nothing

Key directory

documented in Browser Rendering automatic request headers

Cloudflare

Cloudflare signed agent

Visa TAP registry

no public operator-level registration found (checked 2026-11-04)

Mastercard Agent Pay

no public operator-level registration found (checked 2026-11-04)

## Sources

-   [The age of agents: cryptographically recognizing agent traffic](https://blog.cloudflare.com/signed-agents/) read 2026-11-04
-   [developers.cloudflare.com: automatic request headers](https://developers.cloudflare.com/browser-rendering/reference/automatic-request-headers/) read 2026-11-04

Last reviewed 2026-11-04