If they block the internet, or inject stuff in, then they should not be allow to call it the Internet Service Provider; it is not internet, then. The ISP should

If they block the internet, or inject stuff in, then they should not be allow to call it the Internet Service Provider; it is not internet, then. The ISP shouldn't care what application protocol you use. If carrier NAT is enabled (which in my opinion, it should be enabled by default, but the customer ought to have the ability to disable it if they want to disable it, so that you can have a real internet connection), then they might legitimately filter some transport protocols (e.g. TCP and UDP and other protocols in that layer) (but not application protocols), but if you disable NAT then you can use other transport protocols. I use a lot of stuff that isn't HTTP(S). (Still, the system domain name system should be independent of the implementation and the protocol in use. Whether you want to use HTTPS or something else for DNS, the browser shouldn't care.)