Checking whether Cloudflare is active for a hostname

Know the domain’s expected nameservers and hosting origin. Choose the exact hostname and protocol to test, such as www.example.com over HTTPS. Keep origin access restricted according to the service’s supported design.

1. Open the Cloudflare zone and check its activation status. If it is pending, compare registrar nameservers with the assigned pair.
2. Open DNS records and inspect the target hostname’s proxy status. Proxied and DNS-only records have different behaviour even within the same zone.
3. Query public DNS and compare the result with the expected setup. A proxied hostname normally answers with Cloudflare edge addresses rather than exposing the origin address directly.
4. Load the hostname over HTTPS and inspect response information where useful. Cloudflare headers can support the diagnosis, but avoid relying on one header as the only proof.
5. Test email and other nonweb services separately because those records should not be proxied as ordinary website traffic.

The active zone, authoritative DNS and hostname proxy setting should agree. Confirm that the page is served correctly and that the origin certificate configuration works with the selected TLS mode.

If results differ by network, check cached DNS and old resolver answers. If a hostname is DNS-only intentionally, turning it orange is not a universal fix; unsupported protocols or mail can fail. Review the service requirements before changing proxy status.

• Connecting a hosted domain to Cloudflare without breaking email
• Using Cloudflare Under Attack mode during a web attack
• Moving DNS away from Cloudflare and removing a zone
• Changing the hosting origin behind an existing Cloudflare proxy

• Cloudflare: Proxy Status
• Cloudflare: Add Site