Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
On Thursday, the 27th of June 2024, an operational error lead to an automated wipe of the entire UP DNS production infrastructure. The complete redeployment of the UP DNS infrastructure completed after two days. In the course of this operational outage, the entire infrastructure was improved.
Public DNS over TLS (DoT) server with advertising, tracker, and malware blocking.
DNS Stamp
TLS host
IP
Port
adfree.usableprivacy.net
78.47.163.141
853
Public DNS over HTTPS (DoH) service with advertising, tracker, and malware blocking.
Public DNS over HTTPS (DoH) and DNS over TLS (DoT) resolver with ad, tracker, and malware filters.
Use the updns DoH service with your Android device to reduce the tracking of your mobile apps and protect against DNS analysis from your Internet service provider.
The updns service responds with 0.0.0.0 for filtered domains.
In the following screenshot you see that Snapchat App Analytics is blocked by the updns DoH server.
Our adfree DoH server works best against tracking by mobile apps. DNS-based blocking is very coarse-grained. We therefore recommend you use browsers with blocking extensions and use our DNS service primarily to counter mobile app tracking. You can exclude e.g. your mobile browser from Intra:
We run a public privacy-protecting DNS server with advertising, tracker, and malware filtering. The Usable Privacy DNS (updns) service is accessible via the encrypted and protocols. We use the unified hosts from to filter unwanted domains.
The software stack is available under the BSD 2-Clause License on GitHub.
On the 21th of September of 2020, our adfree DoH service faced an immediate spike in requests with a peak of 800K requests per hour (26 times our average request load at this time). The amount of requests led to service interruptions of several hours and our public adfree services became unresponsive during the attack. An adhoc analysis and mitigation showed that our DoH service where potentially hit by a DDoS attack from Turkmenistan.
The mean request rate for a representative set of 3,9 million DoH requests we analyzed, showed that clients had a mean rate of 2.6 DoH requests per second. We observed request rates up to 571 requests per second from the attackers network range.
For a split second one might have thought that the Usable Privacy DNS services all of a sudden became popular in Turkmenistan (maybe the "slashdot" effect, who knows ...). It however became clear that the source of the steep surge in requests originated from handful of class-c network ranges. e.g. one particular class-c network from Turkmenistan was responsible for almost 1,200 requests per second. Requests per class-c network for all other countries than Turkmenistan were below 255 requests per second.
