🔑
blog.cat.ssl

ECDSA or RSA Certificates: Speed, Security and Compatibility

18.11.2026
← All articles

Most people getting an SSL certificate think only about the domain and the expiry date. Inside the certificate, though, is another choice: the algorithm behind the public key. The two mainstream options are RSA, in use for decades, and ECDSA, based on elliptic curves. Both are trusted by browsers, but they differ in speed, size and compatibility. For a small blog you will not notice, while for a busy shop or API server it matters.

The core difference

RSA's security depends on key length: 2048 bits is the current minimum, with 3072 or 4096 for extra margin, at the cost of slower operations and bigger certificates. ECDSA reaches the same strength with far shorter keys. The common P-256 curve is considered roughly equivalent to 3072-bit RSA, so it is stronger than RSA 2048 and much more compact.

PropertyRSA 2048ECDSA P-256
Approximate security level112 bits128 bits
Public key size256 bytes64 bytes
Signing on the serverSlowerMuch faster
Verification on the clientVery fastFast
Very old devicesFull supportNearly full

Effect on speed

In a TLS handshake the server signs and the client verifies. RSA signing is expensive and verification cheap; ECDSA is the opposite. Because a busy server signs for thousands of handshakes, ECDSA noticeably reduces CPU load. Measure it yourself:

openssl speed rsa2048 ecdsap256

ECDSA certificates and chains are also smaller, which helps on slow mobile connections.

Compatibility

RSA works almost everywhere. ECDSA is supported by all modern browsers, operating systems and libraries; only very old systems and some legacy embedded or industrial devices may struggle. Key type can also change the intermediate chain, for example Let's Encrypt uses different intermediates for ECDSA and RSA, so make sure servers point to the correct fullchain file.

Choosing the key type in Certbot

Recent Certbot versions default to ECDSA, but being explicit avoids surprises:

certbot certonly --nginx -d example.uz -d www.example.uz \
  --key-type ecdsa --elliptic-curve secp256r1

certbot certonly --nginx -d example.uz -d www.example.uz \
  --key-type rsa --rsa-key-size 2048 --cert-name example.uz-rsa

Check an existing certificate with openssl x509 -in cert.pem -noout -text | grep "Public Key Algorithm": id-ecPublicKey means ECDSA, rsaEncryption means RSA.

Serving both

Nginx accepts several certificate pairs in one server block and picks the one each client supports:

server {
    listen 443 ssl;
    server_name example.uz www.example.uz;

    ssl_certificate     /etc/letsencrypt/live/example.uz/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/example.uz/privkey.pem;

    ssl_certificate     /etc/letsencrypt/live/example.uz-rsa/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/example.uz-rsa/privkey.pem;
}

Certbot renews both certificates automatically; add a deploy hook that reloads Nginx after each renewal so the new files are actually served.

Example and recommendation

A Tashkent grocery delivery service runs one API server for its misol.uz site and mobile app. At evening peaks much of the CPU goes to new TLS handshakes. Switching from RSA 4096 to ECDSA P-256 cuts that cost noticeably, while an RSA certificate stays as a fallback for old cash register software. For most sites ECDSA P-256 is the sensible default; add RSA only if you have legacy clients, and never use RSA keys shorter than 2048 bits. On sayt.uz shared hosting, free Let's Encrypt certificates are issued and renewed automatically; to control the key type yourself, a VPS is the easier route.

Related articles

🚫 Disabling TLS 1.0 and 1.1: Why It Matters and How to Do It 🛡️ Cloudflare Origin Certificates: When to Use Them and When Not To 🔐 ERR_CERT_COMMON_NAME_INVALID: when the SSL certificate name does not match 🔐 acme.sh: Issuing and Renewing SSL Certificates on a VPS
🌐 Language
🇺🇿 O'zbek 🇺🇿 Ўзбек 🇷🇺 Русский 🇬🇧 English ✓