Communication with Uplynk services is protected and encrypted in-transit over the open internet using industry-standard TLS (Transport Layer Security).

To ensure maximum compatibility with the public certificate authorities (CAs) that Uplynk uses to sign our TLS certificates, you should ensure the device, browser, app, or player trusts the root CAs described below.

Root CA Certs

Uplynk platform uses TLS certs signed by:

• Amazon (https://www.amazontrust.com/repository#certification-authorities)
  • CN=Amazon Root CA 1,O=Amazon,C=US
  • CN=Amazon Root CA 2,O=Amazon,C=US
  • CN=Amazon Root CA 3,O=Amazon,C=US
  • CN=Amazon Root CA 4,O=Amazon,C=US
  • CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies, Inc.,C=US,S=Arizona,L=Scottsdale
• Sectigo (https://www.sectigo.com/faqs/detail/Sectigo-Chain-Hierarchy-and-Intermediate-Roots)
  • CN=USERTrust RSA Certification Authority,O=The USERTRUST Network,C=US
  • CN=COMODO RSA Certification Authority,O=COMODO CA Limited,C=GB
• Digicert (https://knowledge.digicert.com/general-information/digicert-trusted-root-authority-certificates#otherroots)
  • C=US, O=DigiCert Inc, OU=www.digicert.com, CN=DigiCert Global Root G2

Notes

Note 1: The above Public CAs may list multiple additional root CAs, but the certs required for Uplynk support are listed above, and is current as of January 2026. We may infrequently add new CAs to this list over time, as the vendors or cloud providers update or add root CAs.

Note 2: Most modern OSes, browsers, and major TLS client libraries already support these root CAs, and therefore typically do not require any explicit action on our customers' side. We do not recommend using custom or curated CA cert bundles as this can create long term maintenance burdens. However, if you have devices or apps requiring the use of custom CA trust stores or bundles, then you will need to explicitly include the root CAs listed above in your trust bundle(s).