Free public URL tool

Cache/CDN Checker

Review public cache-control and common CDN header signals for a URL without claiming private infrastructure visibility.

Problem, cause, fix, verify

Problem

Cache and CDN discussions stall when nobody has captured the public response headers, final URL, third-party requests, and visible cache indicators for the exact page.

Audience

WordPress owners, agencies, developers, hosting support teams, and operations reviewers.

First check

Enter a public URL for the page whose cache and CDN signals you want to review.

Verify

Check page cache, object cache, CDN rules, plugin exclusions, WooCommerce cart and checkout bypasses, logged-in behavior, and invalidation after content changes.

Editorial trust

Published
Updated
Content type
Tools
Review editorial policy

Decision Support

Cache and CDN discussions stall when nobody has captured the public response headers, final URL, third-party requests, and visible cache indicators for the exact page.

For: WordPress owners, agencies, developers, hosting support teams, and operations reviewers.

Use The Tool

What this tool helps you check

Inputs

Enter a public URL for the page whose cache and CDN signals you want to review.

Output

The tool reports homepage cache-control, common CDN/cache header indicators, third-party request count, and resource-domain weight from the HTTP-lite result.

How To Read It

Visible cache headers help identify the next owner, but they do not replace host or CDN dashboard access. Treat missing or conflicting headers as evidence for a focused configuration review.

WordPress Fix Path

Check page cache, object cache, CDN rules, plugin exclusions, WooCommerce cart and checkout bypasses, logged-in behavior, and invalidation after content changes.

This reads public cache and CDN header signals. Missing headers can mean no signal was visible, not that no CDN exists.

Limitations

Use the result as planning guidance

  • Reviews public response headers only.
  • Missing CDN headers can mean no visible signal was exposed.
  • Does not inspect private CDN, hosting, or WordPress cache configuration.