diff --git a/_docs/30_features/20_bypass.md b/_docs/30_features/20_bypass.md
index f93e4da..5e804f2 100644
--- a/_docs/30_features/20_bypass.md
+++ b/_docs/30_features/20_bypass.md
@@ -2,7 +2,7 @@
title: Bypass ad-blockers
category: features
permalink: /bypass-ad-blockers
-last_modified_at: 2022-04-14
+last_modified_at: 2026-09-10
---
Simple Analytics never collects any personal identifiable information. Ad-blockers see us just any other analytics company and some of the ad-blockers are blocking our domain as a result. To prevent your stats being blocked as a result we allow you to setup a bypass. This basically hides Simple Analytics' server name from the browser by redirecting a subdomain to our domain.
@@ -17,25 +17,27 @@ We cannot stress this enough, if you want the best ad-blocker bypass, set up [ou
You only need access to your DNS to set this up. Add a CNAME record to your DNS pointing to `simpleanalyticsexternal.com` and fill in your full domain in [your website settings](https://simpleanalytics.com/select-website/settings#bypass-ad-blockers). We advise to choose a domain like `api.example.com` instead of `track.example.com` _(tracking, analytics, collect, and similar keywords are usually blocked)_.
-You will need to enable the record in [your website settings](https://simpleanalytics.com/select-website/settings#bypass-ad-blockers) on Simple Analytics. We need to know this to request a certificate with Let's Encrypt. This means your analytics will travel safe via HTTPS to our servers.
+Add the CNAME record before you save the domain in [your website settings](https://simpleanalytics.com/select-website/settings#bypass-ad-blockers). We check that the record points to `simpleanalyticsexternal.com` and show a warning if it does not. If you see the warning, check the CNAME target, wait for the DNS change to propagate, and save the domain again to retry the check. DNS changes can take a few minutes to propagate.
-
+Existing CNAME records pointing to `external.simpleanalytics.com` or `external.simpleanalytics.io` are also supported.
-> If you are using
CloudFlare, make sure to disable the orange cloud.
+
+
+> If you are using
Cloudflare, set the record to **DNS only** (the gray cloud). Proxied records hide the CNAME target, so our check cannot verify it.
## Check if SSL works
+After you save the domain and the DNS check passes, we automatically make an HTTPS request to your custom domain to start certificate issuance with Let's Encrypt. Certificates are issued on the first HTTPS connection that needs one, so this first request can take a few seconds. This keeps your analytics traffic encrypted via HTTPS.
+
Check if your custom domain page shows at `https://custom.domain.com`. It should show something like this:
-If you get an SSL error, please hit refresh in your [website settings](https://simpleanalytics.com/select-website/settings#bypass-ad-blockers):
-
-
+If you get an SSL error, try opening the domain again after a few seconds. You can inspect the certificate with our [SSL checker](https://simpleanalytics.com/check-ssl), also linked as **Check SSL certificate** in your website settings. If the error persists, verify your DNS record and save the domain again in your website settings to retry.
## Update your script
-Include these two lines at the end of your `