What does an SSL checker do?
An SSL checker inspects the SSL/TLS certificate presented by a website during an HTTPS connection, verifying expiry dates, issuer details, trust chains, supported TLS versions, and domain coverage.
SSL & HTTPS support
In-depth explanations of how SSL/TLS certificates work, why browsers show warnings, how trust chains are validated, and what secure HTTPS configuration looks like.
An SSL checker inspects the SSL/TLS certificate presented by a website during an HTTPS connection, verifying expiry dates, issuer details, trust chains, supported TLS versions, and domain coverage.
No. SSL checks are completely read-only. They do not modify certificates, server configuration, encryption settings, or traffic in any way.
TLS (Transport Layer Security) is the modern replacement for SSL. Although the term SSL is still widely used, all modern HTTPS connections use TLS.
Best practice is to support TLS 1.2 and TLS 1.3 only. Older protocols such as SSLv3, TLS 1.0, and TLS 1.1 are insecure and should be disabled.
Browser warnings appear when a certificate is expired, untrusted, self-signed, revoked, missing intermediate certificates, or does not match the domain name.
Certificates expire to reduce the impact of compromised keys and outdated cryptographic standards. Short lifetimes improve overall internet security.
Browsers will display security warnings or block access entirely. APIs and mobile apps may refuse to connect until a valid certificate is installed.
A trust chain links a website certificate to a trusted root certificate authority through one or more intermediate certificates.
Some browsers and devices may fail to establish trust, causing SSL warnings even if the main certificate appears valid.
A domain mismatch occurs when a certificate does not include the requested domain name in its Common Name or Subject Alternative Names.
A wildcard certificate secures a domain and all its first-level subdomains, such as *.example.com.
A multi-domain certificate secures multiple, unrelated domain names using a single certificate.
Yes. HTTPS is required for modern APIs. Many platforms and clients refuse to connect to APIs over unencrypted HTTP.
Yes. iOS and Android enforce HTTPS by default. Invalid or insecure certificates can cause app network requests to fail.
ATS is an iOS security feature that enforces HTTPS connections using strong TLS configurations and valid certificates.
Revocation invalidates a certificate before its expiry date, typically due to key compromise or mis-issuance.
OCSP (Online Certificate Status Protocol) allows browsers to check whether a certificate has been revoked in real time.
HSTS forces browsers to use HTTPS only. If SSL fails while HSTS is active, users may be completely locked out of the site.
Modern HTTPS has minimal overhead and often improves performance due to HTTP/2 and TLS optimisations.
Let’s Encrypt is a free certificate authority that provides automated, trusted SSL certificates for websites.
Best practices include automated renewal, TLS 1.2+ only, complete certificate chains, strong ciphers, monitoring expiry, and avoiding deprecated protocols.
No. SSL inspections are performed live and no certificates, domains, IP addresses, or results are stored or logged.
Want to try it yourself? Run SSL checker or Check HSTS configuration or Test IPv6 HTTPS support
Ready to inspect a certificate?