Certum · SimplySign cloud service
EV Code Signing Certificate
Extended validation for organizations that need to establish a verified software publisher identity. Choose an EV service for your procurement or platform requirements.
From $299/year
EV does not guarantee that new downloads bypass SmartScreen. Check the required validation, operator access and release workflow before ordering.
Compare Standard and EV code signingEV Code Signing
For organizations that need extended validation.
$299 USD total / 1 year
- Extended organization verification
- Certum SimplySign cloud signing
- No USB token shipped
- Timestamp compatible signing
Applicable taxes and the final payable amount are shown at checkout. 30-day refund policy.
All service terms and prices
Organization verification: prepare before ordering
Your certificate must identify an eligible organization. Certum checks the organization and the person authorized to act for it. Exact documents depend on your jurisdiction and application.
- Use the legal organization name and registration details consistently.
- Prepare the requested representative identity and authorization evidence.
- Use contact information that can be verified against the applicable records.
- Confirm country eligibility and documentation before relying on a release date.
Order, validate, activate, sign
- Select a service term and complete checkout.
- Submit the required verification information and respond to CA requests.
- After approval, activate the certificate and set up authorized SimplySign access.
- Sign and timestamp a release artifact, then verify the signature on the target system.
Issuance is subject to CA checks. Complete documentation helps avoid delays, but an order does not guarantee same-day approval. Read about validation timing.
EV and the Windows Hardware Developer Program
Microsoft requires an EV certificate for program registration. Driver submissions, testing and Microsoft approval remain separate requirements. An EV purchase alone does not make a driver approved for Windows distribution.
Publisher identity and SmartScreen reputation
A valid signature identifies the verified publisher and helps detect changes to signed code. Both Standard and EV signed files can still receive SmartScreen reputation warnings. EV does not guarantee a warning-free first download.
Check the format and distribution platform
| Distribution | What to check |
|---|---|
| Windows applications | Authenticode signing for formats such as EXE, MSI and DLL, using a compatible signing tool. |
| Java packages | JAR signing uses Java tooling and the receiving environment’s trust policy. |
| Native macOS distribution | Requires Apple’s Developer ID and notarization workflow; this certificate does not replace it. Apple requirements. |
| Linux and Android packages | Use their package ecosystem’s signing and trust requirements; a commercial certificate is not universally required. |
The operating system used to sign a file is different from the platform that will trust that file. Read the macOS guide.
Cloud signing and release automation
Certum SimplySign keeps the signing key in its cloud service. Its mobile and desktop applications connect an authorized operator to the certificate. You do not receive an exportable PFX or a USB token with this cloud offer. Confirm your build runner, operator access and authentication requirements before purchasing for unattended CI/CD.
Service term, reissues and timestamps
A two- or three-year purchase covers a service term, not one certificate valid for that entire period. Certum limits individual code signing certificates to 459 days from 27 February 2026 and provides reissues within longer product terms. Complete each reissue before the current certificate expires.
A trusted timestamp can allow a signature made while the certificate was valid to remain verifiable after expiry. Revocation, algorithms and platform trust policies still matter. Renew or reissue before signing new releases after expiry.
Support, refunds and renewal
My-SSL handles order support through the shop ticket system. Include your order number and describe the validation or signing problem. Review the published refund policy and checkout billing terms, and schedule certificate reissues before expiry.
Frequently Asked Questions
Answers to common questions about certificates and our services.
Who can apply for EV code signing?
EV code signing is for eligible organizations. Certum verifies organization information and the authorized representative. Confirm your organization type, jurisdiction and required documents before ordering. Individual developers can review the Standard code signing option.
Does EV code signing remove SmartScreen warnings?
No. EV does not guarantee a warning-free download or immediate SmartScreen reputation. Signed software can still trigger reputation warnings; a valid signature establishes publisher identity and code integrity.
Is a two-year or three-year service one long-lived certificate?
No. Certum limits individual code signing certificates to 459 days from 27 February 2026. Longer product terms require reissues during the service period. Follow the issuer’s reissue process before the current certificate expires.
Can I use EV for Windows driver distribution?
Microsoft requires an EV certificate for Hardware Developer Program registration. Registration, driver submission and applicable testing or approval are separate steps; buying an EV certificate alone does not certify or approve a driver.
Can I automate signing without an operator?
Verify SimplySign client compatibility and authentication requirements against your CI/CD environment before purchase. A cloud key is not a promise of unattended operation or unrestricted signing throughput.