Book a call Free rebuild
Home/Glossary/Security/SSL Certificate

SSL Certificate

June 14, 2022 Updated November 16, 2026 3 min read

Security glossaryAn SSL certificate, strictly a TLS certificate, proves a website's identity and lets browsers connect to it over encrypted HTTPS.

An SSL certificate is a small data file, issued by a trusted certificate authority (CA), that ties a domain name to a cryptographic key. When a browser connects to a site over HTTPS, the site presents its certificate; the browser checks that it was issued by a CA it trusts, that it covers the domain being visited, and that it has not expired. If all is well, the browser and server set up an encrypted connection and the padlock appears. If not, visitors see a full-page security warning.

The name is a leftover. SSL, the original protocol, was replaced by TLS (Transport Layer Security) years ago, and every version of SSL is now deprecated. Today's certificates are TLS certificates, but "SSL certificate" is still what hosts, registrars, and most people call them.

What a certificate contains

  • The domain name or names it covers.
  • The site's public key.
  • The issuing certificate authority and its digital signature.
  • The dates it is valid from and until.

The certificate itself does not encrypt anything. It proves the server's identity: during the TLS handshake, the server uses the matching private key to prove it owns the certificate, and the session keys that do the encrypting are agreed separately.

Types of certificate

By validation level:

  • Domain Validated (DV): the CA checks only that the applicant controls the domain. Issued in minutes, often free.
  • Organization Validated (OV): the CA also verifies the organization behind the domain.
  • Extended Validation (EV): stricter checks of the organization. Major browsers no longer show EV certificates any differently in the address bar.

All three provide the same strength of encryption. By coverage, a certificate can protect a single name, every subdomain at one level (a wildcard, such as *.example.com, which does not cover example.com itself unless that name is added), or a list of different names (a multi-domain or SAN certificate).

Why every site needs one

  • Browsers label HTTP pages "Not secure", and many features, including HTTP/2, only work over HTTPS.
  • Logins, form entries, and payment details travel encrypted rather than in readable text.
  • Google has used HTTPS as a lightweight ranking signal since 2014.

Getting one for a WordPress site

Most hosts now issue free DV certificates from Let's Encrypt or a similar CA automatically, and renew them without anyone lifting a finger. Paid certificates are mainly worth it when an organization needs OV or EV validation, or a particular warranty or support arrangement.

After the certificate is active, switching WordPress to HTTPS takes a few steps:

  1. Set the WordPress Address and Site Address under Settings, then General, to https://.
  2. Add a site-wide 301 redirect from HTTP to HTTPS.
  3. Fix mixed content: replace hard-coded http:// links to images, scripts, and styles in the database and theme, for example with WP-CLI's search-replace.
  4. Once everything works over HTTPS, consider adding HSTS.

Common problems

Certificates are valid for a limited time, and maximum lifetimes keep getting shorter, so automatic renewal matters more each year. Renewals usually fail because the domain's DNS points somewhere other than the server requesting the certificate, often after a move to a new host or CDN. Other frequent causes of warnings are a certificate that does not cover the www or non-www version of the domain, and a missing intermediate certificate in the server's configuration. Our guide to installing a free SSL certificate in WordPress walks through setup.

WP Services

WordPress services at revolutionary pricing.

Productized WordPress services, from builds to care, delivered by Seahawk and tracked in one app. For the WordPress lovers.