Retest the same public URL and preserve the result as the next baseline. If this is a business-critical route, request monitoring access rather than relying on a one-off check.

Open monitoring foundation

Loading CheckWebs…

Cloudflare website checks, fixes, and retesting.

Use public checks to separate origin problems from DNS, TLS, edge, cache, and redirect configuration.

Check a Cloudflare site

Start with these checks

DNS lookup

Review the published records that route visitors to the edge.

Run check

SSL checker

Validate the certificate and hostname presented to browsers.

Run check

Security headers

See the headers delivered on the public response.

Run check

Common public issues

A DNS update has not reached the resolver a visitor uses.
An edge redirect conflicts with application-level redirect rules.
A cache or security rule changes the public response unexpectedly.

Fix and retest focus

Record the final URL and response before changing edge rules.
Change one routing layer at a time so the cause stays observable.
Retest DNS, TLS, redirects, and the final public page together.

Good monitoring signals

DNS answers across resolvers
Certificate validity
HTTP status and final redirects
Public response headers

After the fix

Retest the same public URL and preserve the result as the next baseline. If this is a business-critical route, request monitoring access rather than relying on a one-off check.

Open monitoring foundation