Compare specialized certificate types
Specialized certificate types support use cases beyond TLS, including software integrity, document authenticity, user authentication, email security, and regulatory compliance.
Code signing certificates
Confirms the identity of the software publisher
Ensures that code has not been altered after signing
Establishes trust with operating systems and end users
Common use cases: distributing software, signing executables, scripts, or installers
Document signing certificates
Verifies the identity of the document signer
Ensures that document content has not been altered
Supports digital signature workflows
Common use cases: contracts, agreements, and compliance-driven documents
Client certificates
Provides strong identity-based authentication
Eliminates reliance on passwords alone
Supports mutual TLS (mTLS) authentication
Common use cases: internal systems and API access
S/MIME certificates
Encrypts and digitally signs email communications
Common use cases: secure email for employees and organizations
VMC and CMC certificates
Display verified brand logos in supported email clients
Common use cases: brand identity in email
Regional and regulatory certificates
Meet jurisdiction-specific requirements such as eIDAS, PSD2, or other compliance standards
Choosing a specialized certificate type
Required function | Certificate type |
|---|---|
Software integrity | Code signing |
Document authenticity | Document signing |
User authentication | Client certificate |
Email security | S/MIME |
Brand identity in email | VMC or CMC |
Regulatory compliance | Regional or regulatory certificate |
What's next
Review business SSL certificates in CertCentral to understand OV and EV certificates for public-facing websites