How is Airtel Blocking Even https:// Sites?

  • Thread starter Thread starter apuw
  • Start date Start date
  • Replies Replies 55
  • Views Views 22,886
This thread is so much in chaos and confusion. I read this thread 2 times really to understand whats been concluded here.

What scary from this thread is, Airtel is continuously experimenting with enforcing censorship even on https traffic and at some level they have been successful, in few years they probably will be able to achieve complete censorship control as most traffic (for almost all ISPs) pass through airtel and tata. The censorship for https traffic might be limited to airtel customers at first but once its successful a backroom meeting might force/tempt other ISPs to use their technology as it ensures DoT directives are upheld very well!
Capitalism FTW! /s
 
well the sooner people realize the value of a good VPN, the better it would be the people of this country. not only to get around stupid blocks but also to prevent snooping by your isp and your government.
 
I read this thread 2 times really to understand whats been concluded here.
Then you probably didn't read it good. Its been proven that Airtel uses Netsweeper by looking at the URL parameters and even news reports of the same.
 
Thanks for letting us know @Jiharsh. Can you please paste here the page source where the https:// linked is blocked. We maybe able to get more information out from it.
 
@Sushubh I was recently getting a NET::ERR_CERT_AUTHORITY_INVALID error on websites due to some configuration error on a Cisco product used by my LCO. This certificate was being used: Cisco Umbrella Secondary SubCA hkg-SG

This Google forum post describes my issue: exactly Google Groups

The error has since been resolved by contacting the LCO.

Any idea which Cisco product they are using and why?
 
Last edited:
@x720 You are probably right. I knew instantly that it was a problem from the LCO's side as I had previously seen phishing websites getting blocked by OpenDNS which I do not use. The certificate issue is there again and the LCO is still trying to fix it.

It is probably a configuration problem on a network device which is corrupting the secure certificate chain and leading to the aforementioned certificate errors.
 
Back