Confirm that the certificate actually works
The browser's connection indicator matters more than proof of purchase. A good result means the site opens over HTTPS without a warning, the certificate is currently valid and it covers the hostname being opened.
- test the actual HTTPS address;
- open WWW separately when it is used;
- save a screenshot and an external test result.
What counts as a problem
| Result | Level | Action |
|---|---|---|
| HTTPS fails, the browser blocks the page, or the certificate is expired or issued for another hostname | Critical | The certificate is absent or unusable; issue or reinstall it. |
| The main hostname works, but a used WWW hostname or subdomain is uncovered; some clients receive an incomplete chain | Noncritical | Repair coverage or the chain before warnings become widespread. |
| Every used hostname opens without warnings, the certificate is current and the chain is trusted | No problem | Check automatic renewal and save evidence. |
Quick browser check
- Open
https://example.comin a private window. - Confirm that there is no full-page security warning.
- Open connection information and view the certificate.
- Check the hostname, issuer and validity dates.
- Repeat for
https://www.example.comif that address is used.
Independent Qualys check
- Open the Qualys SSL Server Test.
- Enter the hostname without
https://or a path. - If desired, select Do not show the results on the boards.
- Wait for the report and review Certificate, Common names, Alternative names, Chain issues and Not valid after.
- Save the result URL or a screenshot of the final page.
A grade below A does not always mean the certificate is missing; the test also considers protocols and ciphers. This check focuses on presence, trust, hostname coverage and current validity.
curl check
curl -Iv https://example.com/A successful TLS connection without certificate verify failed confirms that curl trusts the chain. The HTTP status may be 200, a 301 redirect or another valid response.
OpenSSL check
openssl s_client -connect example.com:443 \
-servername example.com </dev/null 2>/dev/null |
openssl x509 -noout -subject -issuer -dates \
-ext subjectAltNameThis displays the issuer, validity period and covered hostnames.
Why results may differ
A browser may cache an old certificate, a CDN may present another certificate, and IPv4 and IPv6 can lead to different servers. Repeat the test in a private window and from an outside network. An error limited to an old device may reflect its trust store rather than missing SSL on the server.
The automated wSEO check associated with this service tests for a working certificate on one entered hostname. It does not replace separate checks of redirects, mixed content, HSTS, ciphers or every subdomain. If the certificate is absent or issuance fails, follow the self-service guide or order assistance.
