Ryan Sullivan

Use this checklist after a nameserver migration, O2O activation, origin change, or routing update.DNS delegationdig NS example.com @1.1.1.1 dig NS example.com @8.8.8.8 dig example.com +traceConfirm...

CoreSpeed can preview a migrated website through its real domain before the public website is moved to the new origin.Preview architectureDuring preview: Public traffic continues to the existing pr...

CoreSpeed uses a custom Cloudflare Worker rather than relying only on Cloudflare’s default static-asset cache.Cache layersThe page-cache Worker uses two Cloudflare services:Cache APIThe Cache API s...

CoreSpeed uses Cloudflare Workers as middleware in front of the WordPress origin.For this architecture, a Worker Route is more appropriate than a Worker Custom Domain because WordPress remains the ...

In an O2O configuration, requests pass through both the customer’s Cloudflare zone and SiteCare’s Cloudflare zone.Cloudflare generally applies customer-zone settings first. Customer settings can ov...

This process applies when the customer retains its own authoritative Cloudflare account.O2O request flowVisitor ↓ Customer-owned Cloudflare zone ↓ SiteCare Cloudflare for SaaS zone ↓ CoreSpee...

Not every DNS record should pass through the Cloudflare reverse proxy.Proxied recordsCloudflare can proxy A, AAAA, and CNAME records used for HTTP or HTTPS traffic.When a record is proxied: Visitor...

This process applies when SiteCare will host the authoritative Cloudflare zone for CoreSpeed.1. Inventory the existing DNS zoneBefore changing nameservers, provide SiteCare with an export or comple...

CoreSpeed uses resources that exist at both the Cloudflare account level and the individual zone level.Cloudflare account-level resources can include Workers, KV namespaces, account members, lists,...

CoreSpeed supports two Cloudflare configurations.Option 1: SiteCare-managed Cloudflare zoneThe domain’s authoritative nameservers point to a zone in SiteCare’s Cloudflare account.SiteCare manages: ...