When a website works for you but not for someone else, the cause is often one address among several. A domain can publish more than one A record for IPv4 and more than one AAAA record for IPv6, and each visitor's browser picks one. This check connects to the two web ports, 80 for plain HTTP and 443 for HTTPS, on every address your domain publishes, and shows the result for each address and port side by side.
What we check
- Addresses: the domain's A and AAAA records. We test up to four of each family; any more are counted and left out. A domain that points at a private or reserved address isn't contacted at all.
- Port 443: whether a connection opens. When it does, we start one TLS handshake to see the protocol version and whether the certificate names your domain, and we note the alert the server sends if the handshake fails.
- Port 80: whether a connection opens. When it does, we send one plain HTTP request for the home page and note the status and where a redirect points: only its scheme and host, never the path.
- IPv6: each AAAA address is tested the same way while our IPv6 connection is on; otherwise those rows say they weren't tested.
Nothing else is sent. A connection that opens is closed again straight away, and only these two ports are ever used.
Reading the result
Each row is one address, with a cell for each port:
- Open: the address accepted the connection. For port 443 the cell adds the TLS version; for port 80 it shows the redirect, or the status code when there isn't one.
- Closed: the address refused the connection, so nothing listens on that port.
- Doesn't answer: no reply within three seconds, usually a firewall that drops traffic silently.
- Unreachable: the network reported that the address can't be reached.
- Not tested: skipped, because IPv6 connections are off, the address was tested many times in the last minute, or the check ran out of time.
A good result has both ports open on every address, a working TLS handshake on 443, and a redirect from port 80 to an HTTPS address.
Common problems
The most serious finding is an address where port 443 doesn't answer while the others work: some visitors reach your site and others don't. It is usually a leftover record from a previous host. A site that works over IPv4 but not over IPv6 is the next most common, often because a firewall has IPv4 rules but no IPv6 rules. A closed port 80 is less harmful, but it strands visitors and tools that start with plain HTTP, so we suggest opening it with a redirect. A failed handshake on an open port 443, or a certificate for another name, usually means one server in the set has a default or outdated configuration. Each of these has a guide linked from its finding.
Why it matters
Reachability problems on one address are easy to miss, because a reload can land on a working address and your own monitoring may always use the same one. Browsers on IPv6 networks try IPv6 first, so a broken AAAA record slows down or blocks exactly the visitors on modern mobile networks. Checking every address and both families at once shows the whole picture in a few seconds.
Testing changes
After you fix a server or remove a stale record, wait for the record's old TTL to pass, then run the check again with the fresh option so the cached answer isn't used. Results are cached for a minute, and a site can be checked up to 20 times a minute in total, by everyone, so repeated checks of one site may be asked to wait briefly.
Using it with other tools
The DNS lookup shows the A and AAAA records behind each row. The SSL checker looks at the certificate in depth, and the IPv6 test checks IPv6 for the website, mail servers and nameservers together. The IP lookup shows who runs an address.
Privacy
We record the domain in your usage history, as with every domain check. The result keeps the addresses, the port states, the TLS version and the redirect's scheme and host. The page we fetch on port 80 is discarded.