README: add info about hosts file usage

README.md

@@ -71,6 +71,30 @@ Be aware that some applications or websites may break if too greedy policy is ta
 
 ----------
 
+## Why not just a simple hosts file??
+
+Of course, you can apply DNS sinkhole list to your device's `hosts` file (Linux: `/etc/hosts`, Android: `/system/etc/hosts`, Windows: `C:\Windows\System32\Drivers\etc\hosts`). However, there are some benefits and some drawbacks:
+
+**Benefits of `hosts`**:
+
+- _Simple setup_: no software installation or compilation
+
+- _No DNS server required_: thus no extra configuration/software overhead or server-specific security risks
+
+**Drawbacks of `hosts`**:
+
+- _Does not scale_: does not apply to a network segment or segments for which you want to block specific domain names. Applies only to single devices.
+
+- _No extra security_, such as enforced DNS-over-HTTPS*, proxy configurations** or DNSSEC*** verification, provided by a properly configured DNS server
+
+`*` By default, domain name lookups are done via UDP port 53, and DNS queries are unencrypted. Thus, anyone between you and the DNS server can read the domain name lookups your applications request. With [DNS-over-HTTPS](https://en.wikipedia.org/wiki/DNS_over_HTTPS), all DNS queries are wrapped in encrypted packets, sent through TCP port 443 and thus making your DNS queries unknown by others excluding you and the DNS server.
+
+`**` You can enforce DNS queries through a proxy, such as via a server of your choise or via [Tor network](https://en.wikipedia.org/wiki/Tor_(anonymity_network))
+
+`***` You can set-up DNS server of your choice to use enforced [DNSSEC](https://en.wikipedia.org/wiki/Domain_Name_System_Security_Extensions) policy. In other words, if a rogue DNS server to which your DNS query (domain name lookup) is pointed to, breaks DNSSEC chain, the query is being left unanswered.
+
+----------
+
 # License
 
 This repository uses MIT license. See [LICENSE](LICENSE) file for details.