Fail

Your certificate is self-signed

The short version

Replace it with a certificate from a trusted authority; Let's Encrypt is free.

What it means

A normal certificate is signed by a certificate authority that browsers trust. A self-signed certificate is signed by its own key, so it vouches only for itself. The SSL check found a self-signed certificate on this host name. Servers often start with one: control panels, appliances and fresh installs create a placeholder until a real certificate is added.

Why it matters

Every browser shows a security warning for a self-signed certificate, and apps and API clients refuse to connect. Visitors can't tell your placeholder apart from an attacker in the middle, which is exactly why browsers block it.

How to fix it

  1. Get a certificate from a trusted authority. Let's Encrypt and ZeroSSL issue them for free, and most hosting providers can do it with one click.
  2. Prove that you control the domain, usually through an HTTP file or a DNS record the issuer checks.
  3. Install the new certificate with its full chain in place of the self-signed one, then reload the web server.
  4. If the server is a device or panel that keeps regenerating its own certificate, look for its setting to upload or request a proper certificate.

Let's Encrypt with certbot

On a server running nginx or Apache, sudo certbot --nginx -d example.com -d www.example.com requests and installs a certificate in one step.

Cloudflare

If Cloudflare proxies your site, visitors see Cloudflare's certificate, but the connection to your server needs a valid one in Full (strict) mode. Install a free Cloudflare origin certificate on the server.

Check it worked

Run the SSL check again. The card should say "Trusted", and the chain should end at a root from a known certificate authority.