OV Code Signing
OV Code Signing
Put your organization's name on every binary you distribute. OV Code Signing verifies and displays your verified company name, preventing “Unknown Publisher” warnings and building user trust from the first click.
Key Benefits
Organization name on installer
Your verified company name displayed when users install your software: eliminating “Unknown Publisher” warnings.
Tamper-evident signing
Any modification after signing cryptographically breaks the signature: Windows, macOS, and inspection tools detect tampering before the binary runs, protecting users from altered or repackaged software.Trusted on all Windows versions
OV certificates prevent untrusted-publisher warning messages on Windows 11, Windows 10, Windows Server 2025, Server 2022, Server 2019, and every earlier supported Windows release with Authenticode.Unlimited rekeys and reissues
Full operational flexibility: rekey or reissue the certificate at no additional cost throughout its lifetime, useful for HSM migrations, key rotation policies, or responding to compromise.Who Is It For?
Software companies & ISVs
Distributing applications to end users who need to see a verified organization name on the installer.
Enterprise IT teams
Enterprise IT teams distributing internal tooling, management agents, custom utilities, and patch packages where a recognized corporate publisher name is required for software governance and GPO allowlisting.Open source organizations
Open source organizations with a registered legal entity that want the organization’s verified name on distributed binaries: typical for foundations, vendor-backed projects, and maintainer collectives.Any organization shipping software
Any organization shipping software that wants its verified legal name on every installer screen without the extended validation requirements or hardware-token constraints of EV Code Signing.Purchase & Pricing
1. Select Certificate Duration
2. Select Key Storage & Delivery (optional)
eSigner Cloud Signing
Sign anywhere using eSigner.com. No hardware required.YubiKey
Physical TokenStandard
3–5 business days after validation (Continental US)Express + $329.00
1 day after validationBring Your own Cloud HSM
Self-managed infrastructureSSL.com must attest your key to your chosen provider before issuing the certificate. This fee is a one-time charge per order.
Looking for a simpler option? SSL.com eSigner for Code provides cloud-based signing with no HSM to provision, no attestation fee, and a lower total cost for most teams.
Bring your own on-premises HSM
SSL performs an attestation ceremony for your compliant on-premises HSM.Please contact sales.
3. Validation Speed (optional)
Choose how quickly your organization or identity is validated before your certificate is issued.
Standard
3–5 day validation · 2–3 day US shipping Validation completed after all agreements, entity info submitted, and a successful callback to a listed phone number. IncludedExpedited
2 business day validation · overnight US delivery 2 business days priority validation from first complete submission and callback. Token shipped overnight in continental US. +$599.00Order Summary
How It Works
1: Purchase
Select OV duration and complete your order.
2: Organization validation
SSL.com validates your organization using business registration documentation.
3: Certificate issued
Certificate issued with your verified organization name. Install on a FIPS token or enroll in eSigner for cloud signing.
4: Sign your code
Users see your organization's name on the installer screen.
5: Timestamp
Timestamp at signing to extend signature validity beyond certificate expiry.
Compliance & Standards
CA/B Forum Code Signing BR
WebTrust for Code Signing BR
Microsoft Authenticode
Frequently Asked Questions
OV signs with your organization's name and is trusted on Windows. EV provides the strongest verified publisher identity in SmartScreen prompts and is required for kernel-mode driver signing. Note: since 2024, Microsoft no longer grants EV-signed binaries immediate SmartScreen reputation: reputation builds through download volume for both OV and EV.
Each certificate is issued to the organization but should be used by a single authorized signer. For multiple signers, each needs their own certificate or use a shared eSigner account.
No: if you timestamp at signing time, the signature remains valid indefinitely even after the certificate expires.
Yes: eligible for 30-day unconditional refunds per SSL.com's refund policy.
Ready to get OV Code Signing?
Related Products
IV Code Signing
EV Code Signing
eSigner for Code
Cloud HSM signing for CI/CD pipelines: no hardware token required. Works with OV certificates.