Skip to main content
All WP Cloud instances use Cloudflare DNS by default for fast propagation and global resilience. From PanelAlpha, you can manage DNS records and configure Cloudflare’s proxy and security features directly.

Accessing Cloudflare Settings

From your instance, go to Advanced → Cloudflare.

DNS Management

Click Manage Records to open the DNS Zone Editor for this instance’s domain. You can add, edit, or delete DNS records (A, CNAME, MX, TXT, etc.) directly from here. To activate Cloudflare’s proxy for the domain, click Activate next to the DNS management section.

Settings

Purge Cache

Clears Cloudflare’s cached files, forcing it to fetch fresh content from the origin server on the next request.
Purging the Cloudflare cache may temporarily increase load on your origin server and degrade performance while the cache rebuilds.

Development Mode

Temporarily bypasses Cloudflare’s cache so you can see changes on your origin server in real time. Useful during active development or troubleshooting.
Development Mode does not purge existing cached files. After disabling it, purge the cache manually to ensure visitors see the latest content.

Browser Integrity Check

Evaluates HTTP headers from visitor browsers for signs of threats. If a threat is detected, a block page is delivered instead of your site content. Enabled by default.

Security Level

Controls which visitors receive a Cloudflare challenge page based on their threat score. The default level is Medium, which balances security and accessibility.
LevelDescription
Essentially OffOnly challenges the most severe threats
LowChallenges visitors with moderate threat scores
MediumDefault — balances security and user experience
HighChallenges visitors with lower threat scores
I’m Under AttackChallenges all visitors — use only during active attacks

Edge Cache and Cloudflare Proxy

Do not run WP Cloud Edge Cache and Cloudflare Proxy caching simultaneously. They use separate caching layers that conflict with each other, causing inconsistent content, broken pages, or slower performance. Disable Edge Cache if you want to use Cloudflare’s caching, or keep Cloudflare in DNS-only mode if you want to use Edge Cache.
Cloudflare’s WAF remains active regardless of your caching configuration.