ECDSA
For ECDSA, purpose is digital signature; current status is Approved; planned status is deprecated after 2030 and disallowed after 2035; replacement is ML-DSA (FIPS 204); source document is IR 8547, recorded from its source on 2026-08-16; source re-checked 2026-11-18.
- Algorithm
- ECDSA verified
- Purpose
- digital signature our reading
- Current status
- Approved our reading
- Planned status
- deprecated after 2030 and disallowed after 2035 our reading
- Replacement
- ML-DSA (FIPS 204) our reading
- Source document
- IR 8547 our reading
Values marked our reading are our classification of what the source says — the source does not print them in those words. The quote below is the evidence for each one; judge it yourself.
Cite as: ECDSA — NIST cryptographic algorithm deprecation schedule: what is approved, deprecated, and disallowed, and when (NIST cryptographic algorithm deprecation schedule: what is approved, deprecated, and disallowed, and when), referencesource.org/nist-cryptographic-algorithm-deprecation-schedule/ecdsa/, checked 2026-11-18.
What the source says
IR 8547’s proposed timeline: quantum-vulnerable public-key algorithms (RSA, ECDSA, ECDH, finite-field DH) are deprecated after 2030 and disallowed after 2035. Hybrid modes that combine an approved
— encryptionconsulting.com, retrieved 2026-08-16
Source
- encryptionconsulting.comhttps://www.encryptionconsulting.com/education-center/nist-ir-8547-sp-800-131a-algorithm-transitions/
Does your own code still call ECDSA? npx crypto-deprecation-check reads the places where naming an algorithm is the point of the line -- createHash, a JWT alg, Cipher.getInstance, MODE_ECB, generateKeyPair, createECDH, an SSH HostKeyAlgorithms setting, an openssl subcommand -- and prints the status we hold for each with this page's sentence quoted. It fails a build only on a status that is already deprecated or disallowed, says nothing at all about algorithms we hold no record for, and makes no network calls. crypto-deprecation-check on npm