SSL certificate and HTTPS checker
Is your page on HTTPS, with a certificate that is not about to expire, and HSTS?
- Checks your page
- Reads:Server response
- 3 rules
- Last updated
What we keep
The result appears here
Enter your page’s address and press “Check the page”. This is what the tool runs on it:
- Page without HTTPSnot started
- TLS certificate about to expirenot started
- HTTPS without HSTSnot started
What it checks
- That the page's final address, after its redirects, starts with
https:. Local development addresses are left out. - That the certificate the server presented has not expired, and does not end within 14 days, or within a third of its lifetime when that is shorter.
- That an HTTPS page sends
Strict-Transport-Securitywith amax-ageabove zero, written as RFC 6797 asks, so browsers keep to HTTPS on later visits.
Example
HTTP/1.1 200 OK Content-Type: text/html; charset=utf-8
HTTP/1.1 200 OK Content-Type: text/html; charset=utf-8 Strict-Transport-Security: max-age=31536000; includeSubDomains
How to fix
- Install a TLS certificate. Let's Encrypt's certificates are free, and renewal tools such as Certbot renew them by themselves.
- Redirect every HTTP request to its HTTPS address, with a permanent redirect (301).
- Keep renewal automatic, and test it: with Certbot,
certbot renew --dry-runtries a renewal without changing anything. - Then send HSTS on your HTTPS responses, for a year:
includeSubDomainscovers every subdomain: keep it once they all work over HTTPS, or start without it.
Strict-Transport-Security: max-age=31536000; includeSubDomainsFAQ
Because the address and the certificate come from the connection itself, which an example on a page cannot show: the check reads them from your server when you run it. The example shows HSTS, the part of HTTPS that the response's headers carry.
Our fetch verifies the certificate, the authority that signed it and the name it is for, so the connection fails. The result then says that the secure connection failed, instead of judging the page.
Let's Encrypt's certificates last 90 days, and it advises renewing them every 60, which automatic renewal tools do. The check fails when fewer than 14 days are left: by then, automatic renewal has stopped for over two weeks.
No. The check reads the address you give and the redirects it follows. Check your other pages too, and use the mixed content check for what a page loads over HTTP.
What this tool runs
- Page without HTTPScritical
https-missing - TLS certificate about to expireserious
tls-expiring - HTTPS without HSTSmoderate
hsts-missing
How we measure
We fetch the page as ArablyzerBot and follow its redirects. We read the final address, the dates of the certificate the server presented, and the Strict-Transport-Security header of its response. The address fails when it starts with http: on a public site. The certificate fails when it has expired, or has fewer than 14 days left, or less than a third of its lifetime when that is shorter. HSTS fails when an HTTPS page on a host name sends none, sends max-age=0, or writes it in a way RFC 6797 says browsers ignore; browsers read only the first such header, and so do we. The time left is counted from the moment of the check, which the report keeps.