Short answer: “The website does not work over HTTPS” is a critical finding in the Security area of a Site AI Audit report. It appears when the audit cannot open a secure connection to your domain on the standard HTTPS port within ten seconds, or cannot read a certificate from it. Browsers mark such sites as not secure, visitors leave and search engines rank them lower. The fix is to install a valid SSL certificate, open port 443 and redirect every http address to https.
What triggers the finding
At the start of every audit, the crawler tries to open an HTTPS connection to your domain on port 443, the standard port for secure web traffic. It gives the server ten seconds to answer and then tries to read the certificate. If the connection fails, or there is no certificate to read, the audit records that the site does not work over HTTPS and raises this finding.
The report explains the consequences in plain words: browsers mark sites without HTTPS as “Not secure”, visitors leave, and Google ranks them lower. The advice is to install an SSL certificate, mentioning that a free one is available from Let’s Encrypt, and to redirect all http traffic to https.
Why it is critical
Three things go wrong at once. First, visitors see a warning next to your address in their browser, or a full-page warning when a form is involved. Many people stop right there, especially when they are asked for an e-mail address, a phone number or a payment. Second, anything sent between the visitor and your site, including form content and login details, can be read or changed on the way. Third, search engines have used HTTPS as a ranking signal for years, and they prefer to send people to secure pages.
The finding also hides other issues. When there is no HTTPS connection, the audit has no certificate to check, so findings about expiry, trust and name match are not produced. The redirect finding is skipped for the same reason. Once you fix this problem, those checks run, and new findings may show up in the next report. That is normal: they were always there, only not visible, and it is better to learn about them from a report than from an unhappy visitor.
The usual causes
- No certificate has been installed. The site was set up with http only and nobody added a certificate.
- The certificate exists but is not attached to this domain. It was issued for another name, or the domain was added to the server without the certificate.
- Port 443 is closed. A firewall or a hosting rule only allows port 80, or the web server does not listen on 443.
- A CDN or proxy is set to a mode that does not use HTTPS to your server. The article on CDN SSL modes explains the options.
- The handshake fails. The server only supports very old protocol versions or broken settings, so modern clients cannot connect.
- A very slow server. The connection needs more than ten seconds to start, which counts as a failure.
- A new domain or a DNS change. The name has not yet reached the new server, so the connection goes to a place that has no certificate for it.
How to check it yourself
- Type the address with https:// in a browser. If you see a warning page or a connection error, the cause is on the server side.
- Read the error. “Connection refused” or “timed out” suggests a closed port. A name mismatch or untrusted warning suggests a wrong certificate. The article on ERR_SSL_PROTOCOL_ERROR covers one frequent case.
- Look at your hosting panel. Most panels have an SSL or security section that shows whether a certificate is installed for each domain.
- Test from outside your own network. Your own computer may have cached results or be on a network that behaves differently.
How to get a certificate
A certificate proves that the server belongs to the domain and encrypts the connection. For most sites, a free certificate from a trusted authority is enough, and the article on free and paid certificates explains when a paid one makes sense. The way to install it depends on where you host:
- Shared hosting. Open the control panel, find the SSL or “Let’s Encrypt” option and enable it for the domain. This is usually a few clicks.
- A managed platform or website builder. Turn on HTTPS in the domain settings.
- Your own server or VPS. Use a tool such as Certbot, which gets the certificate and renews it automatically. The guide to automating renewal with Certbot shows the steps.
- Behind a CDN. Enable HTTPS in the CDN and also install a valid certificate on your server, so that the whole path is encrypted.
Whichever route you take, the certificate must cover the exact names visitors type, with and without www, and it must be renewed before it expires. If you are not sure what a certificate is, start with the article what is an SSL certificate.
After the certificate: redirect and tidy up
- Redirect http to https with a permanent 301 redirect, so that every old link and bookmark ends on the secure version. The article on redirecting HTTP to HTTPS shows how to do it without loops.
- Update internal links, the sitemap and the canonical tags to use https.
- Fix mixed content. Images or scripts that still load over http make browsers warn on a secure page. The audit reports this as a separate finding, covered in mixed content and redirect findings.
- Turn on automatic renewal and make sure someone is notified if it fails.
- Re-check. The critical finding should disappear, and the certificate checks will run for the first time.
What you may see after the fix
When the certificate is in place, the report may show new findings that were hidden before. A certificate that is close to expiry, a certificate that does not cover the www version of your name, or a missing redirect from http to https are typical examples. The article on SSL certificate findings explains each one. These are easy to fix, and fixing them now means you will not meet them later as an outage.
Special cases to check
- The www version only. The certificate may cover your bare domain but not the www name, or the other way round. A certificate should list both names. The finding about the name on the certificate is explained in the SSL article linked below.
- Subdomains. A certificate for the main domain does not automatically cover a subdomain such as shop.example.com, unless it is a wildcard certificate or lists that name.
- Staging copies and new domains. A site that is still being built often runs on http only. Install the certificate before you announce the address, so the first audit and the first visitors see a secure site.
- Several sites on one server. Each domain needs its own certificate entry. If one domain has none, the server may answer with the certificate of a different site, which leads to a name mismatch instead.
- E-mail and other services on the domain. The certificate for the website does not secure your mail server. They are separate things.
If the connection works but the browser still complains, the cause is usually a certificate that is untrusted, expired or issued for another name. Those cases are reported as their own findings rather than as “does not work over HTTPS”.
A worked example
A small photographer launches a new portfolio site on a cheap hosting plan. The first audit shows a critical finding: the website does not work over HTTPS, and the security score is low. The photographer opens the hosting panel and finds that an SSL option exists but has not been switched on for the new domain. After enabling it, the certificate is issued within minutes. A redirect from http to https is added, and two images that were linked with http addresses are corrected. A new check shows the critical finding gone. It also shows a notice about missing HSTS, which the photographer adds later with the help of the article on security header findings.
To see how your own site responds, run a Site AI Audit. The check needs a free account; the plans unlock the full report with the details.
Related reading
- SSL Certificate Expired: What Happens and How to Fix It Fast
- SSL vs TLS: What Is the Difference and Why It Still Matters
- Website Security for Small Businesses: Where to Start
- Is Your Website Protected From Hacking? What the Audit Checks
The bottom line
A site that does not work over HTTPS shows warnings, loses visitors and ranks lower. Install a valid certificate, make sure port 443 is open, redirect http to https and run the audit again to unlock the other certificate checks.
KKK
Do I have to pay for a certificate?
No. Free certificates from trusted authorities such as Let’s Encrypt work for most websites, and many hosts install them with one click.
Why does the audit say there is no HTTPS when my site opens in my browser?
Your browser may show a cached result, or the site may open over http only. Type https:// explicitly and test from another network.
Will the certificate findings appear right away?
Yes. After the connection works, the next check also looks at expiry, trust and the name on the certificate.
Is a closed port 443 enough to cause the finding?
Yes. If the audit cannot open the connection in ten seconds, it records that HTTPS does not work.
Does moving to HTTPS affect my rankings?
Done properly, with permanent redirects and updated links, it supports your rankings. The risk comes from leaving both versions live or from broken redirects.



