mirror of
https://github.com/yokoffing/NextDNS-Config.git
synced 2025-11-08 11:23:50 -05:00
Compare commits
8 Commits
ea8188a1f4
...
main
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
3027bc2f3a | ||
|
|
1a1247b10b | ||
|
|
746a0a0fcc | ||
|
|
f8415b1406 | ||
|
|
68355457a2 | ||
|
|
0fff653ffa | ||
|
|
84330e1416 | ||
|
|
1427a81f2f |
50
README.md
50
README.md
@@ -1,12 +1,3 @@
|
||||
[](https://github.com/yokoffing/NextDNS-Config/issues)
|
||||

|
||||

|
||||

|
||||

|
||||

|
||||
[](https://hits.seeyoufarm.com)
|
||||
|
||||
***
|
||||
# Guidelines :bookmark:
|
||||
1) Prevent overblocking by utilizing the [law of diminishing returns]() (e.g., using [sane](https://www.privacyguides.org/en/basics/threat-modeling/), quality [blocklists](https://github.com/yokoffing/NextDNS-Config#blocklists-1); allowing most [TLDs](https://github.com/yokoffing/NextDNS-Config#block-top-level-domains-tlds-1-2-3-4-5-); etc.).
|
||||
2) Pass the [girlfriend test](https://www.urbandictionary.com/define.php?term=Grandma%20Test) with few exceptions. These deviations are documented throughout the guide.
|
||||
@@ -24,18 +15,22 @@ Sign up for NextDNS [here](https://nextdns.io/?from=xujj63g5) and support this p
|
||||
Security settings protect your data from harm, theft, and unauthorized use.<sup>*^[why does this matter?](https://thenewoil.org/en/guides/prologue/why)*</sup>
|
||||
|
||||
## Threat Intelligence Feeds <sup><sup>[1](https://github.com/nextdns/metadata/blob/6f9b6cd0670e7e31ad2ca716742088c2fc0616c2/security/threat-intelligence-feeds.json)</sup></sup>
|
||||
 Use Threat Intelligence Feeds
|
||||
## AI-Driven Threat Detection <sup><sup>[1](https://x.com/NextDNS/status/1440291577713233925)</sup></sup>
|
||||
> [!NOTE]
|
||||
> NextDNS labels this feature as [beta](https://www.vocabulary.com/dictionary/beta), although most users report it works well.
|
||||
> [!CAUTION]
|
||||
> Leave this feature enabled if you use something other than the [recommended blocklists](https://github.com/yokoffing/NextDNS-Config#privacy-lock) (see https://github.com/yokoffing/NextDNS-Config/issues/74).
|
||||
|
||||
 Enable AI-Driven Threat Detection
|
||||
 Use Threat Intelligence Feeds
|
||||
|
||||
## AI-Driven Threat Detection <sup><sup>[1](https://x.com/NextDNS/status/1440291577713233925)</sup></sup>
|
||||
|
||||
NextDNS labels this feature as [beta](https://www.vocabulary.com/dictionary/beta), although most users report it works well.
|
||||
|
||||
 Enable AI-Driven Threat Detection
|
||||
|
||||
## Google Safe Browsing <sup><sup> [1](https://safebrowsing.google.com/safebrowsing/report_general/) [2](https://blog.cryptographyengineering.com/2019/10/13/dear-apple-safe-browsing-might-not-be-that-safe/) [3](https://the8-bit.com/apple-proxies-google-safe-browsing-privacy/) [4](https://github.com/brave/brave-browser/wiki/Deviations-from-Chromium-(features-we-disable-or-remove)#services-we-proxy-through-brave-servers) </sup></sup>
|
||||
> [!TIP]
|
||||
> Unlike the version embedded in some browsers, this feature does not associate your public IP address to threats and does not allow bypassing the block.
|
||||
> [!CAUTION]
|
||||
> Google Safe Browsing wasn't designed as a DNS-level blocker and may flag legitimate [CNAME domains](https://en.wikipedia.org/wiki/CNAME_record) as scams. NextDNS can also take months to remove a [false positive](https://csrc.nist.gov/glossary/term/false_positive).
|
||||
|
||||
 Enable Google Safe Browsing
|
||||
 Enable Google Safe Browsing
|
||||
|
||||
## Cryptojacking Protection <sup><sup>[1](https://github.com/nextdns/metadata/blob/6f9b6cd0670e7e31ad2ca716742088c2fc0616c2/security/cryptojacking.json)</sup></sup>
|
||||
> [!CAUTION]
|
||||
@@ -136,10 +131,10 @@ Here are the suggested blocklists, based on past issues and observations:
|
||||
> [!TIP]
|
||||
> Use different blocklists on separate DNS profiles (e.g., NORMAL for your router and PRO++ for your web browser).
|
||||
|
||||
You can also check out Hagezi's own [recommendations](https://github.com/hagezi/dns-blocklists/tree/main#whatshouldiuse).
|
||||
You can also check out Hagezi's own [recommendations](https://github.com/hagezi/dns-blocklists/wiki/FAQ#whatshouldiuse).
|
||||
|
||||
### Why Hagezi?
|
||||
[Hagezi](https://github.com/hagezi/dns-blocklists) block ads, trackers, native device trackers, and badware. He maintains a sensible allowlist, handles false positives quickly, and communicates known issues to blocklists maintainers. Hagezi's primary DNS lists combine multiple [sources](https://github.com/hagezi/dns-blocklists/wiki/FAQ#-which-sources-are-used-for-the-lists-and-how-are-the-lists-compiled-on-the-basis-of-these-sources) including respected community blocklists like [OISD](https://oisd.nl/), [Steven Black](https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts), [1Hosts](https://github.com/badmojr/1Hosts#safeguard-your-devices-against-pesky-ads-trackers-and-malware), [notrack](https://gitlab.com/quidsup/notrack#notrack), and [more](https://github.com/hagezi/dns-blocklists/blob/main/sources.md).
|
||||
[Hagezi](https://github.com/hagezi/dns-blocklists) block ads, trackers, native device trackers, and badware. He maintains a sensible allowlist, handles false positives quickly, and communicates known issues to blocklists maintainers. Hagezi builds his blocklists using many of the same original [sources](https://github.com/hagezi/dns-blocklists/blob/main/sources.md) that feed into other popular lists like OISD and 1Hosts. He also adds his own unique sources, rather than just repackaging other combined blocklists.
|
||||
|
||||
You may also wonder why other lists are not utilized. This is because many list maintainers:
|
||||
* do not remove [false positives](https://csrc.nist.gov/glossary/term/false_positive) and/or are no longer active <sup>[1](https://github.com/lightswitch05/hosts/issues/356) [2](https://github.com/EnergizedProtection/block/issues/916)</sup>
|
||||
@@ -147,8 +142,10 @@ You may also wonder why other lists are not utilized. This is because many list
|
||||
* offer no meaningful additional coverage when compared with the chart combinations above
|
||||
|
||||
## Native Tracking Protection <sup><sup>[1](https://github.com/nextdns/native-tracking-domains/tree/main/domains)</sup></sup>
|
||||
> [!CAUTION]
|
||||
> Leave this feature enabled if you use something other than the [recommended blocklists](https://github.com/yokoffing/NextDNS-Config#privacy-lock) (see https://github.com/yokoffing/NextDNS-Config/issues/76).
|
||||
|
||||
Add all the device brands you use.
|
||||
If you decide to use this feature, then add all the device brands that you use.
|
||||
|
||||
<details>
|
||||
|
||||
@@ -164,7 +161,9 @@ Add all the device brands you use.
|
||||
</details>
|
||||
|
||||
## Block Disguised Third-Party Trackers <sup><sup>[1](https://github.com/nextdns/cname-cloaking-blocklist/blob/master/domains) [2](https://www.reddit.com/r/nextdns/comments/10nenu3/disguised_trackers_are_blocked_regardless_of) [3](https://medium.com/nextdns/cname-cloaking-the-dangerous-disguise-of-third-party-trackers-195205dc522a) [4](https://arxiv.org/pdf/2102.09301.pdf) [5](https://tma.ifip.org/2020/wp-content/uploads/sites/9/2020/06/tma2020-camera-paper66.pdf) </sup></sup>
|
||||
 Block Disguised Third-Party Trackers
|
||||
 Block Disguised Third-Party Trackers
|
||||
|
||||
The domain [list](https://github.com/nextdns/cname-cloaking-blocklist/blob/master/domains) hasn't been updated in years, and it blocks some referral domains that **Allow Affiliate & Tracking Links** doesn't unblock. NextDNS blocks [CNAME records](https://en.wikipedia.org/wiki/CNAME_record) by default, even with this list disabled.
|
||||
|
||||
## Allow Affiliate & Tracking Links <sup><sup>[1](https://github.com/nextdns/click-tracking-domains) [2](https://x.com/NextDNS/status/1539229377560461312) </sup></sup>
|
||||
> [!TIP]
|
||||
@@ -203,6 +202,9 @@ Some DoH providers block this feature automatically.
|
||||
mask-h2.icloud.com
|
||||
mask-canary.icloud.com
|
||||
|
||||
> [!CAUTION]
|
||||
> The domains below may prevent external images from loading in Apple mail clients. You don't need these unless you're running a very aggressive profile.
|
||||
|
||||
And possibly:
|
||||
|
||||
apple-relay.cloudflare.com
|
||||
@@ -383,6 +385,9 @@ Users have [reported](https://www.reddit.com/r/nextdns/comments/v84ag6/paramount
|
||||
|
||||
 Enable CNAME Flattening
|
||||
|
||||
## Bypass Age Verification
|
||||
 Bypass Age Verification
|
||||
|
||||
## Web3 <sup><sup> [1](https://x.com/NextDNS/status/1491034351391305731) [2](https://gabygoldberg.notion.site/f7050e62461143d49345e7b46eb5576b)</sup></sup>
|
||||
 Enable Web3 → (optional)
|
||||
|
||||
@@ -469,6 +474,3 @@ Ultimately, you don't need a VPN unless your [threat model](https://thenewoil.or
|
||||
* [Easylist](https://github.com/easylist/easylist/issues?q=author%3Ayokoffing)
|
||||
* [uBlock Origin](https://github.com/uBlockOrigin/uAssets/issues?q=author%3Ayokoffing)
|
||||
* [AdGuard](https://github.com/AdguardTeam/AdguardFilters/issues?q=author%3Ayokoffing)
|
||||
|
||||
<div align='center'><a href='https://websitecounterfree.com'><img src='https://websitecounterfree.com/c.php?d=9&id=19651&s=1' border='0' alt='Free Website Counter'></a><br / ></div>
|
||||
<div align='center'>since 23 July 2022</div>
|
||||
|
||||
Reference in New Issue
Block a user