Skip to content

fix: clarify Turnstile hostname management subdomain behavior - #29752

Merged
patriciasantaana merged 2 commits into
cloudflare:productionfrom
zeinjaber:fix/turnstile-hostname-management-clarity
Apr 27, 2026
Merged

fix: clarify Turnstile hostname management subdomain behavior#29752
patriciasantaana merged 2 commits into
cloudflare:productionfrom
zeinjaber:fix/turnstile-hostname-management-clarity

Conversation

@zeinjaber

Copy link
Copy Markdown
Collaborator

Summary

  • Clarifies that adding a root domain (e.g. example.com) automatically authorizes all its subdomains (www.example.com, shop.example.com, etc.)
  • Adds an explicit "Root domain" example alongside the existing "Specific subdomain" example
  • Rewords the "no wildcards" statement to clarify it means the * character is not accepted as input — not that there is no subdomain inheritance

Context

This was raised in an internal support chat where multiple agents were unsure whether adding a root domain covers subdomains. The current doc only shows a subdomain example (www.example.com) and the "no wildcards" statement is easily misinterpreted.

Testing

End-to-end testing was performed using a Cloudflare Worker deployed across three hostnames:

Test 1 — Root domain (zein.firewall.team) in allowed list:

Hostname Result
zein.firewall.team Widget loaded successfully
sub.zein.firewall.team Widget loaded successfully
test.zein.firewall.team Widget loaded successfully

Test 2 — Only subdomain (sub.zein.firewall.team) in allowed list:

Hostname Result
sub.zein.firewall.team Widget loaded successfully
zein.firewall.team Error 110200 (domain not authorized)
test.zein.firewall.team Error 110200 (domain not authorized)

Related

  • Internal Jira: SPM-3371

Rewrite the Subdomain behavior section to explicitly document that:
- Adding a root domain (e.g. example.com) automatically covers all subdomains
- Adding a specific subdomain restricts the widget to that subdomain and its children only
- Wildcard characters are not supported in the input field, but subdomain inheritance is automatic

Also adds a root domain example alongside the existing subdomain example, and a note
about using specific subdomains for narrower scope.

Addresses confusion reported by support agents (SPM-3371).
@github-actions

Copy link
Copy Markdown
Contributor

Hey there, we've marked this pull request as stale because there's no recent activity on it. This label helps us identify PRs that might need updates (or to be closed out by our team if no longer relevant).

@github-actions github-actions Bot added the stale label Apr 25, 2026
Comment thread src/content/docs/turnstile/additional-configuration/hostname-management/index.mdx Outdated
@patriciasantaana
patriciasantaana enabled auto-merge (squash) April 27, 2026 17:47
@patriciasantaana
patriciasantaana merged commit 2c00d3d into cloudflare:production Apr 27, 2026
8 checks passed
@github-actions
github-actions Bot deleted the fix/turnstile-hostname-management-clarity branch June 27, 2026 06:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants