QUICK DIAGNOSTIC
Website Status Checker
Enter a public website address to run a safe, one-off diagnostic check: HTTP status, DNS resolution, SSL/TLS validity, redirects, and response time. Nothing is published or attached to your identity, and this tool never scans internal or private networks.
Erriscope Editorial Team
Last reviewed: 2026-10-05
We check public websites only — no internal networks, IP addresses, or localhost. Requests are rate-limited to prevent abuse.
What this checks
- HTTP status — whether the site responds, and with what status code.
- DNS resolution — whether the domain resolves to a public, reachable address.
- SSL/TLS — whether HTTPS is served correctly, when applicable.
- Redirects — how many redirects occur before the final response, up to a safe limit.
How to read your results
The four fields above map to four independent points of failure. A site can fail at any one of them while the others look completely normal, so read each result separately rather than relying only on the overall color.
HTTP status
A 2xx code such as 200 means the server handled the request normally. A 3xx means the request was redirected, so check the redirect count if it looks high. A 4xx means the request was rejected or the resource was unavailable. A 5xx means the server or an upstream service failed. For deeper diagnosis, use the relevant Erriscope HTTP error guide.
DNS resolution
“Resolved” means the domain name pointed to a public address that our server could reach at the moment of the check. If DNS resolution fails, the browser cannot reach the web server yet, so fix the DNS problem before changing application or TLS settings.
SSL/TLS
“Valid” means the certificate chain validates for the checked hostname and is not expired. This confirms certificate validity for the connection; it does not mean the site, account, or application is otherwise secure.
Redirects
Each redirect hop adds latency. One or two redirects can be normal, such as HTTP to HTTPS, but loops or long chains can fail and should be corrected so requests converge on one canonical URL.
What this check cannot prove
This is one independent request from the Erriscope server. It can confirm what our server observed at that moment, but it cannot prove that every region, ISP, CDN edge, account, API method, or product feature is healthy. Compare the result with the vendor's official status page and reports from your own users when diagnosing a widespread incident.
Frequently asked questions
Does this tool store or publish the URLs I check?
No. Each check is a one-off server-side request made when you submit it. Results are not published or indexed. See our Privacy Policy for details about the limited data retained for security and abuse prevention.
Why can this show a different result from another uptime tool?
Different tools probe from different networks, use different timeout and redirect rules, and may cache results for different periods. This checker reports what the Erriscope server observed at that moment from its own network location.
Can I check an internal, staging, or password-protected site?
No. The checker is limited to public websites reachable over the open internet. It rejects localhost, private IP ranges, internal networks, and direct IP targets to prevent abuse as a network scanner.
What does “SSL/TLS: valid” verify?
It verifies that the TLS certificate chain validates for the checked hostname and is not expired. It does not certify the website's content, application security, or overall configuration.
My check says the site is fine, but visitors say it is down. Why?
The issue may be regional, limited to a CDN edge, affected by DNS propagation, tied to a particular ISP, or limited to a specific feature or account. Compare multiple observations and the provider's official status page before concluding that the whole service is healthy.