Free individual check · without registration
Check whether HTTP and HTTPS arrive with and without www on a secure destination address. You will see HTTP status, forwards, certificate expiration and HSTS directly in the result.
The check relates to the domain homepages. Paths, query parameters and own ports are not taken over. Status and TLS are assessed separately.
| Variant | HTTP status | Final URL | Redirects | TLS test | Note: |
|---|
Check with the hosting provider whether the certificate for the specific host is issued and fully installed. example.com and www.example.com must both be covered if both are accessed via HTTPS. A forwarding only helps after the TLS connection setup. Also check the automatic renewal.
An unidentified expiration date is not proof of an expired certificate. The result distinguishes a confirmed TLS check from a non-retrievable host.
Select your preferred HTTPS address and align the other domain variants directly to it. For permanent diversions, 301 or 308 are common. After the change, also adjust internal links, sitemap and canonical URLs. Avoid chains like HTTP → HTTPS with www → HTTPS without www.
For a single underside path, use the HTTP status code checker. This HTTPS check compares the start pages of the four domain variants.
First, check DNS, accessibility, and firewall rules. Not every subdomain has to exist; if www is used, however, it needs a suitable DNS entry. A HEAD request can also be handled differently than a browser call. Compare the result with a normal page call and the server logs.
Determine the IP address of the domain It helps to narrow down DNS resolution.
Encryption and HTTP status are separate checks. A valid certificate does not make a missing landing page or a server error unproblematic. Check the final URL and fix the status error in application, routing or hosting.
HSTS instructs browsers to only call the domain via HTTPS in the future. A positive max-age value determines the validity period; max-age=0 removes the stored rule. Activate includeSubDomains only if all affected subdomains support HTTPS reliably. HSTS does not replace a functioning certificate renewal.
Technical basis: MDN to HSTS header.
It retrieves four domain variants with HTTP and HTTPS, each with and without www. It shows final HTTP status codes, forwardings, the TLS check status and available information about the certificate expiration and HSTS. CSV export is free of charge.
HTTPS is HTTP over an encrypted connection. This today uses TLS; the expression SSL certificate is still common. The checker evaluates the HTTPS connection, but does not replace a full TLS configuration or security test.
No. This check checks headers and connections of the domain variants. It does not load and render a complete website with its pictures, scripts and style sheets. Mixed content also requires checking these resources and the browser console.
Your browser can use a different DNS result, saved forwarding, or HSTS. Firewall rules and the handling of HEAD requests also differ. Compare the specific host, the final URL and the error mentioned in the result.
The initial answers may differ: one variant may forward, another may reply directly. Decisive are the desired final HTTPS address, a working TLS connection and a reachable landing page. The table shows the status after the redirects.
For the next check: Save this free tool in the browser as a bookmark (Ctrl+D or ➳D).
