---
title: X
description: Knowing you are behind Cloudflare was never the interesting part — you already knew that. Paste a URL and WatchFor requests it three times from every probe…
canonical: https://watchfor.io/changelog/2026-09-10-global-cdn-analyzer
---

[All updates](/changelog/page/3#2026-09-10-global-cdn-analyzer) ⚡ Improved Sep 10, 2026 · v 7.2.4

# CDN Checker is now a global CDN analyzer

Knowing you are behind Cloudflare was never the interesting part — you already knew that. Paste a URL and WatchFor requests it three times from every probe location, then tells you whether it is really being cached, which edge answered where, whether traffic is steered by anycast or by DNS, and which regions behave differently. Detection recognises over sixty providers — hosting platforms like Hostinger, Kinsta and Wix included — with the source behind every claim. You get a graded report, a clickable world map, and a guide to what HIT, MISS and EXPIRED mean. Still free, at /cdn-checker.

## How it works

Paste a URL and WatchFor requests it three times from every probe location. Three requests tell a cold cache from a broken one: MISS, then HIT, HIT means the edge is warming up, while three misses in a row means it is not caching that URL at all.

## What the report shows

- The provider, with the evidence. Response headers, the CNAME chain, the network the edge address belongs to. Where a platform sits in front of a CDN, both are named: a Kinsta site reads as Cloudflare via Kinsta.

- The edge in each region: which edge location answered, its time to first byte and its cache result.

- How traffic is routed: one anycast address everywhere, or DNS handing out different addresses per region.

- Findings in plain words, with the locations they affect, such as persistent cache misses in one region, and what to do about it.

- A letter grade and a world map coloured by latency. Click a location to see its three requests.

- A short guide to cache statuses such as HIT, MISS and EXPIRED.

## An example

You put a CDN in front of shop.example.com and want to know it is really working. The report shows HIT on the second and third request almost everywhere, but three misses in São Paulo. Visitors there are served from your origin every time, and the finding says so, with the request sequence as proof.

## Use it

Free at [/cdn-checker](/cdn-checker), no account needed. Test the URL you care about, such as /static/app.js , not just the domain. To keep watching it, add a [CDN monitor](/docs/monitors/performance#cdn).

Since then: [a warm cache no longer grades worse than a cold one](/changelog/2026-09-23-cdn-grade-warm-cache).

Share this update

---

Canonical page: https://watchfor.io/changelog/2026-09-10-global-cdn-analyzer · Site guide: https://watchfor.io/llms.txt