3 ms·
For people saying; "its working for me". Here is the explanation. The block has been implemented using a hosts based method. Such methods work in HTTP as anyon
by ShirsenduK 9y ago
For people saying; "its working for me". Here is the explanation.
The block has been implemented using a hosts based method. Such methods work in HTTP as anyone on the network can intercept the traffic and modify it. This snooping is not possible in HTTPS, hence the word secure.
(Update: The above statement is misleading. Please read TallGuyShort's comment for clarity).
This kind of block sometimes take time to propagate given how our ISP networks are setup. The blockage can be implemented at any level. ISP, acquiring ISP, backbone etc.
But even HTTPS can get blocked via DNS provided you are using a DNS which is under the influence of DoT. Most internet users use Google DNS(8.8.8.8) or OpenDNS(208.67.222.222) or Berkeley DNS (4.2.2.2) as their DNS (They have fallback ips also). This is set in your network adapter settings or router settings. They are not under the influence of the DoT. I am not sure if there is a DNS block as I use Google DNS.
Also, IP based blockage is possible which restricts access to HTTPS sites but it is not the case here.
Censorship is no solution to piracy or terrorism. Burying your head in the sand doesn't solve the problem.
Edit: Updated to read TallGuyShort's comment.
- TallGuyShort 9y ago>> The block has been implemented using a hosts based method I'm curious what exactly you mean by hosts-based. For it affect HTTP but not HTTPS, routers would have to be inspecting TCP packets and parsing HTTP. I'd call that packet-sniffing. hosts-based sounds like the DNS-level block to me. Am I missing something?
- ShirsenduK 9y agoYou are correct. I should have explained it better. I tried to over simplify it and ended up writing misinformation.
- jwilk 9y agoUsing an alternative DNS server won't necessarily save you from DNS-based censorship. The ISP can modify any DNS traffic they want. I actually had an ISP once that redirected all 53 port traffic to their own DNS server. It was "fun" every time this DNS server went down.
- captn3m0 9y agoJust using OpenDNS or Google DNS does not prevent DNS-based attacks. ISPs in India are known to do transparent DNS proxying. See https://www.dnsleaktest.com/what-is-transparent-dns-proxy.html https://www.dnsleaktest.com/what-is-transparent-dns-proxy.ht...
- mavidser 9y agoAFAIK, Jio, at least is using IP based blocking. Unable to ping or connect to any port on the the blocked IP addresses.