Browser Ubiquity

Browser root ubiquity is an important requirement when deciding on a Certificate Authority (CA) for your SSL Certificates. Many Certificate Authorities claim 99% browser ubiquity, but this claim does not mean that every SSL Certificate will activate without triggering a security warning in a browser.

Our SSL Certificates Work With All Known Browsers

Newer or smaller Certificate Authorities (CA) may not have had their roots included in the root store for some browsers, this is especially an issue for older browsers.

All SSL Certificates issued by Trustico® are prominent in new and older browsers, which means they are compatible with 99.9% of client platforms and browsers.

In the past, some Certificate Authorities roots have not been included when a new browser version was released, causing browser error messages for website visitors. This can have a serious effect on sales conversion and reputation for a website owner.

To ensure a continued high level of browser ubiquity, Trustico® only provide SSL Certificates from reputable Certificate Authorities (CA).

Most Popular Questions

Understand browser ubiquity and why SSL Certificates from Trustico® work seamlessly across 99.9% of browsers and client platforms without triggering security warnings.

What Does Browser Ubiquity Mean for SSL Certificates?

Browser ubiquity refers to how widely a Certificate Authority's root certificates are recognized by web browsers. High ubiquity ensures your SSL Certificate is trusted automatically without triggering security warnings that could drive visitors away from your website and hurt sales conversion.

Will the SSL Certificate Work with Older Browsers?

SSL Certificates from Trustico® are compatible with 99.9% of client platforms and browsers, including older versions. Trustico® only provides SSL Certificates from reputable Certificate Authorities whose roots are included in both new and legacy browser root stores.

Why Do Some SSL Certificates Trigger Browser Security Warnings?

Security warnings occur when a browser does not recognize the Certificate Authority that issued the SSL Certificate. This typically happens with newer or smaller Certificate Authorities whose roots have not been included in all browser root stores, particularly older browsers.

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