← Back to Learning Hub

DNS • Intermediate • 6 min read

RSA vs ECDSA Certificates: Key Types and Dual-Cert Setups

RSA and ECDSA certificates compared on speed, size, and compatibility, plus how a dual-certificate setup serves ECDSA to modern clients and RSA to old ones.

When you request a TLS certificate you also choose the type of key behind it, and the two mainstream options are RSA and ECDSA. They do the same job, proving your server's identity and setting up an encrypted session, but they differ in speed, key size, and how widely old clients accept them. This guide compares RSA and ECDSA on the things that actually affect a production site, explains why a smaller ECDSA key can be as strong as a much larger RSA key, and shows how a dual-certificate setup serves ECDSA to modern clients while keeping RSA ready for the few that still need it.

Two ways to prove a server's identity

Every TLS certificate contains a public key, and during the handshake the server proves it holds the matching private key. RSA keys are based on the difficulty of factoring large numbers, and they have been the default for decades. ECDSA keys use elliptic-curve cryptography, which reaches the same security level with far smaller keys. Both are fully standardized and both are accepted by every current browser and operating system as of November 2026. The choice is not about whether one is secure and the other is not; both are secure at recommended sizes. It is about performance, key size, and how far back into legacy clients you need to reach.

Key size and equivalent strength

The headline difference is how much key you need for a given strength. A 256-bit ECDSA key on the P-256 curve is generally considered comparable in security to a 3072-bit RSA key, and a 384-bit ECDSA key compares to roughly a 7680-bit RSA key. In practice most sites run either a 2048-bit RSA key, which remains acceptable as of November 2026, or a P-256 ECDSA key. The smaller ECDSA key means smaller certificates and signatures on the wire, less data in each handshake, and lighter computation on the server for the signing operation. For a busy server terminating many new connections, that efficiency adds up.

Speed, compatibility, and the real trade-off

RSA and ECDSA split the handshake cost differently. RSA signing, which the server does on every handshake, is comparatively expensive, while RSA verification, which the client does, is cheap. ECDSA flips the heavier side toward the client and makes the server's signing operation fast, which is usually the side you care about because the server handles far more handshakes than any single client. The result is that ECDSA typically lets a server set up new connections with less CPU. The one thing RSA still buys you is reach: a small number of very old clients, legacy embedded devices, and ancient libraries understand RSA but not modern elliptic curves. For the public web that population is tiny as of November 2026, but if your audience includes old point-of-sale terminals or industrial equipment, it can matter.

RSA versus ECDSA at a glance

The table below summarizes the comparison.

PropertyRSAECDSA
Common key size2048-bit256-bit (P-256)
Rough equivalent2048-bit RSA256-bit ECDSA matches about 3072-bit RSA
Server signing costHigherLower
Handshake and cert sizeLargerSmaller
Very old client supportBroadestNot understood by some legacy clients
Best default forMaximum legacy reachModern performance

When a dual-certificate setup makes sense

You do not have to choose one and abandon the other. Modern web servers can hold both an ECDSA and an RSA certificate for the same hostname and pick which to serve based on what the client advertises in its handshake. A client that signals support for elliptic-curve signatures gets the ECDSA certificate and its performance benefit; a client too old to understand those curves falls back to the RSA certificate and still connects. This dual-certificate, or hybrid, setup gives you modern efficiency for the overwhelming majority while preserving a path for stragglers. The cost is operational: two certificates to issue, renew, and monitor instead of one. For most sites a single ECDSA certificate is simpler and sufficient; dual-cert is worth it mainly when you have measured a real population of legacy clients you cannot drop.

Setting up and verifying your key type

  1. Decide your default: ECDSA P-256 for performance, or RSA 2048 if you must reach very old clients and will not run two certificates.
  2. Generate the key of the chosen type, or let your ACME client request it; most clients let you set the key type and curve.
  3. If you need both, issue a separate RSA and ECDSA certificate for the same names and configure the server to hold both.
  4. Order the server's cipher and certificate preferences so capable clients negotiate ECDSA first.
  5. Test with a client that supports modern curves and, separately, confirm the RSA fallback still serves if you run dual certificates.
  6. Recheck after every renewal, since a renewal script set to the wrong key type can silently swap what you serve.

Confirm which certificate and key your server actually presents with the Valla DNS SSL checker, which reports the signature algorithm and key details from the live handshake. Reading those fields correctly is covered in our guide on how to check an SSL certificate issuer, chain, expiry, and SAN.

Which to pick in 2026

For a new public-facing site with a normal web audience, ECDSA P-256 is the sensible default as of November 2026: faster handshakes, smaller certificates, and universal support among current browsers. Keep RSA 2048 as the choice when you know you must serve legacy clients and prefer one certificate over two, or add RSA alongside ECDSA in a dual setup when you have both modern traffic and a measured legacy tail. Avoid chasing larger RSA keys for their own sake; a 4096-bit RSA key costs noticeably more CPU per handshake for a security margin most sites do not need, when a small ECDSA key delivers comparable strength far more cheaply.

Frequently asked questions

Is ECDSA more secure than RSA?

Not inherently; both are secure at recommended sizes. ECDSA reaches the same security level with a much smaller key, so a 256-bit ECDSA key is roughly comparable to a 3072-bit RSA key. The practical advantage is efficiency, not a difference in how safe they are.

Will an ECDSA certificate break for some visitors?

Only for a small set of very old clients and legacy devices that do not understand modern elliptic curves. Every current browser and operating system supports ECDSA. If you have a measurable legacy audience, run a dual-certificate setup so those clients fall back to RSA.

What is a dual-certificate setup?

It is serving both an ECDSA and an RSA certificate for the same hostname and letting the server choose per client. Modern clients get ECDSA and its speed benefit; clients too old for elliptic curves get RSA and still connect. The trade-off is two certificates to manage.

Should I use RSA 4096 for extra safety?

Usually not. RSA 2048 remains acceptable as of November 2026, and 4096 roughly doubles the per-handshake signing cost for a margin most sites do not need. If you want more headroom efficiently, an ECDSA key gives comparable strength with far less overhead.

Does the key type change how I get or renew a certificate?

No. The ACME flow and validation are the same; you simply tell your client which key type and curve to request. The only extra work is in a dual-certificate setup, where you issue and renew two certificates for the same names instead of one.

RSA and ECDSA both secure your site, so the decision comes down to performance versus legacy reach. Default to ECDSA, keep RSA in reserve for old clients, and confirm what your server presents on the SSL checker after every change.

Troubleshooting box

If results look inconsistent, compare authoritative nameservers first, then recursive resolvers by region. Capture snapshots every 10 minutes for deterministic incident timelines.

Try VallaDNS free →

Intermediate • 6 min

How to Find a DNS Record's TTL (Current Value)

Find the TTL currently set on a DNS record: read the TTL column in dig and nslookup, tell the authoritative TTL from a resolver's countdown, and confirm a change.

Intermediate • 7 min

How to Check If Nameservers Have Propagated

Nameserver changes live at the parent TLD and follow the registry NS TTL, not your zone. Check the parent delegation and confirm the new NS set worldwide.