Independent DNS tools & practical learning resources No account required · Made for webmasters
Illustration for SSL Certificates and HTTPS Basics

What a TLS certificate tells a visitor

When a browser connects to a site over HTTPS, the server presents a TLS certificate containing information about the name it covers, the issuing certificate authority and a validity period. Browsers also evaluate trust chains and other security properties before considering a connection secure.

Expiry dates matter, but they are not the whole story

Certificates have a beginning and end to their validity period. An expired certificate commonly triggers a browser warning. However, a certificate that is not yet expired can still be untrusted if it belongs to the wrong hostname, has an invalid chain, or is subject to other security failures.

What the SSL tool checks

Our SSL Certificate Checker connects to the requested public IP on port 443 and inspects the presented certificate's subject, issuer and validity dates. It does not provide a complete certificate chain, revocation, cipher configuration or hostname trust audit, so interpret it as a certificate metadata inspection.

Common causes of warnings

  1. The certificate expired or renewal failed.
  2. The certificate covers a different name.
  3. The server presents an incomplete or unsuitable certificate chain.
  4. Different server nodes expose different certificates.
  5. The site is reachable via HTTPS but contains mixed-content resources.

Before changing certificates

Check which hosting provider or reverse proxy terminates TLS. A CDN may present a different certificate from the origin server. Confirm the DNS destination, preferred www/non-www hostname and automated renewal method before changing settings.

Further reading: MDN introduction to TLS.


Editorial note: This is general educational information, not a live audit. DNS behavior and provider policies can change, and results should be verified against authoritative sources.

← Back to all DNS guides