TLS & certificates

Certificate chain trusted by browsers

Certificate validity and trust, key strength and protocol versions.

Why it matters

Browsers and apps refuse the connection or show a warning; some clients silently fail.

How to fix it

Quick fix · under 1 hour
  1. Use a certificate from a public CA (Let's Encrypt is free).
  2. Serve the full chain: configure the 'fullchain' file, not only the leaf certificate.
nginx
ssl_certificate     /etc/letsencrypt/live/example.com/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;
Test this now, free: SSL certificate checker - no sign-up.

How we test it

The check runs from the public internet as part of every scan, read-only and without touching your data. If it fails, your report shows the evidence that proves it - the record, header, file or banner we observed - together with the fix above, tailored to the issue we found.

Does your domain pass this check?

Run all 97 checks in about a minute. Your first scan is free, with the complete fix for your most urgent finding.

Scan your domain free