1.1.1.3 does not filter content if queries are made via DoT (DNS over TLS)

Hi,
based on my test the Cloudflare DNS 1.1.1.3 (No Malware or Adult Content) does not make Adult Content filter if the DNS query is made in DoT (DNS-over-TLS).
So, if I query 1.1.1.3 via UDP port 53 (normal DNS) the Adult Content filter works (I tried www.youporn.com and the answer was 0.0.0.0).
But if I query 1.1.1.3 via TCP port 853 using DoT (DNS-over-TLS) and I lookup for www.youporn.com I have the correct IP of www.youporn.com.

Is it normal?
If yes, when 1.1.1.3 will works with No Malware or Adult Content also for DoT (DNS-over-TLS)?
Thank you.

DoT is not currently supported for Cloudflare for Families.

1 Like

Thank you.
Any plan for implementation?
I hope also 1.1.1.2 and 1.1.1.3 will soon supports DoT and DoH also to benefit of “Android Private DNS” feature.

Thanks.

1 Like

If you’re looking to block adult content while adding security, such as 1.1.1.3 & secure DNS, take a look at Clouldflare for Teams. I’m using a similar setup as listed in the blog post below.

It’s been good so far though it’s still pretty new.

Thank you for your suggestion but for now I prefer to wait that Cloudflare will implement DoT also for 1.1.1.2 and 1.1.1.3.

1.1.1.3 needs to stop answering dot queries until this is implemented so Android automatic private DNS stops automatically disabling filtering.

1 Like

+1 Is this going to be impemented? Like, ever?

1.1.1.3 filtering over DoT would be awesome +1