diff --git a/.github/workflows/test.yaml b/.github/workflows/test.yaml
index de10dbd4a6..2ffc6b9545 100644
--- a/.github/workflows/test.yaml
+++ b/.github/workflows/test.yaml
@@ -40,7 +40,7 @@ jobs:
       - run: npm run build
       - run: npm test
       - name: Install xmllint
-        run: sudo apt-get install -y libxml2-utils
+        run: sudo apt-get update && sudo apt-get install -y libxml2-utils
       - name: Validate RSS feed
         run: xmllint --noout public/feed.xml
       # - run: npm run test:html5validate
diff --git a/content/en/caaproblem.md b/content/en/caaproblem.md
index 6fe41aefd0..a25d97e27b 100644
--- a/content/en/caaproblem.md
+++ b/content/en/caaproblem.md
@@ -1,50 +1,14 @@
 ---
-title: Download affected certificate serials for 2020.02.29 CAA Rechecking Incident
+title: Affected certificate serials for 2020.02.29 CAA Rechecking Incident
 slug: caaproblem
 date: 2020-03-02
-lastmod: 2020-03-03
+lastmod: 2026-09-24
 english_is_canonical: 1
 show_lastmod: 1
 ---
 
-
-This page hosts the list of affected serial numbers and a hostname checking utility for the incident reported at
+This page formerly hosted the list of affected serial numbers and a hostname
+checking utility for the incident reported at
 https://community.letsencrypt.org/t/2020-02-29-caa-rechecking-bug/114591.
 
-We have sent notification emails to affected subscribers who have registered an email address. If you need to re-subscribe to
-email notifications, please see <a href="https://letsencrypt.org/docs/expiration-emails/">this document</a>. You may not have
-received an email if you did not provide an email address while registering your ACME account. You may also be missing an email
-due to email delivery issues or spam filtering. If you are unsure whether your hostname is affected, use the checking tools below.
-The email will have the following subject line:
-```
-ACTION REQUIRED: Renew these Let's Encrypt certificates by March 4
-```
-
-The file <a href="https://d4twhgtvn0ff5.cloudfront.net/caa-rechecking-incident-affected-serials.txt.gz">caa-rechecking-incident-affected-serials.txt.gz</a> contains a list of all
-affected certs, sorted by account ID. Each entry has the following syntax:
-
-```
-serial 0362...8fdb 131 b8dc...ed3f names: [....] missing CAA checking results for <name> at 2019-12-03 21:08:34.826011675 +0000 UTC
-```
-
-The first chunk is the serial (03..), next is the account id (131), next is a
-hash of the names on the cert (you can disregard), then the list of names on
-the cert. The date is when the affected cert was issued.
-
-You can download this file and look up your account id(s) (if you received an
-email, your account ids were in that email). For each certificate listed,
-you will need to renew and replace it, unless you have renewed it
-more recently than the date listed. For instance, if you know your ACME client
-always renews certificates when they are 30 days from expiration, you can safely
-ignore any entries with a date earlier than 2020-01-02.
-
-If you want to double check whether a given hostname still
-needs its certificate replaced, you can use the tool at
-https://checkhost.unboundtest.com/
-
-```
-$ curl -XPOST -d 'fqdn=letsencrypt.org' https://checkhost.unboundtest.com/checkhost
-The certificate currently available on letsencrypt.org is OK. It is not one of the certificates affected by the Let's Encrypt CAA rechecking problem. Its serial number is 03a1c95bdaa36a8268327f2253cbd3ba243
-```
-
-If you have a large list of domains you need to check, <a href="https://github.com/hannob/lecaa">this tool</a> will be more effective.
+The data is no longer available from this page.