CoreSpeed Cloudflare Validation and Troubleshooting Checklist

Use this checklist after a nameserver migration, O2O activation, origin change, or routing update.

DNS delegation

dig NS example.com @1.1.1.1
dig NS example.com @8.8.8.8
dig example.com +trace

Confirm:

• The expected authoritative nameservers are returned.
• No previous nameservers remain.
• No stale DS record is causing SERVFAIL.
• Apex and www resolve as expected.

Cloudflare requires the registrar nameservers to exactly match the assigned values, with no additional nameservers listed.

Critical DNS records

Check:

dig example.com A
dig www.example.com CNAME
dig example.com MX
dig example.com TXT
dig _dmarc.example.com TXT

Confirm email, validation, and delegated services continue to resolve.

Proxy status

In Cloudflare DNS, verify the primary web records are Proxied.

A DNS-only web record bypasses Cloudflare and therefore bypasses the CoreSpeed Worker, cache, and edge security layers.

O2O

For customer-owned Cloudflare accounts:

• Confirm the record is a CNAME, not an A record.
• Confirm the CNAME is proxied.
• Confirm SiteCare created the corresponding custom hostname.
• Confirm there are no conflicting records.
• Confirm SiteCare sees cf-connecting-o2o: 1 at the provider layer.
• Review customer-zone Workers, redirects, WAF, and cache rules.

TLS

Confirm:

• The browser receives a valid certificate.
• The hostname appears on the certificate.
• HTTP redirects correctly to HTTPS.
• There are no redirect loops.
• The origin accepts requests from Cloudflare.
• The configured minimum TLS version supports the organization’s required devices.

Headers

curl -I https://example.com/

Review:

• HTTP status
• CF-Ray
• CF-Cache-Status
• Location
• Cache-Control
• Set-Cookie
• Unexpected server or proxy headers

The CF-Ray header identifies the Cloudflare data center that processed the request and can help correlate a request with Cloudflare or SiteCare logs.

Dynamic routes

Verify that these are not improperly cached:

• /wp-admin/
• /wp-login.php
• Checkout and cart routes
• Account pages
• Form submissions
• Authenticated application pages
• Personalized content

A cached login or session page can cause missing cookies, failed authentication, or CSRF errors.

Escalation information

When reporting a Cloudflare-related issue to SiteCare, include:

• Exact URL
• Timestamp and timezone
• Expected behavior
• Actual behavior
• Screenshot
• HTTP status
• CF-Ray value
• Whether the request was authenticated
• Whether the problem occurs in a private browser
• Recent DNS, Worker, WAF, redirect, or cache changes

This gives SiteCare enough information to trace the request through the Cloudflare and CoreSpeed layers.