1. Nguồn
Kiểm tra HTTP phía máy chủ trực tiếp. Kết quả xác định nguồn gốc của bằng chứng.
The Novaverb website status checker sends one live server-side HTTP request to the address you submit and reports the status code, response time and final URL as a single point-in-time result.
Bảng trực tiếp gồm các trang web đã chọn, được nhóm theo phản hồi máy chủ đo được gần đây nhất. Mỗi trạng thái đến từ một lượt kiểm tra phía máy chủ đã lưu; các miền do khách truy cập gửi lên không bao giờ được công bố ở đây.
Không có trang nào khớp với tìm kiếm của bạn.
A website status checker is a tool that requests a web address and reports whether the server answered. The Novaverb version makes one live server-side HTTP request and returns the status code, the response time and the final URL. The result is a one-time check, not a service that keeps watching the site.
The website status checker checks a single response: the HTTP status code, the time the request took in milliseconds, the final URL after any redirects and the time of the check. The analysis rates the response time as fast, acceptable or slow, and notes a redirect on entry when the final URL differs from the address submitted.
The website status checker is for site owners who just heard the site is down and want a reading from outside their own network, developers confirming that a deploy answers publicly, support staff checking a customer report, and agencies verifying that a client address returns the expected status before a campaign starts.
A website status check separates a problem on your own connection from a problem on the server. When a page fails to load for you, one request from another network shows whether the server replies at all and with which status class, which tells you whether to look at your own device or at the site.
The website status checker works by requesting the exact public address once, through a safety check that also rechecks every redirect destination. The final response is then classified by its status class as healthy, reached but needing review, or failed. The submitted check is kept as one evidence sample, with its timestamp and final URL attached.
Enter the exact public address you want to reach into the website status checker, as a bare domain or a full URL. A stable page whose status reflects the site works best. A private host is refused, and a page that requires login usually returns 401 or 403 to an anonymous request, which reads as reached, not healthy.
yourdomain.comBất kỳ hình thức địa chỉ công khai nào cũng hoạt động. http hoặc https, có hoặc không có www, chỉ tên miền hay một đường dẫn đầy đủ - chúng tôi chuẩn hóa cho bạn.https://yourdomain.com/healthMột URL công khai ổn định mà trạng thái HTTP của nó phản ánh đáng tin cậy lên hoặc xuống.A page requiring loginMột trang yêu cầu xác thực thường trả về 401/403 cho một lượt thăm dò ẩn danh, nên trang đó vẫn truy cập được nhưng thuộc diện cần xem xét chứ không phải khỏe mạnh.Expecting continuous uptime historyĐây là một lần kiểm tra tại một thời điểm; giám sát liên tục là tính năng dành cho không gian làm việc đã kết nối.A website status checker report contains a verdict badge, the HTTP status, the response time for the one live request, the requested and final URLs, the time of the check and any probe error. An analysis panel adds findings, and a history panel shows the stored check for the URL. Selected public-radar sites also show scheduled samples.
Read a website status checker result from the verdict badge. Healthy response means the final status was 2xx or 3xx. Reached, needs review means the server answered with a 4xx error. No usable response means nothing came back or the server returned 5xx. A final URL marked moved shows the address redirected, which is not downtime.
Một lần yêu cầu thành công chỉ là một lát cắt, nên việc theo dõi mới có ích. Novaverb dò các website trong radar khả dụng công khai theo lịch cố định, nên những site đó có chuỗi mẫu thật. Với mọi URL khác, trang này chỉ hiển thị lần kiểm tra bạn vừa chạy: chúng tôi không bao giờ đăng lại lần kiểm tra của người khác.
It is not a 24/7 global uptime SLA, a browser performance test or real-user monitoring. For scheduled checks, alerts, multi-location monitoring and long-term reports, explore Novaverb Uptime Monitor.
Mỗi lượt kiểm tra là một yêu cầu từ Novaverb. Một phản hồi chứng minh rằng lượt thăm dò đó đã tới được máy chủ tại thời điểm đó, chứ không chứng minh rằng mọi khách truy cập đều có thể tới được.
The website status checker gets its data from one live server-side HTTP request sent from Novaverb infrastructure at the moment you submit. The status, timing and final URL belong to that request alone. For the selected sites on the public availability radar, the page also shows stored samples that Novaverb collected for those sites on a fixed schedule.
The website status checker does not tell you the site's uptime. Each result is one server-side request, so a site that is down for three minutes an hour will usually pass. The result is not a global uptime SLA, a browser performance test or proof that every visitor can reach the site.
A website status checker result proves that one address answered one HTTP request at one moment, and with which status class. That supports the conclusion that the server was reachable from the probe at that time. Availability over a period cannot be concluded, and a site that answers here can still be failing for visitors on another network.
Kiểm tra HTTP phía máy chủ trực tiếp. Kết quả xác định nguồn gốc của bằng chứng.
Mỗi kết quả là một yêu cầu từ phía máy chủ. Đây không phải là SLA thời gian hoạt động toàn cầu, bài kiểm tra hiệu suất trình duyệt, hoặc bằng chứng rằng mọi khách truy cập đều có thể truy cập trang web.
Sử dụng phát hiện để xác minh một vấn đề, sau đó kết nối một không gian làm việc khi bạn cần lịch sử, giám sát hoặc phân tích toàn bộ trang web.
The website status checker applies RFC 9110, the IETF specification for HTTP semantics, which defines what each status class means. The classification follows that specification and not a house interpretation. A 301 is therefore reported as reachable, because a redirect is a successful response that names another location, and calling it downtime would misreport the server.
Đọc trạng thái cuối cùng và phân biệt các phản hồi 2xx/3xx khỏe mạnh, 4xx có thể xem xét và 5xx thất bại.
Đọc thông số kỹ thuậtVerify a website status check by requesting the same address from a different network, for example a phone on mobile data, and by using a command line HTTP client to print the status line. If both agree with the report, the reading holds. If they differ, the difference lies between network paths, which a single probe cannot see.
A typical website status checker finding is a bare domain entered without www that returns a healthy response while the final URL reads moved and shows the https www address. The analysis notes a redirect on entry beside the response time. The site answered, and the entry also reveals which address the domain resolves to in the end.
The website status checker is free and needs no account. Any public address can be checked from the form, and the result appears on the page. A free Novaverb account is needed for what one request cannot provide: checks that run on a schedule and an alert when the site goes down.
A Novaverb workspace adds scheduled checks and alerts to the website status checker, turning a single reading into a pattern you can review. Site Trust is the product that continues the job: a bounded scorecard for captured site trust signals, headers and supported external probes, in the same workspace area as the uptime monitor.
A free website status check is not enough when you need to know about outages you were not present for. One request cannot catch a failure overnight, show a pattern across many samples or compare locations. Those need checks that repeat on a schedule with alerts, which belong to a connected workspace and not to this page.
After running the website status checker, act on the class of the result. For no response or a 5xx, check the origin server, DNS and TLS certificate, then application logs and recent deployments. For a 4xx, confirm the address and whether the page needs login. For a healthy result, run the check again later and compare.
Deeper free tools pair with the website status checker once the site answers. The Server Response Time Checker breaks one request into DNS lookup, TCP connect, TLS handshake and time to first byte. The Website Performance Test compares response timing from available probe locations. The HTTP Status & Redirect Checker traces every hop to the final URL.
People ask what the website status checker checks, whether it is an uptime SLA or a monitoring service, what the status codes mean, why the final URL differs from the one entered, what a good response time is, whether a passing check means every visitor can reach the site and what to do about a 5xx error.
Each run sends one live HTTP request from Novaverb infrastructure and reports the HTTP status code, response time, and final URL after redirects, then stores a history of these measured checks over time.
No. Each check is a single server-side HTTP request from one location. It indicates whether the site responded to that request; it is not a contractual uptime SLA or proof that every visitor everywhere can reach the site.
A 200 means the request succeeded. A 3xx is a redirect (the final URL shows where it landed), 4xx indicates a client error like 404 not found, and 5xx signals a server-side error worth investigating immediately.
Because it follows redirects and reports where the request ultimately resolved. If you entered an HTTP or non-www address, the final URL reveals your canonical HTTPS or www destination, which is useful for spotting redirect chains or loops.
One request cannot establish a universal good threshold because distance, caching and page behavior differ. Compare repeated checks for the same URL from the same probe; a sustained rise is evidence worth investigating.
The monitor repeatedly records status, response time, and final URL to build an availability history. The performance and speed tests break one request into DNS, TCP, TLS, and TTFB stages for deeper diagnosis rather than ongoing tracking.
No. It confirms one location got a response at one moment. Regional network issues, DNS problems, or per-user routing could still block some visitors, so treat a passing check as a strong signal, not universal proof.
Frequently enough to catch outages before customers do; many teams check every few minutes for critical sites. More frequent checks build a denser history, making it easier to correlate slowdowns and failures with deployments or traffic spikes.
A 5xx means your server failed to fulfill the request. Check application logs, database connectivity, and recent deployments, and confirm the origin is running. Recurring 5xx responses in the history point to instability rather than a one-off blip.
A crawler can only process a page when its request succeeds. Repeated timeouts or server errors reduce successful retrieval; only that crawler's own reporting can confirm how a specific search engine experienced the site.