diff --git a/README.md b/README.md
index 42523ad5..a8e03613 100644
--- a/README.md
+++ b/README.md
@@ -10,13 +10,11 @@ It is an independent open source implementation that is not affiliated with or e
 
 ## ACME v1
 
-This _acme4j_ branch implements the deprecated _ACME v1_ protocol. It should only be used for existing code, and for connecting to CAs that do not provide an _ACME v2_ service.
+This _acme4j_ branch implements the deprecated _ACME v1_ protocol. _Let's Encrypt_ has announced an [End of Life Plan for ACME v1](https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430). According to this plan, access to the ACME v1 servers will be limited starting November 2019, and completely stopped in June 2021.
 
-For new projects, it is recommended to use _acme4j_ version 2, which fully implements the current ACME v2 protocol.
+**Please [migrate](https://shredzone.org/maven/acme4j/migration.html) your code to _acme4j_ v2.5 or higher soon!**
 
-Existing code should be migrated to _acme4j_ version 2 (see the [migration guide](https://shredzone.org/maven/acme4j/migration.html)). _Let's Encrypt_ has not yet announced a sunset date for ACME v1, so there seems to be plenty of time for migration at the moment.
-
-This _acme4j_ v1 branch is not actively maintained any more. It will only get bugfixes and security updates, but no new features. As soon as _Let's Encrypt_ officially ends its ACME v1 support, work on this branch will be stopped.
+This _acme4j_ v1 branch will **only receive security fixes until November 1st, 2019**. After that date, ACME v1 support will end and this branch will be closed.
 
 ## Features
 
diff --git a/src/site/markdown/index.md.vm b/src/site/markdown/index.md.vm
index 9b2dfbd9..c8126965 100644
--- a/src/site/markdown/index.md.vm
+++ b/src/site/markdown/index.md.vm
@@ -14,11 +14,11 @@ The source code can be found at [GitHub](https://github.com/shred/acme4j) and is
 ACME v1
 -------
 
-This version of _acme4j_ implements the deprecated _ACME v1_ protocol. It should only be used for existing code, and for connecting to CAs that do not provide an _ACME v2_ service.
+This _acme4j_ branch implements the deprecated _ACME v1_ protocol. _Let's Encrypt_ has announced an [End of Life Plan for ACME v1](https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430). According to this plan, access to the ACME v1 servers will be limited starting November 2019, and completely stopped in June 2021.
 
-For new projects, it is recommended to use _acme4j_ version 2, which fully implements the current ACME v2 protocol.
+**Please [migrate](https://shredzone.org/maven/acme4j/migration.html) your code to _acme4j_ v2.5 or higher soon!**
 
-Existing code should be migrated to _acme4j_ version 2 (see the [migration guide](https://shredzone.org/maven/acme4j/migration.html)). _Let's Encrypt_ has not yet announced a sunset date for ACME v1, so there seems to be plenty of time for migration at the moment.
+This _acme4j_ v1 branch will **only receive security fixes until November 1st, 2019**. After that date, ACME v1 support will end and this branch will be closed.
 
 Quick Start
 -----------