privacyguides/privacytools.io
Archived
1
0
Fork 0
Code Issues 304 Pull Requests 47 Activity

Update DNS page with card-based client recommendations (#1900)

Browse Source 
* WIP: Add icons

* Add Google Play and App Store links

* Add tentative Android logo

* Update Unbound logo, text cleanup, formatting

* Add banner for anonymized dns, more cleanup

* Some text clarification

* Add "https:" for local development

* Update terms formatting and include anonymized dnscrypt

* Move terms section to bottom of page

* Add LibreDNS

* Update AdGuard hosting provider

* Add forum links

* Reword "terms" to "definitions"

* Add card for Stubby

* Add warning link to Android 9 card

* LibreDNS supports QNAME min
This commit is contained in:
nitrohorse
2020-06-04 09:00:31 -07:00
committed by GitHub
parent 93b3b611f0
commit 607b9d73d5
7 changed files with 194 additions and 121 deletions
Download Patch File Download Diff File Expand all files Collapse all files

67
_includes/sections/dns.html
View File

@ -1,10 +1,12 @@
<h1 id="dns" class="anchor"><a href="#dns"><i class="fas fa-link anchor-icon"></i></a> Encrypted Domain Name System (DNS) Resolvers</h1>
<h1 id="dns" class="anchor">
<a href="#dns"><i class="fas fa-link anchor-icon"></i></a> Encrypted DNS Resolvers
</h1>
<div class="alert alert-warning" role="alert">
<strong>Note: Using an encrypted DNS resolver will not make you anonymous, nor hide your internet traffic from your Internet Service Provider. But, it will prevent DNS hijacking, and make your DNS requests harder for third parties to eavesdrop on and tamper with. If you are currently using Google's DNS resolver, you should pick an alternative here.</strong>
DNS-over-HTTPS, DNS-over-TLS, and DNSCrypt resolvers will not make you anonymous. Using Anonymized DNSCrypt hides <i>only</i> your DNS traffic from your Internet Service Provider. However, using any of these protocols will prevent DNS hijacking, and make your DNS requests harder for third parties to eavesdrop on and tamper with. If you are currently using Google's DNS resolver, you should pick an alternative here. See the <a href="#dns-definitions">definitions</a> below.
</div>
<div class="table-responsive">
<div id="dns-table" class="table-responsive">
<table class="table sortable-theme-bootstrap" data-sortable>
<thead>
<tr>
@ -46,10 +48,7 @@
<td>Yes</td>
<td>
<span class="no-text-wrap">
Ads, trackers,
</span>
<span class="no-text-wrap">
malicious domains
Based on server choice
</span>
</td>
<td>
@ -60,6 +59,9 @@
</a>
</td>
<td>
<span class="no-text-wrap">
<a href="https://www.choopa.com/">Choopa, LLC</a>,
</span>
<span class="no-text-wrap">
<a href="https://flops.ru/en/about.html">Serveroid, LLC</a>
</span>
@ -168,7 +170,11 @@
<td>DoH, DoT</td>
<td>Yes</td>
<td>Yes</td>
<td>No</td>
<td>
<span class="no-text-wrap">
Based on server choice
</span>
</td>
<td>?</td>
<td>Self</td>
</tr>
@ -240,6 +246,51 @@
</td>
</tr>
<tr>
<td data-value="LibreDNS">
<a href="https://libredns.gr/">LibreDNS</a>
</td>
<td>
<span class="no-text-wrap">
<span class="flag-icon flag-icon-de"></span>
Germany
</span>
</td>
<td>
<a
class="btn-secondary btn-icon"
href="https://libreops.cc/terms.html">
<span class="fas fa-globe"></span>
</a>
</td>
<td>
<a data-toggle="tooltip" data-placement="bottom" data-original-title="Part of LibreHosters, &quot;a network of cooperation and solidarity that uses free software to encourage decentralisation through federation and distributed platforms.&quot;" href="https://libreho.st/">
Informal collective
</a>
</td>
<td>No</td>
<td>DoH, DoT</td>
<td>Yes</td>
<td>Yes</td>
<td>
<span class="no-text-wrap">
Based on server choice only for DoH
</span>
</td>
<td>
<a
class="btn-secondary btn-icon"
href="https://gitlab.com/libreops/libredns">
<span class="fas fa-globe"></span>
</a>
</td>
<td>
<span class="no-text-wrap">
<a href="https://www.hetzner.com/">Hetzner Online GmbH</a>
</span>
</td>
</tr>
<tr>
<td data-value="nextdns">
<a href="https://www.nextdns.io/">NextDNS</a>