Skip to content

Commit c17ffb4

Browse files
revert
1 parent 87f0d3a commit c17ffb4

File tree

2 files changed

+4
-2
lines changed

2 files changed

+4
-2
lines changed

src/content/docs/turnstile/concepts/hostname-management.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -61,6 +61,6 @@ If the widget is embedded on a hostname not listed, it will display an error mes
6161

6262
## Optional hostname validation (Enterprise only)
6363

64-
For Enterprise customers, optional hostname validation adds an additional layer of security. When enabled, this feature ensures that Turnstile widgets can load on any hostname.
64+
Customers with Enterprise Bot Management or Enterprise Turnstile can have the optional any hostname validation entitlement.
6565

66-
Hostname validation is not enabled by default and must be explicitly configured in your account settings.
66+
By default, a widget requires at least one hostname to be entered. With this entitlement, you can create and use a widget without entering any hostnames for the widget. Contact your account team to enable this entitlement.

src/content/docs/turnstile/concepts/pre-clearance-support.mdx

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,8 @@ For Enterprise customers eligible to toggle off domain checks, Cloudflare recomm
2424
Clearance cookies only support zones that are orange-clouded.
2525
:::
2626

27+
Refer to the [blog post](https://blog.cloudflare.com/integrating-turnstile-with-the-cloudflare-waf-to-challenge-fetch-requests) for more details on how pre-clearance works with WAF.
28+
2729
## Pre-clearance level options
2830

2931
- **Interactive (High)**: Allows a user with a clearance cookie to not be challenged by Interactive, Managed Challenge, or JavaScript Challenge Firewall Rules

0 commit comments

Comments
 (0)