SSL and security check

Find out whether the connection to your site is encrypted and trusted, when the certificate runs out, and which server headers protect visitors. With ready settings to copy into nginx or Apache.

Free · no sign-up · up to 10 checks per hour

How the check works

Three steps, a few seconds.

  1. 01

    We read the certificate

    We connect to the site over https and look at who issued the certificate, for which domains and until when.

  2. 02

    We read the headers

    We open the page over https and over http and collect the server headers and cookies.

  3. 03

    You get a report

    A 0–100 score, 12 checks and a ready setting for every problem found.

What is checked

Three groups, 100 points in total.

01

Certificate and https

The certificate is trusted and issued for this domain, at least 30 days left, http leads to https, TLS 1.2 or 1.3. 40 points.

02

Security headers

Strict-Transport-Security, Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy. 45 points.

03

Leaks and cookies

The server and PHP versions are hidden, cookies have the Secure, HttpOnly and SameSite flags. 15 points.

FAQ

Didn’t find the answer?

Write to me — I will reply within one business day.

Is a low score a sign the site has been hacked?

No. The check looks only at the settings visible from outside: the certificate and the headers. A low score means the site is easier to attack, not that it has been attacked. Malware, passwords and the site code are not checked.

Where do I put the settings from the report?

On nginx — in the server block of the site, then run nginx -t and reload nginx. On Apache — in the site config or in .htaccess, the headers module must be on. On shared hosting, write to support or look for "Security headers" in the panel.

Will Content-Security-Policy break my site?

It can, if the policy forbids scripts the site uses: analytics, chats, payment widgets. So start with the Content-Security-Policy-Report-Only header: it only reports violations in the browser console. When the console is clean, switch to Content-Security-Policy.

Why is only TLS 1.2 or 1.3 checked and not the old versions?

The check sees the best version the site and our server agree on. Whether TLS 1.0 and 1.1 are off is shown by deep scanners like SSL Labs, which try every version one by one.

How many checks can I run?

Up to 10 checks per hour from one address. A repeated check of the same site within 2 minutes shows the ready report.

Want the server set up for you?

I will install a certificate with automatic renewal, set up the redirect to https and the security headers so that nothing on the site breaks, and keep an eye on it as part of support.

Assistant
Online now