Why does my browser say "not secure" or "your connection is not private"?

Almost always one of four things: the certificate has expired, it's for a different domain name, it isn't trusted (self-signed or a missing intermediate), or it isn't valid yet. Our check names the exact one.

How do I fix an SSL error on my site?

It depends on the cause: renew and reinstall an expired certificate, install one that matches your exact hostname, or reinstall the full chain (leaf + intermediates) if it's untrusted. The result tells you which applies.

Is the diagnosis free?

Yes, with no signup. To be warned before a certificate breaks next time, add your sites to a free SSLCanary account.

Why does my site say "not secure" after I installed a certificate?

Most often the certificate itself is fine but the chain is incomplete — the server is missing an intermediate certificate. Browsers can't build a path to a trusted root, so they warn. Reinstall the full chain your CA provides.

Why does my SSL work in one browser or device but not another?

Different browsers and devices carry different trust stores and cache intermediates differently, so a missing intermediate certificate can pass on one and fail on another. Installing the complete chain helps your certificate validate more consistently across browsers and devices.

Why is my SSL not working?

Enter your website and we'll tell you, in plain English, exactly what's wrong with its certificate and how to fix it.

Type a website above and press Check. You'll get the status and its exact expiry date, with the technical details a step away.

How it works

We test the common causes

We check expiry, hostname match, trust, chain, and start date — the common reasons a browser rejects a certificate — in one live probe.

We name the problem

No vague errors — we tell you the exact fault: expired, wrong hostname, untrusted, not yet valid, or a broken chain.

You get the fix

Each result names and explains that exact cause in plain English, so you know what to fix and can clear the warning.

Common questions

Why does my browser say "not secure" or "your connection is not private"?: Almost always one of four things: the certificate has expired, it's for a different domain name, it isn't trusted (self-signed or a missing intermediate), or it isn't valid yet. Our check names the exact one.
How do I fix an SSL error on my site?: It depends on the cause: renew and reinstall an expired certificate, install one that matches your exact hostname, or reinstall the full chain (leaf + intermediates) if it's untrusted. The result tells you which applies.
Is the diagnosis free?: Yes, with no signup. To be warned before a certificate breaks next time, add your sites to a free SSLCanary account.
Why does my site say "not secure" after I installed a certificate?: Most often the certificate itself is fine but the chain is incomplete — the server is missing an intermediate certificate. Browsers can't build a path to a trusted root, so they warn. Reinstall the full chain your CA provides.
Why does my SSL work in one browser or device but not another?: Different browsers and devices carry different trust stores and cache intermediates differently, so a missing intermediate certificate can pass on one and fail on another. Installing the complete chain helps your certificate validate more consistently across browsers and devices.

Want this watched automatically across all your domains? SSL certificate monitoring See plans & pricing