Chained Root SSL Certificates

When connecting to a web site over SSL, the visitor's web browser decides whether or not to trust the SSL Certificate based on which Certification Authority (CA) has issued the actual SSL Certificate. To determine this, the browser looks at its own internal list of trusted Certification Authorities (CA's). These are added into the browser by the browser vendor (such as Microsoft, Netscape and Mozilla).

Technical Information Support

Most SSL Certificates are issued by Certification Authorities (CA's) who own and use their own Trusted Root CA Certificates. We only issue SSL Certificates by trusted Certification Authorities (CA's) - this means they have already been added into the browser by the browser vendor and are regarded as highly trusted. Some newer SSL Certificates (such as Extended Validation (EV) SSL Certificates) may contain a Chained Certificate, however we will only provide Chained Certificates where the Certification Authority (CA) owns the Root Certificate associated with it.

Some Companies Issue Inferior SSL Certificates

Some Certification Authorities (CA's) do not have a Trusted Root CA Certificate present in browsers, or do not use a root that they own, and use a Chained Root in order for their SSL Certificates to be trusted. Essentially a Certification Authority (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 and may now be owned by the SSL Certificate issuer.

A Direct Relationship Is A Sign Of Stability & Trust

For a Certification Authority (CA) to have and use its own Trusted Root CA Certificate which is 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, Mozilla and Netscape) for the inclusion of their Trusted Root CA Certificates. For this reason, such Certification Authorities are seen as being considerably more credible and stable than Chained Root SSL 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 (CA's) who have and use their own root certificates by viewing the list in your browser. We do not recommend the use of an SSL Certificate from a vendor that does not have a direct relationship with the browser vendor.

TCP vs QUIC - The Modern Secure Alternative

TCP vs QUIC - The Modern Secure Alternative

Both TCP and QUIC will continue serving important roles as internet infrastructure evolves. Understanding where each protocol is heading helps plan long-term technology decisions.

TCP vs QUIC - The Modern Secure Alternative

Both TCP and QUIC will continue serving important roles as internet infrastructure evolves. Understanding where each protocol is heading helps plan long-term technology decisions.

Understanding HTTP Status Codes - A Complete Guide

Understanding HTTP Status Codes - A Complete Guide

HTTP status codes fall into five groups, each identified by its first digit. This simple numbering system makes it easy to understand the general meaning of any code you encounter,...

Understanding HTTP Status Codes - A Complete Guide

HTTP status codes fall into five groups, each identified by its first digit. This simple numbering system makes it easy to understand the general meaning of any code you encounter,...

How to Redirect HTTP to HTTPS Using .htaccess

How to Redirect HTTP to HTTPS Using .htaccess

Simply installing an SSL Certificate does not automatically force all visitors to use the secure connection. Without a redirect in place, your website remains accessible through both HTTP and HTTPS,...

How to Redirect HTTP to HTTPS Using .htaccess

Simply installing an SSL Certificate does not automatically force all visitors to use the secure connection. Without a redirect in place, your website remains accessible through both HTTP and HTTPS,...

WHOIS for SSL Certificate Validation - Depreciated

WHOIS for SSL Certificate Validation - Depreciated

Current verification methods for SSL Certificates provide robust online security now that traditional methods like WHOIS lookups are obsolete. Several proven approaches are available to streamline the validation process while...

WHOIS for SSL Certificate Validation - Depreciated

Current verification methods for SSL Certificates provide robust online security now that traditional methods like WHOIS lookups are obsolete. Several proven approaches are available to streamline the validation process while...

SSL Certificates and Certification Authority Authorization (CAA) Records

SSL Certificates and Certification Authority Au...

Understanding Certification Authority Authorization (CAA) records, why they exist, and how to configure them correctly helps ensure your SSL Certificate orders complete successfully without delays caused by authorization failures.

SSL Certificates and Certification Authority Au...

Understanding Certification Authority Authorization (CAA) records, why they exist, and how to configure them correctly helps ensure your SSL Certificate orders complete successfully without delays caused by authorization failures.

SSL Certificate Maximum Validity Periods and Multi-Year Purchasing

SSL Certificate Maximum Validity Periods and Mu...

SSL Certificate validity periods have undergone dramatic changes since the early days of web encryption. Understanding this history helps explain why the current system exists and where it is heading...

SSL Certificate Maximum Validity Periods and Mu...

SSL Certificate validity periods have undergone dramatic changes since the early days of web encryption. Understanding this history helps explain why the current system exists and where it is heading...

1 / 6