diff --git a/source/manuals/security-overview-for-websites.html.md.erb b/source/manuals/security-overview-for-websites.html.md.erb
index 6b9a50d3..c81c11b8 100644
--- a/source/manuals/security-overview-for-websites.html.md.erb
+++ b/source/manuals/security-overview-for-websites.html.md.erb
@@ -1,6 +1,6 @@
 ---
 title: Security overview for websites
-last_reviewed_on: 2023-11-21
+last_reviewed_on: 2024-06-27
 review_in: 6 months
 ---
 
@@ -49,7 +49,7 @@ Contact your registrar and ask if they offer any additional safeguards to preven
 
 Ask your registrar for contact details that you can use in the event of an incident and note these in your incident response plan.
 
-Enable DNSSEC if available ([Cloudflare has a great explanation on DNSSEC](https://www.cloudflare.com/en-gb/dns/dnssec/how-dnssec-works/)).
+Enable DNSSEC if practicable ([Cloudflare has a great explanation on DNSSEC](https://www.cloudflare.com/en-gb/dns/dnssec/how-dnssec-works/)).
 
 Ensure your WHOIS details are correct and contain the organisation or department name, the main building address, and a generic shared email address (_service_-webadmin@organisation[.]gov.uk) and do not enable privacy guard.