Skip to content

Basics

My site is not served over HTTPS

Every visitor gets a full-page browser warning before they see anything. Conversion through that screen is effectively zero, and search engines drop the site rather than index it over a broken connection.

What 13x checks

This is rule basics.https in the public registry: Served over HTTPS with a valid certificate. It runs on every audit, against the pages we actually fetched, and its result is derived from the response rather than estimated.

Surface
Basics
Score weight
16 of the readiness score
Scope
Runs on every audited page
Applies
To every site

Registry version 2026-07-30. Every rule is published, and the audit is deterministic — the same page produces the same finding every time.

The fix

The same text the audit hands you when this check fails on your own site.

Serve the site over HTTPS with a valid certificate.

Every managed host issues and renews one free: Vercel, Netlify, Cloudflare Pages and Railway do it automatically once DNS points at them. On your own server, use Certbot with Let's Encrypt and confirm the renewal timer is active — an expired certificate is the same outage as no certificate.

If the certificate exists but is reported invalid, the usual causes are a hostname mismatch (issued for www.example.com but served on example.com) or an incomplete chain. Check both at ssllabs.com/ssltest.

Does your site have this problem?

13x checks this and 112 others against your live URL in about 30 seconds. No account, and every finding comes with the fix for your framework.

No signup. Results in 30 seconds.

More basics checks