Symantec Code Signing certificate Buy

Symantec Code Signing is a high-end certificate that allows developers and software companies to add a digital signature to an application distributed over the Internet. Any changes made in the code that are detected after the signature will invalidate the application and it will be marked as untrustworthy. A valid signature guarantees that the software the customer has acquired is really from the manufacturer.

OV certificate is saved in PC
1 Company name
Additional domains
Few days Issuing Time
100% Browser Recognition
  • Pricefrom {symantec_code_signing_price_us}
  • Validity1-3 years
  • Secures desktop and smartphone apps
  • Compatible w/all major browsers
  • Public key algorithm RSA
  • Symmetric encryption256 bit
  • Public key length2.048 (3.072/4.096) bits
  • Root CADigiCert Global G2
  • Money-back guarantee30 days
  • Certificate reissuefree and unlimited
  • Multi-domain support (SAN)N/A
  • Private key on tokenno

Recommended certificate use

The certificate finds its use especially in developers and software companies. They require their applications distributed over the Internet to be digitally signed and secured by the world's most recognized certification authority.

Symantec Code Signing price list

Symantec Code Signing can be used on all development platforms and you don't have to worry about incompatibilities.

The Symantec Code Signing certificate has been discontinued, the product is replaced by the DigiCert Code Signing certificate.

Displaying the certificate

If the application is correctly signed and trusted, no warning will be displayed to the user when they open the application. The publisher details are in the certificate and allow you to check app identity and integrity. You can find details of the certificate in the file’s digital signature properties. The signature shows the date of application signing, details about the certification authority, timestamp, etc.

Detail of the certificate Symantec Code Signing

Supported platforms

Choose the DigiCert Code Signing EV certificate for your application and platform.

  • Microsoft® Authenticode®

    The certificate is intended for signing .exe, .cab, .dll, .ocx, .msi, .xpi, and .xap files, as well as for signing kernel-mode applications. It is required for Microsoft Windows Logo certification.

  • Java

    The certificate designed for Java applications for desktop and mobile devices. Signs .jar files and is compatible with the Java Runtime Environment (JRE).

  • Microsoft® Office and VBA

    The certificate is intended for signing VBA objects and macros. Suitable for Microsoft Office and third-party VBA applications.

  • Adobe® AIR®

    Digitally signs .air or .airi files. Necessary for all AIR-based applications.

  • Android

    The certificate for signing .apk files for Android.

  • Microsoft Windows Phone

    Digitally signs the code for Windows Phone and Xbox 360. Signing is required to publish the application to the Microsoft App Hub.

  • Qualcomm BREW

    Digitally signs the code for BREW platform.

FAQ - Frequently Asked Questions

The application needs to be signed in order to be distributed – without a signature, mobile applications cannot be issued and a desktop application the operating system would block it and prevent it from running. Therefore, signing applications is unavoidable for their distribution.

On the Windows platform, the SmartScreen filter determines how trusted a reputation is. The SmartScreen filter used to be a part of Internet Explorer and nowadays it is a part of Windows. After signing and issuing an application, it takes some time before this reputation is created. Therefore, the Windows system might want to block it together with the digital signature. The solution to such a problem is only to use a signature with the Code Signing EV certificate, whose signature is always trusted and will not be blocked.

In general, the digital signature of an application itself does not guarantee trouble-free execution for users. For example, Java applets raise security warnings by nature of their platform, which is not considered too secure.
The signature can be done on any platform able to do it. Signing takes place through the given development platform's tools, referring to the repository containing the certificate or a specific file (PFX).
The Code Signing certificate can be signed by a code and applications for any platforms, it is not bound to one. Its typical use is for Microsoft Authenticode, but you can also sign Java applications with it.

From the perspective of the development environment, it again does not matter - the Code Signing certificate will work with any development environment that supports application and code signing. Windows typically uses Signtool, which is a part of the Windows SDK.

The only exception is with the Code Signing EV certificate - this type of certificate needs the Safenet support application for signing, which is available for Windows, Linux, and MacOS.