--- title: "Google Cloud Fraud Defense: vendor profile | Agent Ready Crawlers" description: "Google Cloud Fraud Defense: bot management vendor profile covering Google Cloud Fraud Defense (reCAPTCHA) and Google Cloud Armor. Read 2026-11-05." canonical: https://agentreadycrawlers.com/vendors/google-cloud-fraud-defense site: "Agent Ready Crawlers" last_updated: 2026-11-05 section: "Vendors" --- # Google Cloud Fraud Defense: vendor profile | Agent Ready Crawlers > Google Cloud Fraud Defense: bot management vendor profile covering Google Cloud Fraud Defense (reCAPTCHA) and Google Cloud Armor. Read 2026-11-05. Source: https://agentreadycrawlers.com/vendors/google-cloud-fraud-defense Site: Agent Ready Crawlers Last reviewed: 2026-11-05 Bot management vendor # Google Cloud Fraud Defense In short Google Cloud Fraud Defense reports verified and suspected agent sessions side by side, treating as suspected any session that declares itself through headers or behaves like an agent without being verifiable. It plugs into Cloud Armor, Fastly and Cloudflare at the WAF layer, deciding by signature where one exists or else by matching the user agent to published addresses. Type [Bot management](https://agentreadycrawlers.com/vendors/by-type/bot-management/) Operator Google Homepage [cloud.google.com](https://cloud.google.com/security/products/recaptcha) In one line Google Cloud's bot and fraud service, the evolution of reCAPTCHA, which verifies AI agents by Web Bot Auth signature or by user agent matched to published IP ranges or reverse DNS, and reports verified and suspected agent sessions. Last read 2026-11-05 ## What Google Cloud Fraud Defense does for this layer ### From the vendor's own pages Google Cloud Fraud Defense classifies agent traffic with two verification methods: Web Bot Auth signatures, and the User-Agent string checked against the source IP address. ([docs.cloud.google.com](https://docs.cloud.google.com/recaptcha/docs/monitor-agents), dated 2026-10-26) Google counts sessions that self-declare as agents, for example through HTTP headers, or behave like agents but cannot be verified, as suspected agent sessions. ([docs.cloud.google.com](https://docs.cloud.google.com/recaptcha/docs/monitor-agents), dated 2026-10-26) Google's Fraud Defense post calls Web Bot Auth its preferred standard for agents and bot operators, and says Fraud Defense also validates declared user agents against published egress IP blocks and reverse DNS records. ([security.googlecloudcommunity.com](https://security.googlecloudcommunity.com/community-blog-42/how-google-cloud-fraud-defense-recaptcha-identifies-agents-and-bots-and-why-builders-should-sign-their-traffic-8449)) reCAPTCHA in Fraud Defense is free up to 10,000 assessments a month per organization, then a USD 8 flat fee up to 100,000, then USD 1 per 1,000 assessments. ([cloud.google.com](https://cloud.google.com/security/products/recaptcha)) Google's reCAPTCHA page says it integrates at the WAF layer with Google Cloud Armor, Fastly and Cloudflare, and combines with Cloud Armor and Apigee in Google's WAAP offering. ([cloud.google.com](https://cloud.google.com/security/products/recaptcha)) ### Claims the vendor makes about itself Google says an operator that signs with Web Bot Auth builds a reputation that extends across the 14 million+ websites protected by Fraud Defense. ([security.googlecloudcommunity.com](https://security.googlecloudcommunity.com/community-blog-42/how-google-cloud-fraud-defense-recaptcha-identifies-agents-and-bots-and-why-builders-should-sign-their-traffic-8449)) ## Products and plans | Product | What it does | Price model | From | As of | | --- | --- | --- | --- | --- | | Google Cloud Fraud Defense (reCAPTCHA) | Bot and agent assessments with an Agent overview dashboard and policy controls. | per assessment Free to 10,000 assessments a month; USD 8 flat to 100,000; then USD 1 per 1,000. | USD 0 | 2026-11-05 | | Google Cloud Armor | WAF that can call reCAPTCHA for bot management at the edge. | No price recorded | ## Standards | Standard | Status | Evidence | | --- | --- | --- | | Web Bot Auth | Supports | Fraud Defense verifies Web Bot Auth signatures and calls it the preferred standard. (security.googlecloudcommunity.com) | | Published IP list | Supports | Declared user agents are checked against published egress IP blocks. (security.googlecloudcommunity.com) | | Reverse DNS check | Supports | Declared user agents are also checked against reverse DNS records. (security.googlecloudcommunity.com) | | Visa Trusted Agent Protocol | No statement | No statement on the Fraud Defense pages read 2026-11-05. | | Mastercard Agent Pay | No statement | No statement on the Fraud Defense pages read 2026-11-05. | ## Our checks | Check | Result | Method | Date | | --- | --- | --- | --- | | Homepage fetch | HTTP 200 | GET with the crawl user agent after a robots.txt check | 2026-11-05 | ## What Google Cloud Fraud Defense does not do - Fraud Defense's Agent overview only covers the last 30 days or the current month. - Fraud Defense offers no charging or licensing route for AI crawlers. ## Reading notes Google also runs crawlers, covered on [Google's own profile](https://agentreadycrawlers.com/vendors/google/); this one covers only the bot-management product. ## Related pages on this site - [All bot management vendors](https://agentreadycrawlers.com/vendors/by-type/bot-management/) 23 profiles - [The full vendor list](https://agentreadycrawlers.com/vendors/) 73 profiles in four types - [Google-Agent](https://agentreadycrawlers.com/crawlers/google-agent/) no token ## Sources - [reCAPTCHA website security and fraud protection | Google Cloud](https://cloud.google.com/security/products/recaptcha) read 2026-11-05 - [Monitor agent traffic  |  Google Cloud Fraud Defense  |  Google Cloud Documentation](https://docs.cloud.google.com/recaptcha/docs/monitor-agents) read 2026-11-05 - [How Google Cloud Fraud Defense (reCAPTCHA) Identifies Agents and Bots-And Why Builders Should Sign Their Traffic | Community](https://security.googlecloudcommunity.com/community-blog-42/how-google-cloud-fraud-defense-recaptcha-identifies-agents-and-bots-and-why-builders-should-sign-their-traffic-8449) read 2026-11-05 Last reviewed 2026-11-05