Overview

A digital signature on everything you ship, so users know it's really yours.

A code signing certificate lets you put a digital signature on executables, installers, drivers, scripts and macros. The signature does two jobs: it names you as the publisher after a certificate authority has checked who you are, and it seals the file — change a single byte after signing and the signature no longer verifies. Windows, browsers and antivirus tools read that signature before they decide how loudly to warn your users.

There are two assurance levels. OV (organisation-validated) is open to registered businesses and to individual developers. EV (extended validation) is for organisations only, carries the strictest vetting and is required for kernel-mode drivers. Since 2023 every private key must live on certified hardware, so XcellHost ships a FIPS token within India or sets the certificate up on your existing HSM — and prepares your MCA, GST or Udyam paperwork so validation doesn't stall.

Signs Windows apps & installers Drivers (EV) Java & scripts Office macros MSIX & app packages
How it works

Hash it, sign it on the token, verify it on install.

Code signing never encrypts your software. It fingerprints the file, locks that fingerprint with a key only you hold, and lets every user's computer check both.

01 · Hash

Your build is fingerprinted

The signing tool runs the finished file through SHA-256. The result is a short digest that changes completely if even one byte of the file changes.

  • SHA-256 digest of the whole file
  • Runs on your build machine or CI
  • Your source code is never sent anywhere
02 · Sign on the token

The digest is signed on hardware

The digest is sent to your FIPS 140-2 token or HSM, which signs it with your private key. The key never leaves the device — that's the rule since June 2023.

  • 3072-bit RSA or ECC key
  • Token PIN or HSM policy required
  • Trusted timestamp added (RFC 3161)
03 · Verify on install

Every user's PC checks it

On download and install, Windows re-computes the digest, checks it against your signature and walks the chain to Sectigo's root. Match: your name. Mismatch: a hard warning.

  • Publisher name shown, not "Unknown"
  • Tampered files fail instantly
  • Timestamp keeps old builds valid
The range

Four certificates. Two brands, two assurance levels.

Pick OV or EV first — that's the decision that matters. Sectigo and Comodo are one certificate authority under two names.

One-year certificates ship on a USB token. Two- and three-year terms are for keys on your existing HSM, reissued each year.

S
Sectigo

Sectigo Code Signing

OV

Organisation validation for companies, firms and individual developers. Your verified name replaces "Unknown Publisher".

  • Open toFirms & individuals
  • Issued in1–5 business days
  • Kernel driversNot eligible
  • Key storageFIPS token or HSM
₹26,999/ year
Highest assurance
S
Sectigo

Sectigo EV Code Signing

EV

Extended validation for registered organisations. Required for kernel-mode drivers and the strongest identity you can put on a file.

  • Open toOrganisations only
  • Issued in5–10 business days
  • Kernel driversEligible
  • Key storageFIPS token or HSM
₹34,999/ year
C
Comodo · by Sectigo

Comodo Code Signing

OV

The same OV certificate sold under the Comodo name — familiar to many buyers and procurement lists. Same roots, same vetting.

  • Open toFirms & individuals
  • Issued in1–5 business days
  • Kernel driversNot eligible
  • Key storageFIPS token or HSM
₹26,999/ year
C
Comodo · by Sectigo

Comodo EV Code Signing

EV

Extended validation under the Comodo name. Organisation-only vetting, driver-eligible, with reputation that builds as your downloads grow.

  • Open toOrganisations only
  • Issued in5–10 business days
  • Kernel driversEligible
  • Key storageFIPS token or HSM
₹34,999/ year

Comodo or Sectigo? Comodo's certificate business was renamed Sectigo in 2018. Both names are still sold, both chain to the same Sectigo roots and both go through the same validation. Choose the name your customers or procurement team already recognise — the trust on the user's screen is identical.

OV or EV · try it

Three questions. The right assurance level.

Answer for the software you ship. The recommendation updates as you go, with the reason and an indicative first-year price including the USB token.

1Is the buyer a registered company?
2Will you sign kernel-mode drivers (.sys)?
3Do enterprise or government buyers expect the highest assurance?
Recommended for you

Guidance only. Unsure? Ask us — we'll check your documents before you order.

Key delivery

A token in the post, or a key in your own HSM.

Since June 2023 the private key must be generated and kept on FIPS 140-2 Level 2 or Common Criteria EAL4+ hardware. You choose which.

Team outside India? International courier is ₹12,999 per token. Choose it in the configurator.

USB token · what happens1-year term
    Platforms & file types

    One certificate, every format you ship.

    The same code signing certificate works across Microsoft Authenticode, Java, Office and more. Filter by what you build.

    Windows executables

    .exe .dll .msi .cab

    Microsoft Authenticode — the signature Windows and SmartScreen check on download and install.

    SignToolOVEV

    Kernel-mode drivers

    .sys .cat

    Submitted through Microsoft's Hardware Dev Center for attestation signing. Requires an EV certificate.

    Partner CenterEV only

    Windows app packages

    .msix .appx .appxbundle

    Sign packages for side-loading and enterprise distribution outside the Store.

    SignToolOVEV

    PowerShell scripts

    .ps1 .psm1 .psd1

    Run under AllSigned or RemoteSigned execution policies without exceptions.

    Set-AuthenticodeSignatureOVEV

    Office & VBA macros

    .xlsm .docm .dotm .xlam

    Sign the VBA project so trusted-publisher policies let macros run.

    VBA editorOVEV

    Java archives

    .jar

    Sign applets, desktop apps and libraries so the JVM can verify the publisher.

    jarsignerOVEV

    Adobe AIR

    .air .airi

    Package AIR applications with your verified name in the installer.

    ADTOVEV

    Mozilla objects

    .xpi · legacy & enterprise

    For managed or legacy deployments. Public Firefox add-ons are signed by Mozilla itself.

    signtool (NSS)OVEV

    Linux build servers

    Authenticode from Linux

    Sign Windows binaries in a Linux CI job with a PKCS#11 token or HSM.

    osslsigncodeOVEV
    Validation requirements

    What Sectigo checks, and the Indian documents that clear it.

    Tick what you already have. The meter shows how ready you are to order — we'll help with anything missing before the order goes in.

      Tick the documents you have.

      Typical time1–5 days
      Then couriertoken in India
      Policy changes

      Three rule changes every publisher should know.

      Code signing rules are set by the CA/Browser Forum and by Microsoft. Here is what changed, and what it means when you buy today.

      Today
      June 2023 · CA/B Forum

      Keys must live on hardware

      Private keys for OV and EV code signing must be generated and stored on a FIPS 140-2 Level 2 or Common Criteria EAL4+ device — a USB token or an HSM. Downloadable .pfx files are no longer issued.

      For you: choose token delivery or your HSM at checkout.
      March 2024 · Microsoft

      EV no longer skips SmartScreen

      SmartScreen stopped giving EV-signed files an instant pass. EV still carries the highest assurance, but every new certificate builds reputation as clean downloads accumulate — same as OV.

      For you: plan for reputation to build over the first weeks of downloads.
      February 2026 · CA/B Forum

      One-year certificates

      New code signing certificates are issued for at most about a year. HSM-based orders can be bought for up to three years, with a fresh certificate reissued each year.

      For you: token orders are 1-year; 2–3 years need your HSM.
      Pricing

      Per certificate, per year — token included in the total.

      Pick a certificate, how you want the key delivered, the term and how many developers need one. All prices are indicative and exclude 18% GST.

      VALIDATION HELP INCLUDED
      SSectigo
      XcellSign · Code Signing

      Sectigo Code Signing

      OV · per certificate · firms & individuals
      Validation · issued inOV · 1–5 business days
      Key storageFIPS token or HSM
      Starting from₹18,999 / year
      OV · 3-year term on your HSM
      1 year₹26,999 / year
      3 years · HSM₹18,999 / year
      3 years vs yearly renewalsSave ₹24,000
      Configure & Buy →
      Indicative · excl. 18% GST

      Choose a certificate

      ₹7,999USB token · India courier
      ₹12,999USB token · international
      ₹0Install on your HSM
      ₹4,999Signing setup service

      Prices are indicative placeholders until confirmed on your quotation. Multi-year terms are billed upfront and need an existing HSM; the certificate is reissued every year.

      Certificate
      Key delivery
      Term 1 year
      One certificate per signing identity. Each USB token holds one key — order one per developer or build machine. Over 100? Ask for a quote.
      Your estimate
      ₹0
      for 1 year, excl. GST
      Sectigo OV · 1 × 1 yr × ₹26,999₹0
      USB token · India · 1 ×₹0
      Signing setup · not added₹0
      Saving · choose 2–3 years on HSM₹0
      Validation help & renewal trackingIncluded
      GST (18%)₹0
      Payable incl. GST₹0
      Per certificate · per yearincl. token
      Indicative · excl. 18% GST. Validation time depends on your documents and the verification call. Refund terms confirmed on your quotation.
      What you get with XcellHost

      Powered by Sectigo. Validated, shipped and set up by XcellHost.

      Vetting, token delivery and wiring signing into your build are where teams lose weeks. We take that work on.

      INR billing with GST

      One GST invoice in rupees for certificates, tokens and services — pay by UPI, card, net banking or transfer.

      01
      Validation hand-holding

      We match your MCA, GST or Udyam records, prepare the authorisation letter and line up the verification call.

      02
      Token couriered in India

      The FIPS token is shipped to your office, with the PIN set-up and driver steps explained before it arrives.

      03
      Signing setup help

      SignTool, jarsigner, osslsigncode and CI jobs on Azure DevOps, GitHub Actions or Jenkins — configured and test-signed.

      04
      Renewals tracked

      Reminders at 60, 30 and 7 days, and the yearly reissue on multi-year HSM plans handled for you.

      05
      24×7 support from Mumbai

      Token not detected the night before a release? Our NOC answers on phone, WhatsApp and tickets, round the clock.

      06
      SignTooljarsignerosslsigncodeSafeNet Authentication ClientAzure DevOpsGitHub ActionsJenkinsAzure Key VaultAWS CloudHSMPowerShell