Cloudflare Turnstile glossary
The Turnstile and Cloudflare-challenge terms that come up when you are integrating or debugging, defined precisely and without hedging.
The cf_clearance cookie, explainedThe cf_clearance cookie proves a client passed a Cloudflare challenge. What issues it, how long it lasts, how it is bound, and what invalidates it.How long is a Turnstile token valid?A Cloudflare Turnstile token is valid for 300 seconds and can be validated once. How expiry, siteverify, timeouts and turnstile.reset() actually work.Cloudflare Turnstile widget modesThe three Cloudflare Turnstile widget modes - managed, non-interactive, invisible: what each renders, how each is set, and how to identify one.Cloudflare Turnstile pre-clearanceTurnstile pre-clearance issues a cf_clearance cookie so solved visitors skip WAF challenges. Clearance levels, cookie lifetime, what is unconfirmed.Turnstile vs Cloudflare challengeTurnstile is a widget the site owner embeds; a Cloudflare challenge is an interstitial the edge serves. Who issues each, and what each token clears.Cloudflare Turnstile test sitekey and secret key referenceThe official Cloudflare Turnstile test sitekey and secret key values, what each does, and how to pair them so siteverify returns what you expect.Turnstile vs reCAPTCHAHow Cloudflare Turnstile and Google reCAPTCHA differ: challenge behaviour, privacy model, free tiers, integration details and migration notes.
Related
Automating a gate you own or are authorised to test?
// SolveGate clears Cloudflare Turnstile and WAF challenges through one REST call · first 1,000 solves free