Match the hostname, review the certificate dates and understand the trust result. A valid certificate is one part of a secure website.
- Hostname match
- Certificate dates
- Trust chain
How to use this tool
- Enter the exact public hostname visitors use.
- Run the certificate check over HTTPS.
- Review the expiry, issuer and covered names, or read the specific verification failure.
Understanding the results
- Covered names
- The certificate must cover the hostname you entered. Checking example.com does not automatically check every subdomain.
- Expiry and issuer
- Use the validity dates and issuer to investigate renewal and certificate deployment.
- Verification failure
- An expired certificate, missing intermediate certificate or hostname mismatch can stop verification. Resolve the reported issue before retesting.
What this check covers
The result describes the public TLS endpoint reached by Zevonix’s server at that moment. A CDN or reverse proxy can present a different certificate from the origin. This is not a full TLS configuration audit.
Common questions
Does a valid certificate mean a website is secure?
It confirms this check could validate the certificate for the hostname. It does not assess application vulnerabilities, account security or the trustworthiness of the business.
Why can the browser and this tool disagree?
They can reach different endpoints or use different cached DNS answers and certificate stores. Compare the exact hostname, certificate and time of each check.