Docs Security

Served over HTTPS

Checks that your homepage ends up on an https:// address after redirects. Failing it caps the security score at 40 out of 100.

SecurityWeight 1In reports as https

What it checks

We load your homepage at https:// and follow every redirect. The check looks at the address the page finally lands on.

The weight is low because nearly every site passes. Failing it matters far more than the weight suggests: the whole security score is capped at 40 out of 100, however well the other security checks do.

Why it matters

Without HTTPS, everything a visitor sends or receives travels as plain text. Anyone on the same network, such as public wifi, can read logins and form entries or change the page on the way.

Browsers label HTTP pages as not secure, which puts visitors off before they read anything. Several other checks, such as HSTS and secure cookies, only make sense once the site is on HTTPS.

How to fix it

Get a TLS certificate for your domain. Most hosts and CDNs issue one for free, often through Let's Encrypt, and renew it for you.

Then make sure the site itself uses its https:// address everywhere: in its settings, in internal links and in redirects. A site that has a certificate but still redirects to http:// fails this check.

Platform notes

WordPress

Once your host has installed a certificate, set both WordPress Address and Site Address to https:// under Settings, General. Old http:// links inside posts can be updated with a search and replace tool.

Shopify, Wix, Squarespace and Webflow

Certificates are issued for connected domains. If the check fails, look in the domain or hosting settings for a certificate that is still pending or a domain that is not fully connected.

Cloudflare

If your origin server has its own certificate, use the SSL/TLS mode Full (strict). Flexible mode only encrypts the part between the visitor and Cloudflare.

Nginx and Apache

Certbot can request a free Let's Encrypt certificate and add it to your server config.

Next.js, Vercel and Netlify

Vercel and Netlify issue certificates automatically for domains you add to a project.

Your report shows what this check found on your site. Pro shows the exact fix for your site. See pricing.

Questions

Is a free certificate as secure as a paid one?

For encrypting the connection, yes. Free certificates such as Let's Encrypt use the same encryption. Paid certificates mainly add support, warranties or checks on the company behind the site.

Why does my security score stop at 40?

Because the homepage ends up on plain HTTP. Most other protections do not work without HTTPS, so the security score is capped until it is fixed.

See what this check finds on your site

Free, about 30 seconds, with every other check included.