What to Check When an SSL Certificate Looks Broken
HTTPS failures can come from expired certificates, missing intermediates, hostname mismatches, DNS changes, or a deployment that served the wrong certificate. A quick checklist makes the problem less mysterious.

Check the hostname first
Certificates are issued for specific names. If the certificate does not match the hostname users visit, browsers will warn even if the certificate is otherwise valid. Check both the root domain and the www or subdomain version.
Look at expiry before anything else
Expired certificates are common and easy to miss until users report errors. Track the expiration date and renew early enough that DNS, deployment, and CDN propagation do not create a last-minute incident.
Verify the certificate chain
A certificate can be valid but still fail if the intermediate chain is incomplete. Some clients are forgiving, while others are strict. Chain problems often appear after moving hosting providers or changing CDN settings.
Remember DNS and hosting layers
If a domain points to the wrong service, that service may present a certificate for a different project. After DNS changes, check the resolved target and confirm the host is attached to the right deployment.
Document the fix
Certificate issues are recurring operational tasks. After fixing one, document the renewal path, owner, provider, and expected alerting so the same issue is easier to solve next time.
A practical incident sequence
- Record the exact hostname, port, UTC time, client, and error message.
- Confirm DNS resolves to the expected service and that a proxy or CDN is not serving another certificate.
- Inspect the certificate presented for that hostname with SNI enabled.
- Check validity dates, subject alternative names, issuer, and chain completeness.
- Test from a second network or client to separate local cache and trust-store problems from server configuration.
- After a fix, verify the public endpoint again rather than relying only on a control panel status.
Hostname matching is more than the common name
Modern clients compare the requested hostname with the certificate's Subject Alternative Name entries. A certificate for example.com does not automatically cover api.example.com. A wildcard such as *.example.com normally covers one label, such as api.example.com, but not v2.api.example.com. Test the exact hostname users and automated clients request.
Why a valid leaf certificate can still fail
The server must usually provide the intermediate certificates needed to build a chain to a trusted root. Desktop browsers sometimes hide a missing intermediate because they cached it from another site, while a clean mobile device, API client, or server process fails. Compare results from a fresh client and inspect the chain delivered by the server, not only the leaf certificate file stored in the hosting dashboard.
Expiry checks need an operational margin
Do not wait for the final day. Renewal can succeed while deployment fails, a load balancer can retain an old certificate, or one region can lag behind another. Track the certificate currently served by every public hostname and alert with enough time to investigate. After renewal, compare serial number, validity window, issuer, and hostname coverage at the public edge.
What an online checker cannot prove
A remote check observes one public connection from one location. It cannot prove that every CDN region, private origin, IPv4 and IPv6 address, or authenticated service presents the same configuration. It also cannot assess application authorization or the security of content sent after TLS is established. Use it as a diagnostic observation, then confirm with your provider, monitoring, and representative clients.
Evidence to keep after a fix
- The affected hostname and user-visible error.
- The old and new certificate serial numbers or fingerprints.
- The chain served before and after deployment.
- DNS or proxy changes made during remediation.
- Verification from at least two independent clients.
- The next renewal owner, date, and alert path.
Sources and review notes
Terminology and hostname verification guidance are based on RFC 5280 and RFC 9525. Operational examples are synthetic and should be adapted to your TLS termination architecture. See the editorial policy for maintenance details.
Try the related tool
Open SSL Checker to inspect public certificate details for a hostname.