Expiry
Track the exact validity window.
Check certificate expiry, hostname coverage, trust chain and live TLS security settings.
Enter a domain or HTTPS website address, then click Check certificate.
SSL / TLS SECURITY
An SSL/TLS certificate authenticates a website and encrypts data between browsers and servers. A complete check goes beyond the padlock: it reviews hostname coverage, validity dates, certificate chain, public trust and the TLS parameters negotiated by the server.
This tool connects directly to the target server and reads its public certificate and handshake data, helping site owners catch configuration failures before visitors see browser warnings.
Track the exact validity window.
Review server and intermediate certificates.
Inspect the live protocol and cipher.
Certificate renewal, CDN migrations, load balancers and intermediate-CA updates can break a previously healthy HTTPS setup. Regular checks reduce the risk of outages, trust warnings and failed search-engine crawling.
See the exact expiry date and days remaining, and catch renewal or deployment failures early.
Confirm that the SAN covers the host and that the intermediate chain validates publicly.
Review the negotiated protocol, cipher suite and public key strength against modern baselines.
The server resolves the public address, sends the original hostname as SNI during a real TLS handshake, then analyzes the certificate and connection independently.
Normalize the host and port while blocking local, private and reserved network addresses.
Connect to the public IP and retain the hostname as SNI to obtain the intended certificate.
Read CN, SANs, issuer, validity, key, fingerprint and the available certificate chain.
Flag expiry, hostname mismatch, trust, weak-key and obsolete-protocol problems.
Fix expiry, hostname mismatch and trust failures first because they directly trigger browser warnings. Schedule soon-to-expire certificates, weak keys and old protocols for prompt maintenance.
The current time must fall within the certificate dates and the requested host must appear in its SAN list.
The server, intermediate and trusted root certificates must form a path browsers can validate.
Modern sites should prefer TLS 1.3 with a securely configured TLS 1.2 fallback for older clients.
Confirm successful renewal at least 30 days before expiry. Monitor automated renewal too: successful issuance does not guarantee deployment to every CDN, proxy or origin.
Common causes include hostname mismatch, a missing intermediate, mixed page content, a different port, or different certificates on the CDN and origin.
The chain links the server certificate through one or more intermediate CAs to a trusted root. A server normally sends its certificate and the required intermediates.
Properly configured TLS 1.2 remains a useful fallback, but enable TLS 1.3 first and disable TLS 1.0, TLS 1.1 and weak cipher suites.
No. Results remain on the current page. The server uses only a short cache to reduce duplicate connections and creates no indexable history.
Continue with website response, email DNS, page metadata and domain-resolution checks.
Check HTTPS status, redirect chains and response headers.
Review email DNS and delivery-security records.
Check search snippets, Open Graph and Twitter Cards.
View domain records and response data from multiple probes.