SSL certificate checker

Catch expiring or mismatched certificates before the browser warning becomes your launch announcement.

https://

Why SSL still matters

Encryption

HTTPS encrypts traffic between the browser and the site so credentials, sessions, forms, and page content are harder to intercept or alter in transit.

Trust

A valid certificate keeps browsers from showing the warning screen that turns a launch, sales page, or dashboard into an immediate trust problem.

Platform readiness

Modern browsers, APIs, payment flows, analytics scripts, and search engines all expect secure delivery as the default state for production websites.

Common certificate failures

Certificate expired

NET::ERR_CERT_DATE_INVALID

The certificate validity window has ended and the site needs renewal before browsers trust it again.

Hostname mismatch

NET::ERR_CERT_COMMON_NAME_INVALID

The requested hostname is not covered by the certificate's Common Name or Subject Alternative Names. This often happens when www and apex domains are handled separately.

Untrusted issuer

NET::ERR_CERT_AUTHORITY_INVALID

The browser does not trust the issuing CA, or the certificate is self-signed in a context that expects a public CA.

Frequently asked questions

What is the difference between free and paid SSL certificates?

For most websites, the core encryption strength is similar. Paid certificates typically differ in validation depth, support, or business assurances rather than raw HTTPS capability.

Why are some certificates only valid for 90 days?

Shorter lifetimes reduce exposure when keys are compromised and encourage automation. That is why modern certificate workflows rely on automatic renewal.

What is a Subject Alternative Name?

A SAN lists the hostnames covered by the certificate. If example.com is covered but www.example.com is not, browsers can still show a hostname mismatch.

Why does SSL fail right after I point DNS to a new host?

The platform may need time to verify the domain and issue a certificate. During that window, DNS can resolve correctly while HTTPS still returns a certificate error.

Want certificates handled with the deployment?

DeployPages provisions and renews certificates for supported custom domains, so the domain, HTTPS, and published site move together instead of becoming separate launch chores.

See managed SSL