It takes the domain name and resolves it to the associated IP address, which your computer can then use to communicate with the server. And this is exactly where a Domain Name Server comes in. Now all we need a system to map this easy to remember domain name to the associated IP address. As a result domain names were developed to make it easier to remember the 'address' of a server. However this, and more specifically an IP address, is exactly what a computer uses to access a server.

We humans are not great at remembering numbers. Meaning that anyone who has the ability to view the network traffic, would be able to view these queries. This is due to the fact that DNS queries happen over plain text. One of the privacy related concerns existing today, is that anyone between your computer and the server which you are tying to connect to (be it your ISP, government, an eavesdropper, etc) can see which sites you hit. How it helps provides privacy, and how far it goes in doing that. So I decided to do a bit of investigating of what is and isn't possible with this service.

While most might assume that this will go to great lengths to help ensure that their browsing privacy is maintained, I was a bit dubious, and felt that I was missing something completely. As many of you may be aware, Cloudflare recently announced their new 'privacy-first' consumer DNS service.

Seacrh domain in wireshark https