Cloudflare: "Checking if the site connection is secure" / "Verify you are human"
Last verified
Verify you are human by completing the action below. example.com needs to review the security of your connection before proceeding.What it means
This is a Cloudflare challenge page (also called an interstitial). It holds the request until the browser proves it is a real visitor. Older versions said "Checking if the site connection is secure"; current versions say "Verify you are human" and may show a Turnstile checkbox. The page title is usually "Just a moment...". Cloudflare's documentation says challenges evaluate client-side signals from the browser environment and that most visitors pass automatically.
A challenge requires JavaScript and a full browser. Cloudflare notes that challenge pages fail for non-HTML requests such as fetch, XHR or API calls, so an HTTP library receives the challenge HTML (often with status 403 or 503) instead of the content. Responses that are challenges carry the header cf-mitigated: challenge, which lets clients detect them.
For automation, a challenge means the owner wants to filter non-human traffic on that path. Solving or bypassing it programmatically defeats the owner's policy.
What it looks like
HTTP/1.1 403 Forbidden
Server: cloudflare
cf-mitigated: challenge
Content-Type: text/html; charset=UTF-8
<title>Just a moment...</title>Why it happens
- The owner set a WAF rule with a Managed, JS or Interactive Challenge action on the path.
- Bot Management or Super Bot Fight Mode assigned the request a likely-automated score.
- Under Attack mode is enabled site-wide.
- For people: JavaScript disabled, blocking extensions, VPN or proxy interference, unsupported browser or unstable network.
How to fix it
- For automation: detect the challenge (check for cf-mitigated: challenge) and stop; then look for the site's API or ask the owner for access.
- People stuck in a loop: update the browser, enable JavaScript, disable extensions, try a private window or another network, and temporarily turn off VPNs, per Cloudflare's troubleshooting guide.
- If it still loops, send the site owner the Ray ID, plus a HAR file if they ask.
- Site owners: skip challenges for API paths, verified bots and known partners with WAF skip rules; consider Turnstile pre-clearance for APIs.
- Site owners: check for rule combinations that cause challenge loops.
How to stop it recurring
Integrators: never point production automation at pages protected by challenges; agree an API or allowlisted access with the owner. Site owners: scope challenges to the paths that need them, exclude API endpoints that machines legitimately call, and monitor the challenge solve rate to spot false positives.
Official documentation: developers.cloudflare.com/cloudflare-challenges/challenge-types/challenge-pages. See all Cloudflare error messages.
Related errors
Definitions
- CAPTCHACAPTCHA (Completely Automated Public Turing test to tell Computers and Humans Apart) is a challenge-response m
- Cloudflare Bot ManagementCloudflare Bot Management is the set of Cloudflare features (Bot Fight Mode, Super Bot Fight Mode and the Ente
- Cloudflare TurnstileCloudflare Turnstile is Cloudflare's free CAPTCHA replacement: a widget that runs invisible browser checks, is
- User AgentA user agent is a string that browsers send with every HTTP request identifying the browser type, version, and
- Rate LimitingRate limiting is a technique that controls the number of requests a client can make to a server within a given
Quick answers
What does ""Checking if the site connection is secure" / "Verify you are human"" mean in Cloudflare?
This is a Cloudflare challenge page (also called an interstitial). It holds the request until the browser proves it is a real visitor. Older versions said "Checking if the site connection is secure"; current versions say "Verify you are human" and may show a Turnstile checkbox. The page title is usually "Just a moment...".
How do I fix ""Checking if the site connection is secure" / "Verify you are human""?
1. For automation: detect the challenge (check for cf-mitigated: challenge) and stop; then look for the site's API or ask the owner for access. 2. People stuck in a loop: update the browser, enable JavaScript, disable extensions, try a private window or another network, and temporarily turn off VPNs, per Cloudflare's troubleshooting guide. 3. If it still loops, send the site owner the Ray ID, plus a HAR file if they ask. 4. Site owners: skip challenges for API paths, verified bots and known partners with WAF skip rules; consider Turnstile pre-clearance for APIs. 5. Site owners: check for…
Retries and timeouts without writing the loop
Autonoly's HTTP Request node and browser steps have per-node retries, timeouts and continue-on-fail, so a transient 429 or 503 can back off instead of failing the run. It has no proxies or IP rotation: if a site blocks automated traffic, that block applies to Autonoly too.
Also see Error handling in workflows.