A white paper and the webinar replay, for teams that want a second provider in place before they need one.
For security, infrastructure and IT leaders who keep a company's websites, applications and devices running on certificates.

A five-step guide for the person who runs certificates: take inventory, diversify CA relationships, write incident response procedures, test regularly, and activate the standby. It also covers what causes large certificate revocations.
Tim Reidel, our Director of Product Management, walks through what a second provider does for you and what it takes to run two behind one automation setup. Recorded October 7, 2026.
When a provider has an outage, or browsers stop trusting it, a company with one provider waits. A company with a second provider already set up asks that one instead, and the renewals keep running.
Adding a second provider doesn't mean replacing the first. The kit shows how teams set up a standby next to what they already use, so nothing about today's renewals changes.
Public certificates last 200 days at most today. Each renewal is a request to one provider. A company with 1,000 certificates makes this many requests a year.
Per 1,000 certificates, each replaced once at the end of its life. Schedule: CA/Browser Forum ballot SC081v3.
SSL was founded in 2002, maintains WebTrust audit compliance, and has been a full voting member of the CA/Browser Forum, the group that sets the rules public certificates follow, since August 3, 2017.
Free with your work email. The downloads open on the next page.
Take our survey and let us know your thoughts on your recent purchase.