Advanced Settings
Check Website Availability: Global HTTP Test from 50+ Locations
Enter a domain or IP address above to begin the global HTTP check.
Global HTTP & Website Availability Check
An HTTP check sends a GET request to a URL and records the response — status code, response time, and whether the connection completed. This tool runs that request from over 50 nodes at once, covering different continents, ISPs, and data centers. It goes through DNS, TCP handshake, and TLS negotiation the same way a browser does, so the result reflects what real users in those locations actually hit.
HTTP Status Codes & Availability
The response code tells you what the server returned. 200 means it answered. 403 means it answered but blocked the request. 502 means a proxy, load balancer, or edge cache returned an error before the request reached your origin. If status codes differ by region — 200 in Europe, 403 in Asia — you are likely looking at a WAF rule or geoblocking policy that varies by source IP.
Performance & TTFB (Time to First Byte)
Response time here is the total time from connection open to first byte received. High TTFB from specific regions usually means those nodes are hitting your origin directly rather than a CDN edge, or your CDN has no edge presence near that region. It can also point to backend slowness — slow queries, high load — that becomes more visible the further the node is from your server.
Redirects & Security Layers
Redirects are not followed automatically. A URL returning 301 records that 301 and stops — the redirect target is not checked. This lets you verify that HTTPS redirect rules are in place and that the chain is correct before testing the final destination separately. It also makes it easy to spot redirect loops, double-redirects, or cases where HTTP is not redirecting to HTTPS at all.