Compare edge behavior
See whether different regions return the same cache, CDN, and routing headers before users notice inconsistencies.
Website diagnostics
Enter a URL to inspect important response headers across our included countries.
Enter a URL to compare response headers from included countries.
See whether different regions return the same cache, CDN, and routing headers before users notice inconsistencies.
Review HSTS and cross-origin headers from each region to confirm the expected protections are actually being served.
Validate new CDN rules, header transforms, and origin changes with the same regional probe flow used by URL Check.
Enter a full URL such as https://example.com and run the check. AccessTest fetches the page from each selected region and extracts key response headers for comparison.
Use this after CDN changes, reverse proxy configuration updates, cache rule deployments, or security policy rollouts where regional drift can be hard to spot.
If one country shows different cache, server, HSTS, or CORS headers, the issue is usually in edge configuration, origin routing, or a staged deployment rather than the browser itself.
It loads the target URL from the selected regions and surfaces key response headers such as server, content-type, cache-control, HSTS, CORS, and redirect location values.
Different edges or origin paths can inject different headers by region, which may affect caching, security policy, and browser behavior.
Yes. It uses the same URL Check pipeline, so you can review the final URL and the headers returned for that regional request flow.
The page focuses on practical diagnostics: server, content-type, cache-control, CDN cache indicators, HSTS, CORS, and redirect location when present.