Get online today — Domain + Hosting at discounted prices View Combo Offers ›

SSL Certificate Checker

Check any site's certificate: expiry, issuer, hostname coverage and chain.

Add a port for non-standard services, e.g. mail.example.com:993.

Enter a domain to inspect the certificate it actually serves. You get the expiry date and days remaining, who issued it, every hostname it covers, whether the intermediate chain is complete, and which TLS version was negotiated.

An expired certificate shows every visitor a full-page browser warning, and an incomplete chain breaks quietly — often working in desktop browsers while failing on mobile devices, API clients and payment callbacks. This checks both.

How it works

The tool opens a genuine TLS connection to the host on port 443, exactly as a browser would, and reads the certificate the server presents. Nothing is taken from a cache or a third-party database, so what you see is what your visitors get right now.

Four things are worth understanding in the result:

  • Days remaining — most certificates last 90 days (Let's Encrypt) or a year. If automatic renewal is working you should never see this drop below about 30.
  • Covered hostnames — the Subject Alternative Name list. A certificate for example.com does not automatically cover www.example.com; both must be listed. A wildcard such as *.example.com covers one level of subdomain only, so it matches shop.example.com but not a.b.example.com.
  • Chain — servers must send the intermediate certificate(s) linking their certificate to a trusted root. Browsers often paper over a missing intermediate by fetching it themselves; many other clients do not, which is why "it works in Chrome but our app can't connect" is such a common report.
  • Self-signed — a certificate that vouches for itself. Fine for internal testing, but every public visitor sees a security warning.

Frequently asked questions

My certificate is valid but visitors still see a warning. Why?

The three usual causes are a missing intermediate certificate, a hostname that is not on the certificate (commonly the www version), or mixed content — the page loading images or scripts over plain HTTP. This tool checks the first two; the mixed content checker covers the third.

How many days before expiry should I renew?

Renew at 30 days remaining. If you use Let's Encrypt or another automated issuer, renewal normally happens at that point by itself — so seeing fewer than 30 days left usually means automation has broken rather than that you need to renew by hand.

What is the difference between the certificate and the chain?

Your certificate proves your identity but is signed by an intermediate authority, which is in turn signed by a root that browsers already trust. The server must present your certificate and the intermediates. The root is not sent — clients already have it.

Does a wildcard certificate cover every subdomain?

Only one level. A certificate for *.example.com covers shop.example.com but not checkout.shop.example.com, and it does not cover the bare example.com unless that is listed separately.

Can I check a certificate on a port other than 443?

Yes — enter the port alongside the hostname, for example mail.example.com:993. Only common service ports are permitted.

Why does the checker report a different certificate than I installed?

You are most likely behind a CDN or proxy such as Cloudflare, which terminates TLS at its edge and presents its own certificate. What you installed on the origin is then only seen by the CDN, not by visitors.

Related tools

Need hosting that just works?

Free SSL, daily backups and 24×7 support on every Loudhost plan.

View Hosting Plans