SSL checker: are a site's HTTPS and certificate in order?
Enter a website address and we check whether it uses HTTPS, whether its SSL certificate is valid, when it expires, whether it covers the site's name and whether the HTTP address leads to HTTPS. It is an HTTPS check and a certificate check in one, run from the queue of our full audit.
What it checks
Whether HTTPS is enabled. If there is a certificate: whether it is valid (not expired, not yet valid, verifiable), its expiry date and the days left, whether it covers the site's name, who issued it and the HTTP version.
Then the HTTP address: whether it leads to HTTPS with a permanent or a temporary redirect, and whether the variants with and without www lead to the same address.
How to read the result
A valid certificate that covers the site's name, with a distant expiry and a permanent redirect from HTTP, is the healthy picture. An expired certificate, or one that does not cover the name, brings up the full page warning, "Your connection is not private". The "Not secure" label next to the address, by contrast, is what a page served without HTTPS gets.
Expiry close by? Renewing early is easy; afterwards visitors meet a warning and many leave. A temporary redirect tells search engines the move may not last: a permanent one is usually what is meant.
This check reads the certificate and the redirects, not every file the page loads. If the certificate is fine and the browser still warns, the cause may be a resource loaded over HTTP inside the page.
One check only? Here is the full picture.
This tool reads one part of the audit. The full SEO audit measures the homepage with Lighthouse, checks whether AI assistants can read it and, for the cities we have scanned, compares it with their sites.
The short answers.
The report says something's off.
We can fix it.
SEO errors, slow pages, sites invisible to AI: these are exactly the problems we solve for businesses and professionals every day.