Launched in May, Chrome 83 brought the desktop to the DNS-over-HTTPS (DoH) – DNS over HTTPS -, a feature that reinforces the user’s security and privacy by making it difficult to monitor their browsing. Now, with the launch of Google Chrome 85, the same functionality comes to Android phones and tablets.
Whenever you access a website by entering a domain (tecnoblog.net, for example), the browser queries a DNS (Domain Name System) server to discover the IP associated with that address.
The problem is that, as a rule, queries of this type are not protected, even when the site has HTTPS ((Hyper Text Transfer Protocol Secure), an implementation that adds a layer of security to the connection through SSL / TLS.
This is where DNS-over-HTTPS takes on importance. With this feature, the browser performs encrypted queries to DNS servers. Without this protection, the communication between your equipment and the DNS service can be monitored, allowing an attacker or your ISP to discover which pages you have accessed, for example.
According to Google, Chrome 85 (and later versions) will automatically activate DoH if the consulted DNS service supports the feature. Likewise, the functionality will be disabled by the browser when it cannot be used to prevent the user from experiencing interruptions in navigation.
It is also possible to configure DNS-over-HTTPS manually – to indicate a specific DNS server, for example – as well as to leave the functionality completely disabled. There are also configurations available to apply the feature in corporate environments.
But even if you already have Chrome 85, you may not have immediate access to DoH. The novelty is being made available gradually to “guarantee the stability and performance of the resource”, say the responsible developers.
Gradual release can also be a “good neighborhood policy”. Google points out that it is open to feedback from “interested parties”, including mobile operators and internet providers. Why is that? DoH has been in test since 2019 and, at that time, these companies made it clear that they were not at all happy with the change.
It is also worth noting that the DoH is being implemented on Chromium, therefore, it is assumed that other browsers based on this protection will also have access to the resource.