Code Signing Checker

Check if a certificate has code signing capabilities

About Code Signing Certificates

A code signing certificate is a digital certificate used by software developers to sign executables, scripts, and installers to verify the software's authenticity and integrity. Our Code Signing Certificate Checker analyzes a certificate's Extended Key Usage (EKU) extension to determine if it has the code signing purpose set, which is essential for distributing trusted software on Windows, macOS, and other platforms.

How to Use

Enter the domain name of the server hosting the certificate to check.
Click Check to fetch and analyze the certificate's EKU extension.
Review whether code signing is supported based on the EKU analysis.
Examine additional certificate details like subject, issuer, and key algorithm.

Use Cases

Software Distribution: Verify that your signing certificate has the correct EKU before distributing signed software.
Vendor Verification: Check third-party certificates to confirm their code signing capabilities.
Certificate Inventory: Audit certificates in your organization to identify which support code signing.
CI/CD Integration: Validate code signing certificates before automated build and release pipelines.

Frequently Asked Questions

The EKU extension specifies the intended purposes of a certificate. Common values include Server Authentication, Client Authentication, and Code Signing. A certificate must have the Code Signing EKU (1.3.6.1.5.5.7.3.3) to be valid for signing software.

Generally no. TLS (server) certificates and code signing certificates serve different purposes and have different EKU extensions. A standard TLS certificate cannot be used to sign code, and vice versa. Some cross-certificates exist but are rare and not recommended for security reasons.

Code signing assures users that software has not been tampered with and comes from a verified publisher. Operating systems like Windows, macOS, and mobile platforms require valid code signatures to run applications without security warnings. It also helps maintain the integrity of software supply chains.

Tips & Best Practices

•Use code signing certificates to establish trust with users
•Timestamp signed code to ensure validity after certificate expiry
•Protect private keys with hardware security modules (HSMs)
•Monitor code signing certificate usage for unauthorized signing

Technical Details

Certificate: Code signing certificate validation and analysis
Signature: Digital signature verification and validation
Timestamp: Timestamp server support and validation
Output: Code signing status with trust and validity information