How do I check if a website is down for everyone?

Enter the website URL into the HTTP check tool. Results from 50+ global nodes will show whether the site returns a successful response (HTTP 200) or errors from each location, confirming whether an issue is global or regional. If all nodes report failure, the site is down for everyone.

What is TTFB and why does it matter?

TTFB (Time to First Byte) is the time from when a request is sent to when the first byte of response is received. It reflects server processing time plus network latency. High TTFB from specific regions often means those nodes are bypassing your CDN and hitting the origin server directly, or that your CDN has no edge presence near that region.

Why does my website show different HTTP status codes from different countries?

Different HTTP status codes by region usually indicate geoblocking policies, WAF (Web Application Firewall) rules filtering by source IP, or CDN edge nodes returning errors in regions where your service is not correctly configured. A 403 from Asia while Europe returns 200 is a common sign of geoblocking.

Does the HTTP check follow redirects?

No — redirects are intentionally not followed. A URL returning a 301 records that 301 and stops. This lets you verify that HTTPS redirect rules are in place, confirm the redirect chain is correct, and spot redirect loops or cases where HTTP is not redirecting to HTTPS.

HTTP Check for https://us-kan-tierhive.check-host.eu

Name: Check-Host https://us-kan-tierhive.check-host.eu Website Uptime and Header Check
Author: Check-Host

Advanced Settings

Show world map

Info Ping HTTP TCP UDP MTR DNS

Check website https://us-kan-tierhive.check-host.eu

Permanent link |

Location	Result	Time	Code	IP Address
Albania, Tirana
Australia, Sydney
Bosnia and Herzegovina, Novi Travnik
Bulgaria, Sofia
Canada, Montreal
Switzerland, Bern
Chile, Santiago
China, Hohhot
Germany, Nuernberg
Germany, Frankfurt am Main
Germany, Frankfurt am Main
Germany, Limburg
Germany, Frankfurt am Main
Germany, Duesseldorf
Denmark, Glostrup Municipality
Spain, Bilbao
Finland, Helsinki
Finland, Helsinki
France, Gravelines
France, Paris
United Kingdom, London
Georgia, Tbilisi
Greece, Athens
Hong Kong, Hong Kong
Croatia, Zagreb
Hungary, Budapest
Indonesia, Jakarta
Israel, Petach Tikwa
Israel, Netanja
India, New Delhi
Iceland, Reykjavik (Miðborg)
Italy, Como
Kuwait, Kuwait City
Lithuania, Pilaite
Latvia, Riga
Moldova, Chisinau
Netherlands, Amsterdam
Netherlands, Amsterdam
Netherlands, Amsterdam
Netherlands, Amsterdam
Norway, Oslo
Poland, Warsaw
Romania, Bacău
Romania, Bucharest
Serbia, Belgrade
Russia, St Petersburg
Singapore, Singapore
Turkey, Istanbul
Taiwan, Taipei
United States, Miami
United States, Dallas
United States, Kansas City
United States, Dallas
South Africa, Johannesburg

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.