From 24cd3c3f1010608a3fb95882adf86d08014719c1 Mon Sep 17 00:00:00 2001 From: HardenedSteel Date: Tue, 28 May 2024 06:01:55 +0000 Subject: [PATCH] State Secure DNS Prevents Poisoning change "does not" to "can not" because it was sounding like ISP doesn't poison on purpose, which is wrong. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 7bea340..19e344e 100644 --- a/README.md +++ b/README.md @@ -80,7 +80,7 @@ Modern modesets (more stable, more compatible, faster): -6 -f 2 -e 2 --wrong-seq --reverse-frag --max-payload ``` -To check if your ISP's DPI could be circumvented, first make sure that your provider does not poison DNS answers by enabling "Secure DNS (DNS over HTTPS)" option in your browser. +To check if your ISP's DPI could be circumvented, first make sure that your provider can not poison DNS answers by enabling "Secure DNS (DNS over HTTPS)" option in your browser. * **Chrome**: Settings → [Privacy and security](chrome://settings/security) → Use secure DNS → With: NextDNS * **Firefox**: [Settings](about:preferences) → Network Settings → Enable DNS over HTTPS → Use provider: NextDNS