HTTPS checker

What is checked, separately

Two independent requests: one to the plain http:// address, one to https://. They are reported separately because a site can be reachable on one and not the other, or reachable on both but never actually sending visitors from the insecure one to the secure one.

Why "HTTPS reachable" and "redirects to HTTPS" are different questions

A site can have a perfectly valid HTTPS setup that visitors never reach, if nothing ever sends a plain-HTTP visitor there - someone typing the bare domain, or an old link without a scheme, stays on HTTP indefinitely. The redirect is what actually protects a visitor who did not think to type https:// themselves.

What a healthy result looks like

HTTP reachable (so the redirect can happen at all), HTTPS reachable, and HTTP redirecting to HTTPS - ideally with a 301 rather than a 302, so the redirect itself is understood as permanent.

Related tools

See the HTTPS redirect checker for the actual hop-by-hop chain, and HSTS checker for whether the browser is told to skip HTTP entirely on future visits.