Encrypted DNS helps protect your browsing activity from being tracked or tampered with by encrypting DNS queries. Learn how DNS-over-HTTPS (DoH), DNS-over-TLS (DoT) and DNSCrypt work and how to set them up on your devices.
Learn About Pricing
Every time you visit a website, your device makes a DNS request to translate a domain name (like google.com) into an IP address. Traditionally, this request is sent in plaintext, making it vulnerable to eavesdropping, tracking, and manipulation.
Encrypted DNS solves this by wrapping DNS queries inside encrypted protocols such as:
Using encrypted DNS offers several key benefits:
DoH sends DNS queries over the same protocol used for secure websites (HTTPS). This makes DNS requests blend in with regular web traffic and helps bypass some filtering or surveillance systems.
CleanBrowsing supports DoH with these endpoints:
https://doh.cleanbrowsing.org/doh/family-filter/
https://doh.cleanbrowsing.org/doh/adult-filter/
https://doh.cleanbrowsing.org/doh/security-filter/
DoT encrypts DNS using Transport Layer Security (TLS), typically on port 853. It provides strong privacy without tunneling through HTTPS.
CleanBrowsing DoT endpoints:
family-filter-dns.cleanbrowsing.org
adult-filter-dns.cleanbrowsing.org
security-filter-dns.cleanbrowsing.org
DNSCrypt is an open-source protocol that authenticates and encrypts DNS traffic between your device and a DNS resolver. Unlike DoH and DoT which use standardized web encryption (HTTPS/TLS), DNSCrypt uses its own cryptographic protocol to prevent DNS spoofing and man-in-the-middle attacks.
While not as widely supported by browsers and OS-level settings, DNSCrypt is a powerful option for advanced users and router-level setups. It offers strong privacy and security, and works great with CleanBrowsing.
CleanBrowsing DNSCrypt endpoints:
sdns://AQc... (full sdns stamps listed on the docs page)
nslookup example.com
Result should show a CleanBrowsing DNS server like:
Server: 185.228.168.168
Address: 185.228.168.168#53
DoT Test (with kdig
):
kdig @dns.cleanbrowsing.org +tls-ca +tls-host=dns.cleanbrowsing.org example.com
DoH Test (with curl
):
curl -H 'accept: application/dns-json' 'https://dns.cleanbrowsing.org/dns-query?name=example.com&type=A'
You can also inspect DNS traffic using tcpdump
or Wireshark
to confirm that unencrypted DNS (port 53) is not in use:
sudo tcpdump -n port 53
If no traffic appears on port 53, your encrypted DNS is likely working correctly.