I think this is much needed. Currently, devices try to make requests to &quot;special sites&quot; [0] and compare the responses to hardcoded expectations.<p>The WiFi operators usually try to redirect to (or inject) the captive portal site, where the DNS server and&#x2F;or gateway do some MITM. If you use DNSCrpyt, or if they only MITM on HTTP and you use a custom DNS server, then you&#x27;ll simply end up with connection errors. Connecting to a site with HTTPS (intentionally or due to HSTS) will also fail because it can&#x27;t be redirected.<p>The only way to fix this is obtaining a valid SSL CA cert to redirect HTTPS traffic (not really :) -  or this approach via DHCP&#x2F;RAs.<p>0: e.g. <a href="http:&#x2F;&#x2F;www.google.com&#x2F;blank.html" rel="nofollow">http:&#x2F;&#x2F;www.google.com&#x2F;blank.html</a>, <a href="http:&#x2F;&#x2F;www.google.com&#x2F;generate_204" rel="nofollow">http:&#x2F;&#x2F;www.google.com&#x2F;generate_204</a>