GoGetSSL Logo
SSL CertificatesTrust solutions
Home Wiki SSL Basics / FAQ ECC, RSA, and SHA in SSL Certificates

ECC, RSA, and SHA in SSL Certificates

  • When you order an SSL certificate, two separate cryptographic concepts come into play: the key algorithm used to generate your key pair (ECC or RSA), and the signature hashing algorithm used by the Certificate Authority to sign the certificate (SHA-256). Understanding the difference helps you make the right choice for your server environment.

    • *

      What is SHA? (SHA-256 / SHA-2)

      SHA stands for Secure Hash Algorithm. In the context of SSL/TLS certificates, it refers to the algorithm a Certificate Authority (CA) uses to digitally sign your certificate, essentially creating a fingerprint that proves the certificate has not been tampered with.

      The current industry standard is SHA-256, which is part of the SHA-2 family. All SSL certificates issued today use SHA-256 signatures. The older SHA-1 algorithm was deprecated years ago due to known vulnerabilities and is no longer accepted by any major browser or CA.

      SHA-256 is not something you choose or configure manually; it is applied automatically by the CA when your certificate is issued. What you do choose is the key algorithm used in your CSR (Certificate Signing Request): either ECC or RSA.

    • *

      RSA — The Traditional Key Algorithm

      RSA (Rivest–Shamir–Adleman) is the most widely used public-key algorithm in SSL/TLS certificates and has been the industry standard for decades. It works by generating a mathematically linked key pair: a public key embedded in the certificate and a private key kept on your server.

      RSA's main strengths are its universal compatibility and long track record. Every web browser, operating system, and server platform in use today supports RSA without any additional configuration.

      The primary consideration with RSA is key size. To maintain adequate security, RSA requires increasingly large keys — the current recommended minimum is 2048 bits, with 4096 bits recommended for long-lived or high-security certificates. Larger keys mean more CPU work during the TLS handshake, which can have a measurable impact on high-traffic servers.

    • *

      ECC — Elliptic Curve Cryptography

      ECC (Elliptic Curve Cryptography) is a modern public-key algorithm based on the mathematics of elliptic curves over finite fields. Its defining advantage is that it achieves the same cryptographic strength as RSA using dramatically smaller keys.

      To put this in perspective:

      • 256-bit ECC is roughly equivalent to 3072-bit RSA in terms of cryptographic strength.
      • 384-bit ECC is roughly equivalent to 7680-bit RSA.

      Smaller keys mean faster TLS handshakes, lower CPU usage, and reduced memory overhead, which translates directly into faster page loads and more efficient server performance, especially under high load.

      ECC is also the algorithm of choice for IoT devices, mobile applications, and embedded systems where processing power and battery life are limited.

    • *

      When to Choose ECC vs RSA

      Choose ECC if:

      • Your server software is modern (Apache 2.4+, Nginx 1.11+, IIS 8+ on Windows Server 2012 R2+)
      • You are running a high-traffic website and want faster TLS handshakes
      • You are deploying certificates on IoT devices, mobile backends, or resource-constrained environments
      • You want maximum security with minimal key size

      Choose RSA if:

      • You need to support legacy browsers, operating systems, or server configurations
      • You are running older infrastructure that does not fully support ECC
      • Maximum compatibility across all clients is your top priority

      Tip: If you are unsure, RSA 2048-bit remains a safe and well-supported default. For modern infrastructure with no legacy requirements, ECC 256-bit (P-256) offers superior performance and security.

    • *

      Compatibility Considerations

      ECC certificates are supported by all modern browsers and server platforms. However, older environments may have limited or no ECC support:

      • Supported: Chrome, Firefox, Safari, Edge (all modern versions), Android 4.0+, iOS 7+, Windows Vista+, OpenSSL 1.0.1+
      • Limited or no support: Windows XP (pre-SP3), Internet Explorer on XP, very old Java versions (pre-1.7), some legacy embedded systems

      For public-facing websites serving a general audience, ECC compatibility is no longer a concern in practice. The vast majority of devices in use today fully support it. If you maintain software that explicitly needs to support Windows XP or similarly outdated platforms, RSA is the safer choice.

    • *

      Generating Your CSR

      To request an SSL certificate, whether ECC or RSA, you first need to generate a Certificate Signing Request (CSR) along with a private key. The CSR contains your domain name, organization details, and public key, and is submitted to the CA when ordering your certificate.

      You can generate both RSA and ECC CSRs with the GoGetSSL Online CSR Generator. To create the private key directly on your server instead, see How to Generate an ECC CSR and Private Key for Apache .

      Note for Microsoft IIS users: If your server runs Microsoft IIS, you must generate the CSR directly on the IIS server using IIS Manager, not via an online generator. This is because IIS binds the private key to the server at the time of CSR generation, and the certificate cannot be installed if the key was created elsewhere. See your IIS documentation or our CSR Generation Guide for step-by-step instructions.

Fast Issuance within 3-5 minutes

Get a domain-validated SSL certificate within minutes, with no paperwork and no company details needed. Prove you own the domain by email, DNS or a file on your website.

ACME SSL Automation

No more manual installs or expired certificates: automated SSL renews and installs them on any web server. You set it up once, and every renewal runs by itself.

WHMCS Reseller Plugin

Sell SSL certificates from your own hosting platform with our free WHMCS plugin. Your customers order and manage certificates in your client area. See our partner program.

Money Back 30-day guarantee

Your satisfaction comes first: get a full refund within 30 days of buying any SSL certificate, from any brand. Just contact our support team and we will take care of the rest.

Boost Validation

The Legal Entity Identifier (LEI) is a robust and modern way to verify and identify companies, helping to validate OV SSL certificates

Register LEI for $51.00

Help Center

Installation issues or SSL errors? Our Knowledgebase has clear, step-by-step guides to help you install, fix, and troubleshoot fast

Check Manuals

The trust that never expires

Since 2009, we've delivered web security and trust services worldwide. See why customers keep choosing us. From startups to enterprises, we help businesses of all sizes stay secure and build trust with their audience.

Shopper Approved reviews for GoGetSSL