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.

https://t1-tor-2.check-host.eu 的 HTTP 检测

Name: Check-Host https://t1-tor-2.check-host.eu 网站可用性与响应头检测
Author: Check-Host

高级设置

显示世界地图

Info Ping HTTP TCP UDP MTR DNS

HTTP 可用性深度监控探测 https://t1-tor-2.check-host.eu

获取固定链接 |

探针发起节点	通信链路验证	首字节耗时 (TTFB 延迟)	HTTP 状态码	解析获取的 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
Germany, Frankfurt am Main
Germany, Duesseldorf
Denmark, Glostrup Municipality
Spain, Bilbao
Finland, Helsinki
Finland, Helsinki
France, Gravelines
France, Paris
United Kingdom, London
Georgia, Tbilisi
Hong Kong, Hong Kong
Croatia, Zagreb
Hungary, Budapest
Indonesia, Jakarta
Israel, Petach Tikwa
Israel, Netanja
India, New Delhi
Iceland, Reykjavik (Miðborg)
Italy, Como
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, Moscow
Saudi Arabia, Riyadh
Singapore, Singapore
Tor, Onion
Tor, Onion
Tor, Onion
Turkey, Istanbul
Taiwan, Taipei
United States, Miami
United States, Dallas
United States, Kansas City
United States, Dallas
South Africa, Johannesburg

面向现代 Web 架构架构的全球无死角 Uptime 监控

配备重型火力的 Check-Host HTTP 探针组件，赋予运维先锋们洞穿全球网络阻碍，即时获悉服务器运转全貌的实战能力。其核心机制摒弃本地狭隘网络污染，以并发形态指挥跨越四大洋的独立节点，向目标发起最原生的 HTTP(S) 数据拉取。这种剥离地理位置过滤及本地网络劫持的物理级别检测，能极其客观地反映全球各地上网访客真实触达该站点的连通率与健康度。

解构 HTTP 状态异常码与后方应用服务崩溃诊断

由网关引擎返还的 HTTP 状态标头代码，是剖析站点健康度的一把钥匙。"200 OK" 这一无虞标志代表前端服务器精神饱满。然则，若反馈充斥着冰冷的 "403 Forbidden"，预示着访客可能遭遇到苛刻的 Web 应用防火墙 (WAF)、残酷的区域访问拦截 (Geo-Blocking) 或恶意 DDoS 流量清洗中心的排斥。更为凶险的是，一旦暴露 "502 Bad Gateway" 亦或 504 错误，则是后勤设施全线溃逃的确凿证据——后端的数据库负荷宕机，或者源站进程崩溃已致边缘代理无功而返。

锁定页面加载体验致命缺陷：TTFB 首字节时间解析

不仅限于是否存活的二元逻辑，本探测器深潜页面生成的核心反应装甲——“首字节时间 (Time to First Byte, TTFB)”。这根秒表从请求发起一直掐至服务器吐出第一块数据响应报文。拖沓不堪的绝望级 TTFB 数值，冷血地扯下了后端代码低效执行、数据库查询严重锁死、或者缓存加速系统 (Redis/Memcached 机能缺失) 形同虚设的遮羞布。病态的 TTFB 不仅扼杀前端交互体验，更会招致 Google 等主流搜索引擎 (核心网页指标 CWV) 极具破坏性的降权暴击。

拒绝跳转迷宫并直击源头 SSL/TLS 加密鉴权

为了保障诊断报告具备工程级的公信力，系统检索引擎设计理念坚拒随波逐流——默认禁绝跟随狡猾的多重重定向 (如连环 301 跳转深渊)。这一强横的拦截机制成功避免 CDN 负载均衡网关施放的安全幻境干扰真实测量的落点标尺。同时，斩断跳转直接迫使驻守在流量终点入口的边缘节点 (Edge Node) 交出第一手 TLS/SSL 握手数字证书。这让安防排查人员清清楚楚地查明该链路的密码学认证是正常下发，还是已堕入证书逾期、密钥链残缺的瘫痪状态。