Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

This site is mainly focussed on following the development and deployment of DNS-over-TLS (DOTDoT) and DNS-over-HTTPS (DOHDoH) as the leading solutions for DNS Privacy because DOT is they are the only protocol protocols currently standardized by the IETF and DOH is expected to be a standard shortly (as of May 2018).

Some history and background on other alternatives are outlined below and we intend to follow other solutions as they evolve.

Table of Contents

DNS-over-TLS (



RFC7858 specified DNS-over-TLS as a Standards Track protocol in May 2016 with a port assignment of 853 from IANA. There is active work in this area.

There are now multiple implementations (including Stubby a local DNS Privacy stub resolver) and a number of experimental servers deployed and public servers deployed

DNS-over-HTTP (DoH)

RFC8484 specifies DNS-over-HTTPS as a Standards Track protocol on October 2018.  

There are several implementations (including Firefox) and deployments.  Note that with DoH it is possible to intermingle DNS and HTTP traffic on the same port 443 connection and make blocking of encrypted DNS harder. It should be noted that this RFC addresses almost purely protocol issues, there is no dynamic discovery mechanism for DoH specified yet so it cannot be done opportunistically (it must be configured).  


RFC8094 specified  specified DNS-over-DTLS as an Experimental Standard in Feb 2017. To our knowledge that are no implementations of DNS-over-DTLS planned or in progress.

One issue with DNS-over-DTLS is that it must still truncate DNS responses if the response size it too large (just as UDP does) and so it cannot be a standalone solution for privacy without a fallback mechanism (such as DNS-over-TLS) also being available.


The IETF created a new DOH working group in Sept 2017 to look at how DNS messages could be sent over an existing HTTP/2 connection. It is in the very early stages but one advantage of this approach would be to intermingle DNS and HTTP traffic on the same connection and make blocking of encrypted DNS harder. As of May 2018 the draft is in WGLC and there are several experimental implementations and deployments. It should be noted that this draft addresses almost purely protocol issues and a follow up document on discovery and operational usage is expected. 


DNSCrypt is a method of authenticating communications between a DNS client and a DNS resolver that has been around since 2011.