Add DNS.WATCH to the dns section #513
Labels
No Label
🔍🤖 Search Engines
approved
dependencies
duplicate
feedback wanted
high priority
I2P
iOS
low priority
OS
Self-contained networks
Social media
stale
streaming
todo
Tor
WIP
wontfix
XMPP
[m]
₿ cryptocurrency
ℹ️ help wanted
↔️ file sharing
⚙️ web extensions
✨ enhancement
❌ software removal
💬 discussion
🤖 Android
🐛 bug
💢 conflicting
📝 correction
🆘 critical
📧 email
🔒 file encryption
📁 file storage
🦊 Firefox
💻 hardware
🌐 hosting
🏠 housekeeping
🔐 password managers
🧰 productivity tools
🔎 research required
🌐 Social News Aggregators
🆕 software suggestion
👥 team chat
🔒 VPN
🌐 website issue
🚫 Windows
👁️ browsers
🖊️ digital notebooks
🗄️ DNS
🗨️ instant messaging (im)
🇦🇶 translations
No Milestone
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: privacyguides/privacytools.io#513
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I want you to take a look at DNS.WATCH DNS service. It's a privacy respecting public dns resolver (no logs), is fast and has DNSSEC. Both IPv4 and IPv6 are supported.
There are other privacy DNS services out there, but this is the only one I've found that has reasonable security. All the other ones are terrible. You can use the GRC.com DNS spoof test to test your DNS security.
https://dns.watch/
Do we wish to support not-OpenNIC servers? At the moment there is no individual server provider mentioned on the site.
I wonder if it would be better to direct people thinking about DNS servers to e.g. DNSPrivacy.org's list, but they again seem to list also services like Google DNS.
@Jon-guy30 Do you have any connection to the dns.watch admin? I wished to include it in https://github.com/privacytoolsIO/privacytools.io/pull/1054, but it turns out to not support DNS over TLS nor DNS over HTTPS nor mention DNSCrypt.
Closing because of user unresponsiveness.