The certificate is valid for another six months, but the browser warns that the connection is not secure. Check the error message: if the site name doesn’t match the certificate, renewing it won’t help. The server has presented a certificate for a different address, or the required name was never added when the certificate was issued.
Start with the address in the browser bar. example.com, www.example.com, and shop.example.com are different names. Note the version that triggered the error and send it to the administrator along with a screenshot of the warning. Checking only the homepage without www isn’t enough if visitors use the version with www.
Compare the address with the names in the certificate
In the certificate viewer, find the Subject Alternative Name field, usually abbreviated to SAN. It lists the names the certificate was issued for. If the browser opens www.example.com but the list includes only example.com, you’ve found the cause.
A wildcard also has limits. The certificate *.example.com is valid for shop.example.com, but it doesn’t cover example.com or a.shop.example.com by itself. Those names need to be included or covered by separate certificates.
A redirect from www to the main domain doesn’t fix this error. When a browser connects over HTTPS, it first checks the secure connection and only then receives the HTTP response with the redirect. So the original HTTPS address also needs a certificate.
Find out why the wrong certificate was presented
Ask the administrator to check two things: whether the required name is included in the installed certificate, and whether the server is presenting that certificate. These are separate issues. The correct file may be on the server, but the site could still be using an old configuration.
Several sites often share one IP address. When connecting, the client sends the required name via SNI so the server can select a certificate. A site configuration error can cause the server to present a certificate for a neighboring domain. Don’t replace this diagnostic with a request to the bare IP: that request checks different conditions.
If a CDN sits in front of the site, visitors usually see the CDN’s certificate. The origin server’s certificate is checked separately. Clarify which part was changed; otherwise, you might update the server-side file successfully while leaving the error visible to visitors.
What to check with OpenSSL
The command below may be useful for the administrator. Replace the name in all three places with the address showing the error:
openssl s_client -connect www.example.com:443 \
-servername www.example.com \
-verify_hostname www.example.com -verify_return_error </dev/null-servername passes the name used to select the certificate, while -verify_hostname checks whether it matches that name. -verify_return_error stops the check on an error instead of continuing with a warning.
Save the error message. The successful verification result is Verify return code: 0 (ok); trust verification also depends on the trusted certificate store on the computer. If the command doesn’t support the option, check your OpenSSL version and its help. The options are described in the OpenSSL documentation.
Give the administrator a precise task
Suppose the main domain works, but the version with www presents a certificate for a neighboring site. The message could be:
On https://www.example.com, the browser reports a name mismatch. The certificate was issued for other.example.net; https://example.com opens normally. Check certificate selection for www.example.com and add this name to the certificate if it isn’t already included.
Don’t simply ask them to “renew SSL”: that request can easily be completed without fixing the cause. A list of other errors is available in the SSL troubleshooting guide, and the certificate workflow is covered in the HTTPS guide.
Check all versions in use after the fix
Open the main domain, the version with www, and any required subdomains without bypassing browser warnings. Then follow an actual old link: the original address should establish a secure connection and perform the expected redirect.
If the error appears intermittently, the administrator should check all the servers receiving distributed requests. One of them may still have an old certificate. A repeat technical audit can help verify that the page is accessible after the change; also save the result of checking the specific name in a browser.