FAQ

Welcome to the FAQ

What is "FAQ"? It stands for Frequently Asked Questions. Here, you will find answers and definitions for various items and terms on our site. Feel free to drop us a line if there's anything that isn't clear enough, and we will do our best to not only explain it to you, but we'll update that content to better explain it for everyone else!

Some of the information here is pulled directly from other sites. we do our best to note the website it came from, but, if there's something we missed, just let us know.

What is a SSL Certificate?

SSL

SSL stands for Secure Socket Layer, and is a set of rules used for exchanging information between two computer devices using a public encryption system. SSL establishes secure communications between servers and clients. SSL provides a safe and authenticated method of handling e-commerce transactions. Only authorized users can access and read an SSL-encrypted data stream.

What is a single root certificate?

What is a Single Root SSL Certificate?
When connecting to a webserver over SSL, the visitor's browser decides whether or not to trust the website's SSL certificate based on which Certification Authority has issued the actual SSL certificate. To determine this, the browser looks at its list of trusted issuing authorities - represented by a collection of Trusted Root CA certificates added into the browser by the browser vendor (such as Microsoft and Netscape).

Most SSL certificates are issued by CAs who own and use their own Trusted Root CA certificates, such as those issued by GeoTrust and RapidSSL.com. As GeoTrust and RapidSSL.com is known to browser vendors as a trusted issuing authority, its Trusted Root CA certificate has already been added to all popular browsers, and hence is already trusted. These SSL certificates are known as "single root" SSL certificates. RapidSSL.com, a subsidiary of GeoTrust, owns the Equifax root used to issue its certificates.

Some Certification Authorities do not have a Trusted Root CA certificate present in browsers, or do not use the root they do own, and use a "chained root" in order for their SSL certificates to be trusted - essentially a CA with a Trusted Root CA certificate issues a "chained" certificate which "inherits" the browser recognition of the Trusted Root CA. These SSL certificates are known as "chained root" SSL certificates.

Installation of chained root certificates are more complex and some web servers and applications are not compatible with chained root certificates.

For a Certification Authority to have and use its own Trusted Root CA certificate already present in browsers is a clear sign that they are long-time, stable and credible organizations who have long term relationships with the browser vendors (such as Microsoft and Netscape) for the inclusion of their Trusted Root CA certificates. For this reason, such CAs are seen as being considerably more credible and stable than chained root certificate providers who do not have a direct relationship with the browser vendors, or do not use their own root certificates to issue SSL certificates.

You can view the Certification Authorities who have and use their own root certificates by viewing the list in your browser. Click here for instructions.

Chained root certificates require additional effort to install as the webserver must also have the chained root installed. This is not necessary for single root certificates.