SSL.com EV Code Signing Certificate
Give your software a verified organizational identity while meeting the requirements that matter for Windows Code Signing requirements, hardware workflows and higher assurance software distribution.
1 year purchase term. Longer terms are available with lower annualized pricing.
View SSL.com EV CertificateWhen EV Code Signing Is the Right Choice
EV is not simply a more expensive version of OV. Its strongest commercial value comes from the situations where higher assurance validation and specific Windows signing capabilities are part of the technical requirement.
Windows Drivers
EV is relevant when your product includes applicable Windows 10 or Windows 11 kernel mode or user mode drivers and the associated Microsoft signing requirements.
Hardware Ecosystem
EV is designed for applicable Microsoft Partner Center and Windows Hardware Dev Center workflows, including driver submission and WHQL related processes.
Higher Assurance Publishing
Organizations distributing software can associate their verified legal identity with signed applications, installers and other supported Authenticode objects.
SSL.com EV Pricing
SSL.com offers several validation levels. The annualized price decreases as the purchase term increases.
| Purchase term | Annualized price | Approximate total |
|---|---|---|
| 1 year | $349/year | $349 |
| 2 years | $299/year | $598 |
| 3 years | $249/year | $747 |
| 4 years | $200/year | $800 |
| 5 years | $149/year | $745 |
Certificate purchase pricing does not include separate key storage, cloud signing or expedited validation charges.
Compare EV With Other Code Signing Options
Check whether your release requirements justify Extended Validation or whether an organization validated OV certificate is sufficient for your software distribution needs.
Compare Certificate OptionsWhat SSL.com Actually Validates
Extended Validation goes beyond simply checking that an organization exists. SSL.com describes an EV process that verifies organizational information under the applicable EV procedures and associates that verified identity with the software signature.
Organization verification
The applicant provides organizational information and completes the required validation steps, agreements and callback process.
Publisher identity
The verified organization identity becomes available through the certificate and Authenticode signature details, helping customers and security teams determine who published the software.
Standard validation time
SSL.com currently describes standard validation as approximately 3 to 5 business days. Expedited validation is available for an additional fee.
Organization requirement
Standard SSL.com EV Code Signing is intended for organizations and requires organizational validation. Individuals without a registered business have a separate Sole Proprietor EV product.
Protect the EV Signing Key Without Weakening Your Pipeline
EV signing requires protected private key handling. SSL.com provides several deployment models, allowing teams to choose between physical hardware and cloud based signing according to their release process.
Hardware token
SSL.com lists a $379 YubiKey option. The company also warns that this hardware may not satisfy requirements for some EV use cases, particularly kernel mode driver signing, so compatibility should be confirmed before purchase.
Customer managed HSM
SSL.com lists customer managed cloud HSM options starting at $500, with provider specific attestation fees. On premises HSM support is also available with customized pricing.
eSigner cloud HSM
eSigner keeps the private signing key protected inside a cloud HSM and allows approved signing operations from automated environments without placing an exportable key on the build server.
eSigner for Automated EV Signing
For teams releasing software frequently, a remote signing service can remove the operational friction of connecting physical hardware to every build while keeping the signing key protected.
SSL.com describes eSigner support for environments such as GitHub Actions, Jenkins and Azure DevOps.
| eSigner tier | Monthly price | Included signings | Credentials |
|---|---|---|---|
| Tier 1 | $15/month | 240 | 1 |
| Tier 2 | $63.75/month | 1,200 | 5 |
| Tier 3 | $131.25/month | 3,600 | 9 |
| Tier 4 | $187.50/month | 12,000 | 13 |
eSigner pricing is separate from the EV certificate purchase price.
EV Signing Across the Windows Release Cycle
EV can fit directly into a standard software release process, from source compilation through final signature verification.
Build
Compile the application, installer or driver from the approved source.
Test
Run functional and release validation before the signing stage.
Security checks
Complete the required security scanning and release controls.
Sign
Use the protected EV private key to apply the digital signature.
Timestamp
Apply a trusted timestamp so the signing event can remain verifiable after certificate expiration, subject to applicable trust requirements.
Verify and release
Verify the signature and timestamp before publishing the production artifact.
Windows Driver Signing Is a Major EV Differentiator
If your software includes Windows drivers, certificate selection becomes a technical decision rather than simply a trust or branding decision.
Kernel mode and user mode drivers
SSL.com identifies EV Code Signing as required for applicable Windows 10 and Windows 11 kernel mode and user mode driver signing workflows.
Hardware Dev Center
SSL.com also identifies EV as required for applicable Microsoft Partner Center and Windows Hardware Dev Center workflows, including driver submission and WHQL related processes.
EV Does Not Mean Instant SmartScreen Reputation
Older Code Signing content often presents EV as a guaranteed way to remove SmartScreen warnings. That positioning is no longer accurate.
SSL.com states that since March 2024, EV and OV certificates build SmartScreen reputation through download volume rather than EV receiving a separate instant reputation advantage.
EV still has substantial value where higher validation and Windows driver or hardware workflows are required. SmartScreen reputation, however, should be treated as a separate trust signal that develops as software gains download history.
EV vs OV vs Sole Proprietor EV
Choose the certificate around the identity you need to validate and the Windows capabilities your software actually requires.
| Feature | SSL.com EV | SSL.com OV | Sole Proprietor EV |
|---|---|---|---|
| Validation | Extended Validation | Organization Validation | Individual EV |
| Registered organization | Yes | Yes | No |
| Standard Windows signing | Yes | Yes | Yes |
| Kernel mode driver signing | Yes | No | Yes |
| Windows Hardware Dev Center | Yes | No | Yes |
| eSigner | Supported | Supported | Supported |
| Current 1 year price | $349 | $129 | $359 |
| Best suited for | Companies, drivers and hardware workflows | General organizational software distribution | Independent developers and sole proprietors |
Review SSL.com Certificate Options Before Buying
Compare SSL.com’s certificate range and validation levels before choosing the product that matches your organization, software distribution workflow and signing requirements.
Explore SSL.com CertificatesCodeSignTool and Remote Signing
SSL.com also provides CodeSignTool for remote signing through eSigner. It supports Microsoft Authenticode and Java code objects and can be incorporated into batch signing and CI/CD workflows.
Remote signing
The signing operation is performed through the eSigner service rather than requiring the private key to be exported into the build environment.
Artifact minimization
SSL.com describes a hash based signing model that sends hashes to SSL.com for signing rather than sending the complete code itself.
SSL.com EV Code Signing Specifications
| Validation | Extended Validation |
|---|---|
| Organization required | Yes |
| 1 year price | $349 |
| 2 year annualized | $299 |
| 3 year annualized | $249 |
| 4 year annualized | $200 |
| 5 year annualized | $149 |
| Kernel mode drivers | Supported |
| Windows Hardware Dev Center | Supported |
| Microsoft Authenticode | Supported |
| Hardware token | Supported |
| Cloud HSM | Supported |
| eSigner | Supported |
| CI/CD | Supported |
| Timestamping | Supported |
| Standard validation | 3 to 5 business days |
| Expedited validation | Available for additional fee |
Frequently Asked Questions
What is an SSL.com EV Code Signing Certificate?
It is an Extended Validation Code Signing Certificate for organizations that need higher assurance publisher validation and EV specific capabilities such as Windows driver signing.
How much does SSL.com EV Code Signing cost?
The current one year price is $349. SSL.com lists $299 per year for two years, $249 for three years, $200 for four years and $149 for five years.
Does SSL.com EV Code Signing require a company?
Yes. The standard EV product requires organization validation. Individuals without a registered business can consider SSL.com's separate Sole Proprietor EV product.
Can SSL.com EV Code Signing sign Windows drivers?
Yes. SSL.com identifies EV Code Signing as required for applicable Windows 10 and Windows 11 kernel mode and user mode driver signing workflows.
Can SSL.com EV Code Signing be used with Windows Hardware Dev Center?
Yes. SSL.com identifies EV as required for applicable Microsoft Partner Center and Windows Hardware Dev Center workflows, including driver submission and WHQL related processes.
Does EV Code Signing remove SmartScreen warnings?
No. Since March 2024, EV certificates no longer receive a distinct automatic SmartScreen reputation advantage. EV and OV build reputation through download volume.
Can I use eSigner with SSL.com EV Code Signing?
Yes. SSL.com's eSigner for Code supports EV certificates and provides cloud HSM backed signing for CI/CD environments.
Do I need a physical hardware token?
Not necessarily. SSL.com offers hardware token, customer managed HSM and eSigner cloud HSM options.
Can I use a YubiKey for SSL.com EV Code Signing?
SSL.com lists a $379 YubiKey option but warns that it may not satisfy EV requirements for some use cases, particularly kernel mode driver signing. Confirm compatible hardware before purchasing.
Can I use SSL.com EV Code Signing with GitHub Actions?
Yes. SSL.com lists GitHub Actions among the CI/CD environments supported by eSigner for Code.
Does SSL.com EV Code Signing support Microsoft Authenticode?
Yes. SSL.com supports Microsoft Authenticode signing with its EV Code Signing certificates.
Should I choose SSL.com EV or OV?
Choose EV when you need capabilities such as Windows kernel mode driver signing, applicable Windows Hardware Dev Center workflows or the EV validation level. For ordinary organizational software distribution, OV is generally the less expensive option.