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.

Most Popular Questions

Understand the difference between Trusted Root SSL Certificates and Chained Root SSL Certificates, and why Trustico® only provides SSL Certificates from Certification Authorities that own their own root certificates.

What Are Chained Root SSL Certificates?

A Chained Root SSL Certificate is issued by a Certification Authority (CA) that does not have its own Trusted Root CA Certificate present in browsers. Instead, it relies on a chain back to another CA's root certificate to inherit browser trust. Trustico® only provides SSL Certificates from Certification Authorities that own and use their own root certificates.

How Does Your Browser Decide Whether Trusting an SSL Certificate?

Your browser checks its internal list of trusted Certification Authorities (CAs), which are added by the browser vendor such as Microsoft or Mozilla. If the SSL Certificate was issued by a CA on this trusted list, or chains back to one, the browser will trust the connection.

Why Does Trustico® Only Offer SSL Certificates from CAs with Their Own Root Certificates?

Trustico® only provides SSL Certificates from Certification Authorities that have their own Trusted Root CA Certificates because this indicates long-term stability, credibility, and direct relationships with browser vendors. CAs that rely on chained roots from other providers are considered less stable and trustworthy.

How Can You Check Which Certification Authorities Are Trusted by Your Browser?

You can view the list of trusted Certification Authorities by accessing the certificate settings in your browser. This shows all CAs that have their own Trusted Root CA Certificates included by the browser vendor.

Ask Trustico® Assistant

For Instant Answers - Start Here When You Have a Question or Need Help

Website Security Checks : Essential Steps to Protect Your Business Online

Website Security Checks : Essential Steps to Pr...

Keep your website secure with the SSL Certificate checks that matter most, from expiry and chain coverage to validation levels, issuance controls, and automation.

Website Security Checks : Essential Steps to Pr...

Keep your website secure with the SSL Certificate checks that matter most, from expiry and chain coverage to validation levels, issuance controls, and automation.

Installing an S/MIME E-Mail Certificate in Mozilla Thunderbird

Installing an S/MIME E-Mail Certificate in Mozi...

Import a PKCS12 E-Mail Certificate into Mozilla Thunderbird, assign it for signing and encryption, and exchange secured messages with any recipient.

Installing an S/MIME E-Mail Certificate in Mozi...

Import a PKCS12 E-Mail Certificate into Mozilla Thunderbird, assign it for signing and encryption, and exchange secured messages with any recipient.

Repackaging a PKCS12 File for macOS Keychain Compatibility

Repackaging a PKCS12 File for macOS Keychain Co...

Fix PKCS12 imports that macOS Keychain Access rejects despite a correct password by re-exporting the file with legacy compatible encryption.

Repackaging a PKCS12 File for macOS Keychain Co...

Fix PKCS12 imports that macOS Keychain Access rejects despite a correct password by re-exporting the file with legacy compatible encryption.

Fixing the IIS Binding Error - A Specified Logon Session Does Not Exist

Fixing the IIS Binding Error - A Specified Logo...

Resolve the IIS binding error stating a specified logon session does not exist by repairing the Private Key association or reimporting correctly.

Fixing the IIS Binding Error - A Specified Logo...

Resolve the IIS binding error stating a specified logon session does not exist by repairing the Private Key association or reimporting correctly.

Converting a Java Keystore to PKCS12 Format

Converting a Java Keystore to PKCS12 Format

Convert a legacy Java KeyStore (JKS) to PKCS12 with one keytool command, verify the contents, and extract PEM files for non-Java platforms when needed.

Converting a Java Keystore to PKCS12 Format

Convert a legacy Java KeyStore (JKS) to PKCS12 with one keytool command, verify the contents, and extract PEM files for non-Java platforms when needed.

The 64 Character Limit on the Common Name Field

The 64 Character Limit on the Common Name Field

Understand the 64 character limit on the Common Name (CN) field, why long hostnames fail at CSR generation, and how Subject Alternative Names solve it.

The 64 Character Limit on the Common Name Field

Understand the 64 character limit on the Common Name (CN) field, why long hostnames fail at CSR generation, and how Subject Alternative Names solve it.

1 / 6