检查网站 https://nl-eyg-ghosted.check-host.eu
| 位置 | 结果 | 时间 | 代码 | IP 地址 |
|---|---|---|---|---|
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
|
||||
Denmark, Glostrup Municipality
|
||||
Spain, Madrid
|
||||
Finland, Helsinki
|
||||
|
Finland, Helsinki
|
||||
France, Gravelines
|
||||
|
France, Paris
|
||||
United Kingdom, London
|
||||
Hong Kong, Hong Kong
|
||||
Croatia, Zagreb
|
||||
Hungary, Budapest
|
||||
Indonesia, Jakarta
|
||||
India, New Delhi
|
||||
Iceland, Reykjavik (Miðborg)
|
||||
Italy, Como
|
||||
Lithuania, Pilaite
|
||||
Latvia, Riga
|
||||
Moldova, Chisinau
|
||||
Netherlands, Amsterdam
|
||||
|
Netherlands, Amsterdam
|
||||
|
Netherlands, Amsterdam
|
||||
|
Netherlands, Eygelshoven
|
||||
Qatar, Doha
|
||||
Romania, Bacău
|
||||
|
Romania, Bucharest
|
||||
Serbia, Belgrade
|
||||
Singapore, Singapore
|
||||
Taiwan, Taipei
|
||||
United States, Miami
|
||||
|
United States, Dallas
|
||||
|
United States, Kansas City
|
Global HTTP & Website Availability Check
HTTP 检查是一种用于跟踪基于 Web 的服务的可用性、性能和可靠性的实践。它涉及向目标 URL 或 IP 端点发送全球请求，以确保其为最终用户正常运行。我们的系统不跟踪 301/302 跳转。
HTTP Status Codes & Availability
The tool reports precise HTTP response codes (e.g., 200 OK, 403 Forbidden, 502 Bad Gateway) returned by your server. This helps identify regional geoblocking, WAF (Web Application Firewall) misconfigurations, or edge-cache failures that might be preventing specific countries from accessing your application.
Performance & TTFB (Time to First Byte)
Beyond simple uptime, the HTTP check measures total connection time and Time to First Byte (TTFB). High latency values across specific regions indicate a lack of CDN (Content Delivery Network) caching or overloaded backend database queries, severely impacting your site's Core Web Vitals and SEO rankings.
Redirects & Security Layers
Our engine intentionally does not automatically follow 301/302 redirects. This raw output behavior allows network engineers to inspect exact redirect chains, verify SSL/TLS handshake success, and ensure that security policies are properly enforced at the edge layer before traffic reaches the origin server.