About Is It Down?
When a site won't open, the first question is whether it is down or the problem is your own connection. This checker tries the site from our server, one step at a time. It looks up the IPv4 and IPv6 addresses through public DNS, opens a TCP connection to the port, trying the other of 80 and 443 if that fails, completes the TLS handshake and checks the certificate, then reads the HTTP answer.
The verdict is up, answering with an error, or down, along with the step where it broke: a name that doesn't resolve, a server that won't accept connections, a failed handshake or a 5xx error. If the site is up from here but not for you, look at your own network, DNS cache, proxy or firewall. If it's down here too, the failing step tells the owner where to start. Dig deeper with the SSL Certificate Checker or DNS Lookup.
How to use Is It Down?
- 1Enter the address
Type the domain or the full URL that won't open.
- 2Click Check
Our server tests DNS, the connection, TLS and HTTP in order.
- 3Read each step
Every step shows OK, a warning or a failure, with the details.
- 4Act on the verdict
Up here but not for you points to a local problem, while down here means the site needs fixing.
Why use Cubfile for this
- Four-step diagnosis
DNS lookup, TCP connection, TLS handshake and HTTP answer, in order.
- Both web ports
If the usual port doesn't connect, the other of 80 and 443 is tried.
- Certificate trust
A handshake that works with an untrusted certificate shows as a warning.
- IPv4 and IPv6
A and AAAA records are both looked up before connecting.