Skip to content
MinniHost Guides

What Is an SSL Certificate? How HTTPS Works

By Review by MinniHost Guides Editorial Team Last checked Posted Topic: SSL & HTTPS

An SSL certificate is a digital file that binds a website's public key to its domain name, signed by a certificate authority that browsers trust. It lets a browser encrypt traffic and confirm it reached the right domain. The protocol in use today is TLS, so most people say SSL out of habit. Public certificates now last at most 200 days.

Brass padlock on a weathered wooden door

General information, not professional security or financial advice. Check your host’s and certificate authority’s current documentation; steps differ by provider.

An SSL certificate is the file that lets your browser trust that it has reached the right domain and that nobody can read the traffic in between. It carries a public key and a domain name, and a certificate authority signs the pair. This guide covers what is inside one, how HTTPS uses it, the main types, and the problems that cause most browser warnings. It is the hub for the rest of our SSL and TLS guides.

What is an SSL certificate in plain terms?

An SSL certificate is a digital file that binds a public key to one or more domain names, signed by a certificate authority (CA). The browser checks the signature, the names and the dates. If they all pass, it treats the server as the owner of that domain.

The name is a habit. “SSL” belongs to older protocol versions, and RFC 8446 says that the security of SSL 3.0 and SSL 2.0 is considered insufficient. What your browser runs today is Transport Layer Security (TLS), where MDN names TLS 1.3 as the current version and says TLS 1.0 and 1.1 should no longer be used. The certificate file format did not change, so people kept the old word. On this site “SSL certificate” and “TLS certificate” mean the same file.

MDN lists three protections that TLS gives you:

  • Encryption: data in transit cannot be read by an attacker on the network.
  • Integrity: data cannot be changed in transit without detection.
  • Authentication: the server can prove it is the entity it claims to be. On the web, usually only the server does this.

The certificate supplies the authentication part. Without it, the connection could be encrypted to the wrong party.

What is inside a certificate?

A certificate holds the subject, the names it covers, the issuer, the validity dates and the public key. These fields come from the X.509 format described in RFC 5280, and you can read them yourself with a certificate decoder.

Field What it says Why it matters
Subject alternative names (SAN) The domain names the certificate covers RFC 9525 says the Common Name must not be used to identify a service, so clients check this list
Issuer The CA that signed it Tells the browser which certificate to look for next in the certificate chain
Validity (notBefore, notAfter) The first and last moment the certificate is valid RFC 5280 treats the certificate as valid from notBefore through notAfter, inclusive
Public key The key that matches your server’s private key Used to set up the encrypted session
Signature The issuer’s digital signature over all of the above Proves the contents were not altered

A wildcard name such as *.example.com is allowed. RFC 9525 sets the matching rule: only one wildcard character, and only as the complete left-most label. So *.example.com can stand in for the first label of a name, as in www.example.com.

How does HTTPS use the certificate?

When you open an https address, your browser and the server run a short handshake before any page content moves. MDN lists four steps in the handshake:

  1. Version: both sides agree on a TLS version.
  2. Cipher suite: they agree on the algorithms for key agreement, authentication, encryption and message authentication.
  3. Authentication: MDN says the client and server optionally authenticate each other. On the web, the server presents its certificate and proves it holds the matching private key.
  4. Secret key: both sides agree on a secret key, then use it to encrypt everything that follows, including HTTP headers and bodies.

The browser then checks the certificate. It confirms that the signature chains up to a root it already trusts, that the name you typed appears in the SAN list, and that today’s date falls inside the validity period. If any check fails, you see a warning rather than the page.

The private key never leaves the server and is never part of the certificate. Only the public half is shared. That is why the file can be sent to every visitor safely, and why you must keep the private key secret.

Where do certificates come from?

Certificates come from certificate authorities that browsers and operating systems have agreed to trust. Each system ships a trust store, a list of root certificates. Your certificate is trusted because a chain of signatures leads back to one of those roots, as explained in our certificate chain guide.

To get one, you generate a key pair, send the public key in a certificate signing request, and prove to the CA that you control the domain. The CA then signs and returns the certificate. Automated CAs such as Let’s Encrypt run this through the ACME protocol, described in RFC 8555, with no manual steps. Our guide to the two routes to a certificate walks through both paths.

What types of certificates exist?

Certificates differ in how much the CA checks about you (domain, organization or extended validation) and in how many names they cover (single, wildcard or multi-domain). The CA/Browser Forum Baseline Requirements define a separate certificate profile for domain validated and organization validated certificates, and refer extended validation to its own guidelines.

Domain validation only proves control of a domain name. It is enough for encryption and is what most small sites use. SSL certificate types compares all of them in a table.

Are free certificates different from paid ones?

The encryption is the same; what differs is validation level, support and convenience. Let’s Encrypt states that it does not charge a fee for its certificates, and that it offers domain validation only, with no plans for OV or EV. A paid certificate can add organization details to the certificate and a vendor support channel. A hosting provider may charge a nominal fee for handling it, which the Let’s Encrypt FAQ notes. See Let’s Encrypt explained for how the free route works. We list no prices here because they change and need a dated vendor source.

How long do certificates last?

Public certificates have a legal maximum that is shrinking. The Baseline Requirements, version 2.3.1 dated 4 October 2026, set these maximums by issue date:

Issued Maximum validity
Before 15 March 2026 398 days
15 March 2026 to before 15 March 2027 200 days
15 March 2027 to before 15 March 2029 100 days
From 15 March 2029 47 days

Today, 17 November 2026, the 200-day limit applies to new certificates. The practical effect is that renewal by hand gets harder each time the limit drops, so automation matters more. Renewing an SSL certificate covers how.

What problems do people hit most often?

Three problems cause most warnings: an expired certificate, an incomplete chain, and a name that does not match the address.

  • Expired: the notAfter date has passed. Renew and install the new file.
  • Incomplete chain: the server did not send the intermediate certificate. Browsers sometimes cope; command-line tools often do not. See unable to get local issuer certificate.
  • Name mismatch: the address you typed is not in the SAN list, for example the certificate covers example.com but you opened shop.example.com.

What not to do

  • Do not disable certificate verification in a script or app to make an error go away. That removes the protection the certificate gives.
  • Do not paste a private key into a website, chat, ticket or tool, including ours. The checker needs only the public certificate.
  • Do not email a private key. Generate a new key pair if one has been exposed.

How do I check my own certificate?

Open the site in a browser and view the certificate details, or use the free certificate decoder, which runs in your browser and sends nothing to us. From a terminal, the OpenSSL s_client command with -connect host:443 -servername host connects and prints the certificate list the server sent, and openssl x509 -noout -dates prints the start and expiry dates of a certificate file.

Sources and review

Sources re-opened and compared with this text by the MinniHost Guides team on 2026-11-17. The team holds no security engineering licence or vendor certification. We do not describe browser icons or warnings in detail because browser interfaces change; check your browser’s own documentation.

All Ssl guides

Your questions answered

What is an SSL certificate?

An SSL certificate is a signed digital file that links a website's public key to its domain name. A certificate authority signs it after checking that the requester controls the domain. Browsers use it to set up an encrypted connection and to confirm they reached the domain they typed, which is what turns http into https.

Is SSL the same as TLS?

Not quite. SSL names the older protocol family, while TLS is the protocol browsers use today, with TLS 1.3 as the current version. People still say SSL certificate because the file format and the product names stayed the same. A certificate sold as SSL works with TLS, so you do not need a different file.

Do I need an SSL certificate for my website?

Yes, any public site should serve its pages over HTTPS, and that needs a certificate. MDN states that all websites should serve all their pages and subresources over HTTPS. Without one, browsers warn visitors, and many browser features that need a secure context stop working. Many hosts add a certificate automatically, so check yours first.

What does an SSL certificate not protect against?

It protects the connection, not the site behind it. A certificate does not stop malware on a server, weak passwords, outdated plugins, or a phishing site that also has a valid certificate. A domain-validated certificate proves control of a domain name, not that the owner is trustworthy. Keep the software updated and the accounts locked down as well.

How long does an SSL certificate last?

Under the CA/Browser Forum Baseline Requirements version 2.3.1, a public certificate issued from 15 March 2026 can be valid for at most 200 days. The limit becomes 100 days for certificates issued from 15 March 2027 and 47 days from 15 March 2029. Let's Encrypt certificates are issued for 90 days by default.

What is the padlock in the browser telling me?

The padlock means the connection to that domain is encrypted and the browser accepted the site's certificate. It does not say the site is safe, honest or free of malware. Browser designs change over time, so check your browser's own help pages for the exact meaning of the icon it shows today.

Where this comes from

  1. MDN: Transport Layer Security (TLS) (developer.mozilla.org)
  2. RFC 8446: The Transport Layer Security (TLS) Protocol Version 1.3 (rfc-editor.org)
  3. RFC 5280: Internet X.509 Public Key Infrastructure Certificate and CRL Profile (rfc-editor.org)
  4. RFC 9525: Service Identity in TLS (rfc-editor.org)
  5. CA/Browser Forum: Baseline Requirements for TLS Server Certificates, version 2.3.1 (4 October 2026) (cabforum.org)
  6. Let's Encrypt documentation: FAQ (letsencrypt.org)

More on this topic

Top of page