For Workers & Pages, what is the name of the domain?
What is the issue or error you’re encountering
report test failed
If you’re seeing a 403 error without Cloudflare branding, this is always returned directly from the origin web server, not Cloudflare, and is generally related to permission rules on your server. The top reasons for this error are:
- Permission rules you have set on the origin web server (in the Apache .htaccess for example)
- Mod_security rules
- IP deny rules. You need to make sure that Cloudflare’s IP ranges
aren’t being blocked
Cloudflare-specific information
Cloudflare will serve 403 responses if the request violated either a default WAF managed rule enabled for all orange-clouded Cloudflare domains or a WAF managed rule enabled for that particular zone. Read more at WAF Managed Rules.
If you’re seeing a 403 response that contains Cloudflare branding in the response body, this is the HTTP response code returned along with many of our security features:
- WAF Custom or Managed Rules with the challenge or block action
- Security Level, that is set to Medium by default
- DDoS Protection, that is enabled by default on zones onboarded to Cloudflare, IP applications onboarded to Spectrum, and IP Prefixes onboarded to Magic Transit
- Most 1xxx Cloudflare error codes
- The Browser Integrity Check
- Validation Checks
Cloudflare will also serve an unstyled 403 error page in the following case. There errors are not logged, as they occur early in Cloudflare’s infrastructure, before the configuration for domains has been loaded.
- SNI mismatch: a 403 error is returned if there is a mismatch caused by the client sending a different host to the SNI