Reachability
Check whether a domain or IP address is reachable over HTTPS and measure the response time.
| Field | Value |
|---|
About the Reachability checker
A domain can have perfectly correct DNS records and still be unreachable, due to a firewall blocking traffic, a server being down, or a misconfigured web server returning unexpected errors. This tool checks whether a domain or IP address is actually responding over HTTP and HTTPS, giving you a straightforward answer to "is this thing actually up right now" separate from whether its DNS configuration looks correct on paper.
How it works
DNSbyte sends a request to the domain or IP address and records whether a response was received, how long it took, and what HTTP status code came back. A successful response in the 200 to 399 range generally indicates the server is reachable and responding as expected, while a timeout, connection refused, or error status code points to a different kind of problem depending on which one occurs.
This check is intentionally separate from DNS record validity, since DNS can be entirely correct while the actual server behind it is offline, overloaded, or blocking the request.
Frequently asked questions
The DNS records look correct but this tool shows the domain as unreachable, what does that mean?
It means DNS is successfully telling clients where to find the server, but the server itself is not responding correctly when contacted, possibly due to it being offline, a firewall blocking the connection, or a misconfigured web server rejecting the request.
What does a timeout mean compared to a connection refused error?
A timeout usually means the request was sent but no response came back within a reasonable time, often because of a firewall silently dropping the traffic or severe network congestion. Connection refused means a response was received actively rejecting the connection, which usually indicates nothing is listening on that port at all.
Why might HTTP work but HTTPS fail, or the other way round?
This typically points to a configuration issue specific to one protocol, such as a web server correctly handling plain HTTP requests on port 80 but having a broken or missing SSL certificate setup on port 443, or a firewall rule that only permits one of the two ports through.
My site works fine when I visit it myself, why does this tool show it as unreachable?
Some firewalls and security configurations are set up to allow traffic from specific regions or known good sources while blocking others, which can cause a check run from a different location to behave differently than your own personal browsing session.
What status code should I expect for a healthy website?
A 200 OK is the most common healthy response, though redirects in the 300 range, such as 301 or 302, are also entirely normal and expected if the site redirects from HTTP to HTTPS or from a non-www to www address, or similar deliberate redirect setups.