HomeSSL and Certificates – Part 3 of 3: How Certificates Earn Your Browser’s TrustCybersecuritySSL and Certificates – Part 3 of 3: How Certificates Earn Your Browser’s Trust

SSL and Certificates – Part 3 of 3: How Certificates Earn Your Browser’s Trust

This is the final post in our series on SSL and certificates. Part 1 covered the basics of encryption, and Part 2 explained public and private keys, digital signatures and the man-in-the-middle problem.

We ended Part 2 with a question: when a server hands your browser a public key and claims to be your bank, how do you know it’s telling the truth? The answer is the SSL certificate, and it works a lot like a passport.

A Certificate Is a Signed ID Card

A passport is useful because a government you trust has vouched for the photo and the name in it, and it’s very hard to forge. An SSL certificate is the same idea for a server. It is a small file that contains:

  • The names it is valid for, such as mooselogic.com and www.mooselogic.com. These are listed in a field called the Subject Alternative Name, or SAN.
  • The server’s public key, the padlock from Part 2.
  • Who issued it, and the dates it is valid between.
  • A digital signature from the issuer, covering all of the above.

That signature is what ties everything together. The issuer, called a Certificate Authority or CA, checks that whoever requested the certificate really controls the domain, then signs the bundle with its own private key. Change anything in the certificate, even one letter of the name, and the signature no longer matches.

The Chain of Trust

So who vouches for the Certificate Authority? Your computer does, sort of. Windows, macOS, iOS, Android and the major browsers ship with a built-in list of a few dozen trusted root certificates belonging to CAs that have passed strict audits. Those root keys are so valuable that CAs keep them offline, locked away, and almost never use them directly.

Instead, a root signs one or more intermediate certificates, and the intermediates sign the certificates issued to websites. When you visit a secure site, your browser follows the chain: the site’s certificate was signed by this intermediate, which was signed by that root, which is on my trusted list. If every signature checks out, every name matches and nothing has expired, you get the padlock. If any link is broken, you get a full-page warning.

What Actually Happens When You Connect

The protocol we still call SSL has actually been named TLS (Transport Layer Security) for more than twenty years. The original SSL versions and the early TLS 1.0 and 1.1 are retired as insecure. Today’s connections use TLS 1.2 or, increasingly, TLS 1.3. Stripped to the essentials, a TLS 1.3 connection goes like this:

  1. Your browser says hello, lists the encryption methods it supports and sends its half of a key exchange.
  2. The server replies with its half of the key exchange, its certificate and the intermediate certificates, plus proof that it holds the matching private key.
  3. Your browser checks the chain, the name and the dates.
  4. Both sides derive the same fresh symmetric key, and everything after that is protected with fast encryption such as AES.

All three parts of this series show up in those few milliseconds: the public-key math from Part 2 agrees on a key, the certificate proves who you’re talking to, and the symmetric encryption from Part 1 does the heavy lifting.

Types of Certificates

  • Domain Validated (DV): the CA confirms you control the domain, usually automatically. This is what most websites use, including the free certificates from Let’s Encrypt.
  • Organization Validated (OV) and Extended Validation (EV): the CA also checks that your business legally exists. Browsers no longer display EV differently, so for most small businesses the extra paperwork buys little.
  • Multi-domain (SAN) certificates cover a specific list of names, such as mail.example.com and autodiscover.example.com for an on-premises Exchange server.
  • Wildcard certificates cover every name at one level, such as *.example.com. They are convenient, but the same private key ends up on many servers, so one compromised server exposes them all.

The Gotchas We Still See

Back in Part 1 we promised to cover the “gotchas.” Mobile devices syncing with Exchange were the classic headache in 2009, and the underlying mistakes haven’t changed much. In fact, we tripped over two of them ourselves this very week while setting up a new server.

  • The missing intermediate. The server sends its own certificate but not the intermediate that signed it. Some browsers quietly fetch the missing piece and work fine, while phones, apps and other servers throw errors. Always install the full chain the CA provides.
  • The name mismatch. A certificate for example.com and www.example.com does not cover portal.example.com. Check the SAN list, not just the main name, before you install it somewhere new.
  • The surprise expiration. Certificates expire on schedule, and when one does, the site, mail flow or VPN behind it stops working with little warning.
  • Internal names. Public CAs stopped issuing certificates for internal-only names such as server01.local years ago. Internal systems need a real domain name or a private, company-run CA.
  • The re-key that breaks something else. Re-keying a certificate creates a new key pair, and the old copy may be revoked. Anywhere else that certificate was installed needs the new version too.
  • Careless handling of the private key. Private keys get emailed, left in download folders and copied to every server that needs a certificate. Whoever has the key can impersonate your site.

Certificates Are Getting Much Shorter Lives

That expiration gotcha is about to get a lot more common. In April 2025 the CA/Browser Forum, the group of browser makers and Certificate Authorities that sets the rules, approved a schedule that steadily shortens how long public certificates can last. Certificates issued from March 15, 2026 are limited to 200 days. From March 15, 2027 the limit drops to 100 days, and from March 15, 2029 it drops to just 47 days.

Shorter lifetimes are good for security: a stolen key or a mistaken certificate stops being useful much sooner. But they make manual renewal impractical. A business with a dozen certificates on a 47-day cycle would be renewing something nearly every week. The answer is automation, typically the ACME protocol that Let’s Encrypt popularized, which requests, installs and renews certificates without anyone touching them, backed by monitoring that warns you before anything lapses.

What to Do Now

  1. Take inventory. List every certificate you depend on: websites, mail, VPNs, firewalls, remote access gateways, printers and line-of-business apps.
  2. Automate renewals wherever the system supports it, and plan replacements for systems that don’t.
  3. Monitor expiration dates independently, so you hear about a problem days before your customers do.
  4. Retire old protocols such as TLS 1.0 and 1.1, and keep private keys off email and shared drives.

Encryption has come a long way from decoder rings and bingo hoppers, but the principle hasn’t changed since Bletchley Park: the math is public, and the security lives in the keys and in how carefully people handle them.

Moose Logic manages certificates as part of managed IT and cybersecurity engagements, and websites hosted on The Grove can use free, automatically renewing certificates from Let’s Encrypt or a commercial certificate from the CA of your choice, with expiration monitoring either way. Want a certificate inventory before the 100-day limit arrives? Talk to our team.

Moose Logic

Technology Built for the Long Haul. Since 1994, Moose Logic has been the outsourced IT department and trusted technology partner for businesses across the Greater Seattle Area and beyond: managed IT, cybersecurity, The Lodge private cloud and The Grove website hosting.

Contact

Concierge, John Regis
(425) 616-1540
johnregis@mooselogic.com

Support
(425) 616-1541

Amanda Perez
(425) 616-1542
amanda@mooselogic.com

Scott Gorcester
scott@mooselogic.com

sales@mooselogic.com
Greater Seattle Area, Washington

© 2026 Moose Logic. All rights reserved.  |  Privacy Policy  |  Cookie Policy