Check and diagnose CDN by URL

Online CDN check from multiple locations worldwide: DNS, redirect chain, TCP/TLS traceroute, edge IP, Anycast/Unicast, and response time for the specified URL.

URL

Providers

Countries

Cities

DNS

queued · 0/0 probes · 0 ms ·

Result

What does this check do?

Each selected probe runs the full chain independently: the hub does not resolve the domain centrally or share IP addresses between probes. This shows what a real user in that network actually gets:

which IPs each DNS resolver returns from that probe
for each resolved IP — TCP, TLS with the original SNI and HTTP with the original Host header
whether the actual remote IP of the connection matched the expected one
status, protocol, TTFB, certificate, cache headers and SHA-256 of the response body

How to read the result

This is a drill-down on top of regular monitoring, not a replacement for it. Different IPs from different resolvers, or the same Anycast IP across multiple cities, are not errors — this is expected CDN behaviour. What is worth comparing across probes is the status, certificate, body hash and timings.

Route context: GeoIPBoss enriches each responding hop with ASN, organization, geography, ISP, RIR and range owner. Not yet available: BGP path/communities, CDN node identification, HTTP/3, automated findings and comparison against a historical baseline.