diff --git a/README.md b/README.md
index 7b55393b..e4e58ccd 100644
--- a/README.md
+++ b/README.md
@@ -17,7 +17,7 @@ This Java client helps to connect to an ACME server, and performing all necessar
 * Supports [RFC 9444](https://tools.ietf.org/html/rfc9444) for subdomain validation
 * Supports [RFC 9773](https://tools.ietf.org/html/rfc9773) for renewal information
 * Supports [draft-aaron-acme-profiles-00](https://www.ietf.org/archive/id/draft-aaron-acme-profiles-00.html) for certificate profiles (experimental)
-* Supports [draft-ietf-acme-dns-account-label-00](https://datatracker.ietf.org/doc/draft-ietf-acme-dns-account-label/) for DNS labeled with ACME account ID challenges (experimental)
+* Supports [draft-ietf-acme-dns-account-label-01](https://datatracker.ietf.org/doc/draft-ietf-acme-dns-account-label/) for DNS labeled with ACME account ID challenges (experimental)
 * Easy to use Java API
 * Requires JRE 17 or higher
 * Supports [Actalis](https://www.actalis.com/), [Buypass](https://buypass.com/), [Google Trust Services](https://pki.goog/), [Let's Encrypt](https://letsencrypt.org/), [SSL.com](https://www.ssl.com/), [ZeroSSL](https://zerossl.com/), and **all other CAs that comply with the ACME protocol (RFC 8555)**. Note that _acme4j_ is an independent project that is not supported or endorsed by any of the CAs.
diff --git a/src/doc/docs/challenge/dns-account-01.md b/src/doc/docs/challenge/dns-account-01.md
index 869f721a..6395a547 100644
--- a/src/doc/docs/challenge/dns-account-01.md
+++ b/src/doc/docs/challenge/dns-account-01.md
@@ -2,7 +2,7 @@
 
 With the `dns-account-01` challenge, you prove to the CA that you are able to control the DNS records of the domain to be authorized, by creating a TXT record with a signed content.
 
-This challenge is specified in [draft-ietf-acme-dns-account-label-00](https://datatracker.ietf.org/doc/draft-ietf-acme-dns-account-label/).
+This challenge is specified in [draft-ietf-acme-dns-account-label-01](https://datatracker.ietf.org/doc/draft-ietf-acme-dns-account-label/).
 
 !!! warning
     The support of this challenge is **experimental**. The implementation is only unit tested for compliance with the specification, but is not integration tested yet. There may be breaking changes in this part of the API in future releases.
diff --git a/src/doc/docs/challenge/index.md b/src/doc/docs/challenge/index.md
index b4f01c84..524b3e12 100644
--- a/src/doc/docs/challenge/index.md
+++ b/src/doc/docs/challenge/index.md
@@ -11,6 +11,6 @@ The ACME specifications define these standard challenges:
 
 _acme4j_ also supports these non-standard challenges:
 
-* [dns-account-01](dns-account-01.md) ([draft-ietf-acme-dns-account-label-00](https://datatracker.ietf.org/doc/draft-ietf-acme-dns-account-label/00/))
+* [dns-account-01](dns-account-01.md) ([draft-ietf-acme-dns-account-label-01](https://datatracker.ietf.org/doc/draft-ietf-acme-dns-account-label/))
 * [email-reply-00](email-reply-00.md)
 * [tls-alpn-01](tls-alpn-01.md)
diff --git a/src/doc/docs/index.md b/src/doc/docs/index.md
index 1859db83..bef39062 100644
--- a/src/doc/docs/index.md
+++ b/src/doc/docs/index.md
@@ -21,7 +21,7 @@ Latest version: ![maven central](https://shredzone.org/maven-central/org.shredzo
 * Supports [RFC 9444](https://tools.ietf.org/html/rfc9444) for subdomain validation
 * Supports [RFC 9773](https://tools.ietf.org/html/rfc9773) for renewal information
 * Supports [draft-aaron-acme-profiles-00](https://www.ietf.org/archive/id/draft-aaron-acme-profiles-00.html) for certificate profiles (experimental)
-* Supports [draft-ietf-acme-dns-account-label-00](https://datatracker.ietf.org/doc/draft-ietf-acme-dns-account-label/) for DNS labeled with ACME account ID challenges (experimental)
+* Supports [draft-ietf-acme-dns-account-label-01](https://datatracker.ietf.org/doc/draft-ietf-acme-dns-account-label/) for DNS labeled with ACME account ID challenges (experimental)
 * Easy to use Java API
 * Requires JRE 17 or higher
 * Supports [Actalis](https://www.actalis.com/), [Buypass](https://buypass.com/), [Google Trust Services](https://pki.goog/), [Let's Encrypt](https://letsencrypt.org/), [SSL.com](https://www.ssl.com/), [ZeroSSL](https://zerossl.com/), and **all other CAs that comply with the ACME protocol (RFC 8555)**. Note that _acme4j_ is an independent project that is not supported or endorsed by any of the CAs.