Sectigo Code

Frequently asked questions

• What is a Sectigo Code Signing Certificate?

  A Sectigo Code Signing Certificate allows developers to digitally sign software, scripts, and executables to verify the authenticity and integrity of their code.

• How long does it take to get issued?

  Standard Code Signing: 1–3 business days

  EV Code Signing: 1–5 business days (requires stricter validation)

• Can I renew the certificate?

  Yes, you can renew before expiry. If expired, a new vetting process is required.

• What documents are needed?

  Your identity (for individuals)

  Your company registration (for organizations)

  A phone number from a public directory
  EV also requires hardware token or USB key delivery.

• Can I install it on multiple devices?

  Standard certificates can be exported/imported. EV certificates require hardware token, limiting use to one secure device (or via HSM/USB).

• Does it support all major platforms?

  Yes. Sectigo Code Signing works with:

  Microsoft Windows, macOS (with EV), Java, Adobe AIR, Microsoft Office macros & PowerShell

• Why do I need a Code Signing Certificate?

  It assures users that your code is from a trusted publisher and has not been tampered with. It prevents “Unknown Publisher” warnings during installation.

• What is timestamping and why is it important?

  Timestamping lets your signature remain valid even after the certificate expires, as long as it was signed during the certificate’s validity period.

• Who should use this certificate?

  Software developers, publishers, and companies who distribute:

  Desktop apps (.exe, .dll, .cab), Drivers, Java, PowerShell, or VBA scripts, macOS and iOS apps

• What are the benefits of using Sectigo Code Signing?

  • Eliminates “Unknown Publisher” warnings

  • Confirms code integrity and authenticity

  • Boosts user trust and download rates

  • Meets platform requirements (Microsoft, macOS, etc.)

  • Timestamping ensures the signature stays valid even after the cert expiry

• What’s the difference between Standard and EV Code Signing?

  Standard Code Signing: Easier to get, issued to individuals or organizations

  EV Code Signing: Higher trust, required for Windows driver signing, stronger vetting, and automatic SmartScreen reputation boost

• Is the certificate secure against misuse?

  Yes, especially EV Code Signing, which is stored on a secure hardware token. This prevents theft or misuse of your private key.

• How long is a Sectigo Code Signing certificate valid?

  It can be purchased for 1 to 3 years, but the signature can remain trusted beyond that if timestamped.

• How do I sign my software?

  Use tools like: Microsoft SignTool, Java jarsigner, PowerShell or macOS codesign. You apply the digital signature with your private key.

• What happens if I lose the private key or token?

  You’ll need to request a reissue. For EV certificates, a new token may need to be shipped. Always back up your key securely.