Moving from reCAPTCHA to hCaptcha

This post details the migration from Google's reCAPTCHA to hCaptcha for Cloudflare's CAPTCHA challenges. The rationale for the migration includes privacy concerns related to Google's data collection practices, blocking issues in certain regions (like China), and the introduction of charges for reCAPTCHA by Google. The post highlights the benefits of hCaptcha, including its privacy-focused data handling, comparable or better performance, accessibility features, support for Privacy Pass, and responsiveness. Cloudflare is leveraging its Workers platform to reduce hCaptcha's operational costs and has entered into a paid agreement with hCaptcha. The post also breaks down the usage of CAPTCHAs across different Cloudflare features, with Firewall and Bot Rules being the largest consumer, followed by IP Firewall and Security Level. It also mentions the use of CAPTCHAs by automated systems like Gatebot for DDoS mitigation.
More from the Website Security & Threat Management trail
- We tested our own WAF with frontier AI models. Here’s what we found
- When scanners miss the attack: how Cloudflare Client-Side Security protects storefronts
- Introducing automatic remediation policies with Cloudflare CASB
- Introducing context-aware vulnerability discovery and remediation with Cloudflare Managed Defense and OpenAI Daybreak Models
- Introducing Adaptive Intelligence: undermining the economics of every bot attack