A certificate warning deserves a specific diagnosis. Common causes include an expired certificate, a hostname mismatch, an incomplete certificate chain or a DNS record sending some visitors to a different server. A warning seen on one device can also involve its clock, cached DNS or a network interception page.
Recommended workflow
- Verify the device date and time, then inspect the certificate subject names, issuer chain and expiry shown for the failing connection.
- Compare the public DNS destinations with the server or proxy expected to host the site.
- Correct the identified certificate or routing problem, then test externally before restoring redirects or announcing resolution.
Capture the exact hostname and warning text, then compare results from another network or a clean browser session. Check both the main domain and www address if visitors use both. When a domain has A and AAAA records, ensure that the IPv4 and IPv6 destinations each present the correct HTTPS configuration.
If a proxy or CDN is involved, distinguish the public-facing certificate from the connection to the origin server. Replacing the origin certificate alone may not change what visitors receive. Keep screenshots of the error free of account information and do not distribute private key files.
