Branded Issuing CA
Your name in the certificate chain, publicly trusted from day one
A Branded Issuing CA is an intermediate CA under SSL's publicly trusted root, with your organization's name in the CA field of every certificate. Offered by consultation, and hosted and operated by SSL.
Your name in the certificate chain. SSL's trusted root underneath.
When SSL issues you a Branded Issuing CA, your organization receives an X.509 intermediate CA certificate signed by SSL’s publicly trusted root. The issuing CA’s subject contains your organization’s name, so certificates you issue carry your brand in the CA field, not SSL’s.
A Branded Issuing CA is publicly trusted and available for DV, OV, and EV TLS/SSL, S/MIME, and Code Signing. It covers public-trust certificates only. For private or internal use, see Private Compliance PKI or Managed PKI Certificates.
What your customers and end users see:
Certificate issued by: Your Organization
The issuing CA visible to certificate inspectors, security tools, and enterprise trust configurations carries your organization's name, not SSL's.
Publicly trusted from day one
Chains to SSL's globally trusted root, so it is trusted immediately by every browser and operating system, exactly as SSL's own issuing CAs are. No browser warnings.
No root distribution required
SSL handles root program membership (Mozilla, Microsoft, Apple, etc.), ongoing root store maintenance, and compliance obligations above your Issuing CA.
CA/B Forum compliant
SSL's root program compliance obligations flow down to your Issuing CA, so certificates issued must comply with CA/B Forum Baseline Requirements.
You appear as the CA; SSL hosts and operates it and maintains the root. Every certificate your Branded Issuing CA issues is trusted by every browser and operating system immediately, without any root distribution effort on your part.
Key benefits
Your brand in the CA field
Certificates carry your organization's name in the issuing CA field, visible to certificate inspectors, security tools, and enterprise trust configurations.
Publicly trusted from day one
Chains to SSL's globally trusted root, trusted by every browser and operating system immediately.
No root management
No Root CA key, no Key Ceremony, no root program applications, SSL handles the full chain above your Issuing CA.
CA/B Forum compliant
SSL's root program compliance obligations flow down to your Issuing CA; certificates issued must comply with Baseline Requirements.
HSM-backed sub-CA key
Your Issuing CA private key is stored in FIPS-compliant hardware under SSL's infrastructure.
Defined certificate profiles
Certificate profiles for your Issuing CA are defined per the CA/B Forum requirements and your use case.
Is a Branded Issuing CA right for you?
A Branded Issuing CA puts your organization’s name in the public certificate chain. We build these with organizations that bring:
- an established, recognized brand in their market
- a large customer base and committed annual certificate volume
- access to a market, region, or regulated sector that is hard to reach under the SSL brand
- security, legal, and operational teams ready to meet root program obligations
- a multi-year commitment, with fees paid annually in advance
Not sure where you fit? Talk to our PKI team. We scope every Branded Issuing CA by consultation. If a branded CA is not the right fit, our reseller program lets you offer SSL-branded certificates, often the faster route.
Talk to a PKI specialist
In the message box, tell us about your organization, your expected certificate volume, which types you need (DV, OV, EV, S/MIME, or Code Signing), and your compliance contact. Our PKI team scopes every Branded Issuing CA by consultation and will contact you to discuss your programme.
Important constraints
CA/B Forum Baseline Requirements apply
Because your Issuing CA chains to SSL's publicly trusted root, all certificates issued must comply with CA/B Forum Baseline Requirements, domain and identity control must be validated per BR rules.
No private or internal namespaces
This Issuing CA cannot issue certificates for private namespaces, internal-only names, or non-FQDN identifiers. For private certificate needs, see Managed PKI Certificates or Dedicated PKI.
Subject to SSL audit obligations
Your issuance operations are subject to SSL's CP/CPS constraints and the same audit program that governs our public trust platform.
SSL hosts and operates your CA
Your Branded Issuing CA is hosted and operated by SSL, on the same infrastructure that underpins our public trust platform.
Publicly disclosed, shared accountability
Your Branded Issuing CA is publicly disclosed under your organization's name. SSL remains accountable to the root programs for every certificate issued, so an incident on your CA is also an SSL incident.
TLS issuance is serverAuth-only
A Branded Issuing CA for TLS issues serverAuth certificates only. Client authentication needs a separate Issuing CA.
How engagement works
Compliance & standards
CA/B Forum Baseline Requirements
All certificates issued under your Issuing CA must comply with CA/B Forum Baseline Requirements, enforced through SSL's CP/CPS.
WebTrust for CAs
SSL's root operations are covered by an annual WebTrust audit; your Branded Issuing CA operates within SSL's audit scope.
RFC 5280 (X.509)
FIPS-compliant HSMs
Your Issuing CA private key is stored in FIPS-compliant hardware under SSL's infrastructure.
Frequently asked questions
End users inspecting the certificate will see your organization's name as the issuing CA. The root CA, which SSL controls, will appear in the full chain, but the issuing CA visible to most users and tools will carry your name.
SSL hosts and operates it on SSL's infrastructure, the same infrastructure that underpins our public trust platform. Your organization receives the branded CA; certificates you issue are issued through SSL's issuance API.
Your Branded Issuing CA is publicly disclosed under your organization's name, and SSL remains accountable to the root programs for every certificate issued under its roots. An incident affecting your CA is therefore also an SSL incident, and SSL may require remediation or revoke the Issuing CA.
Pricing is by consultation and depends on your programme. Talk to our PKI team.
Yes, because the Issuing CA chains to SSL's publicly trusted root, all issuance must comply with CA/B Forum Baseline Requirements. SSL's audit obligations and CP/CPS constraints apply to your Issuing CA. This is the fundamental difference between a Branded Issuing CA (publicly trusted, BR-constrained) and a Dedicated Private PKI (not publicly trusted, full policy flexibility).
A Branded Issuing CA is available for DV, OV, and EV TLS/SSL, S/MIME, and Code Signing. Each Issuing CA is scoped to a single use case at a single validation level, and all certificates must comply with CA/B Forum requirements. A TLS Issuing CA issues serverAuth certificates only; client authentication needs a separate CA. Talk to our PKI team to discuss the profiles and EKUs for your use case.
No, because this Issuing CA chains to a publicly trusted root, it cannot issue certificates for private namespaces or internal-only identifiers that violate BR requirements. For that use case, see Managed PKI Certificates or Dedicated PKI.
As the trust chain depends on SSL's root, any distrust of SSL's root would affect certificates issued by your Issuing CA. SSL maintains full compliance with all major root programs to protect against this risk.
Ready to talk to a PKI specialist?
Related Products
Private Compliance PKI
Need your own Root CA + WebTrust audit coverage, full hierarchy ownership.
Private Enterprise PKI
Need your own Root CA for internal use, no public trust constraints.