If your site works on one network but not on Jio, Airtel or another ISP, test it from several networks and resolvers before you touch the server. Researchers have documented Indian ISPs blocking sites at the DNS level and at the HTTPS handshake, and occasionally an innocent site is caught up in it. A host cannot lift a block, but you can find out quickly whether you are looking at one.
Blocking in India is done by each ISP on its own network, usually following government orders under Section 69A of the IT Act or court orders. A 2020 study by the Centre for Internet and Society (CIS), which tested six ISPs, found that the methods differed by provider. It reported that Airtel answered DNS queries for blocked sites with NXDOMAIN (as if the name did not exist), and that Jio blocked HTTPS sites by inspecting the server name in the connection, known as SNI inspection.
A 2026 report called Poisoned Wells by independent researcher Karan Saini, covered by MediaNama in March 2026, describes the wider toolbox: HTTP blocking that reads the Host header, DNS poisoning or injection, and SNI based blocking that drops or resets the TLS connection. Saini said he believed Jio uses SNI inspection, which he presented as his inference rather than a confirmed finding. The report covered six ISPs that together serve about 82 per cent of Indian subscribers.
These studies are snapshots. ISPs change methods, and a technique seen in 2020 may not be the one in use today, so use them to know what to test, not as a guarantee of what any ISP is doing this week.
Usually it is not a targeted block. Several things can catch a legitimate site. A previous owner of the domain may have used it for something that was ordered blocked, and Saini's report says ISPs keep blocking domains after they expire, with no legal requirement to stop. A shared IP address or a hostname pattern can also be affected, and over-broad orders can sweep in unrelated domains.
A recent public example is Supabase, a developer platform. MediaNama reports its domains became inaccessible on Jio, Airtel and ACT Fibernet from 27 February 2026 while some users could still reach them. About six days later the company said the issue was resolved. Supabase suggested a blocking order might be responsible, but no public order had been found at the time. The episode shows how a block can appear, hit only some users and disappear without a clear explanation.
Work from the outside in. The aim is to separate three things: the name not resolving, the connection being cut, and your server genuinely being down.
A browser message such as DNS_PROBE_FINISHED_NXDOMAIN means the name did not resolve on that network. It is also what a mistyped or expired domain produces, so check the domain's own status first, and see the guide to the NXDOMAIN error for the non-blocking causes. Cached answers can also mislead you, so flush the DNS cache on your device before drawing conclusions.
A connection reset or timeout after DNS resolves, only on one network and only for HTTPS, fits the SNI pattern described in the CIS study. CIS also noted that SNI blocking makes it technically impossible for an ISP to show a censorship notice, so you may get no explanation at all. A block page, when it appears, usually points to HTTP or DNS level handling. Our common DNS errors guide lists the other failures that look similar.
Be realistic about the options. Your hosting provider cannot change what an ISP does on its own network, and no hosting plan prevents it. What you can do is gather evidence (which ISPs, which error, since when, screenshots of the lookups), contact the ISP's support and ask whether a blocking order applies to your domain, and tell affected customers to try another DNS resolver while it is investigated.
CIS notes that India's net neutrality rules, in ISP licence agreements, prohibit blocking without a legal order, which is a reasonable basis for asking the ISP to identify the order. For a business with real losses, a lawyer who works on IT Act matters is the right next step. Nothing here is legal advice, and the legal route is for the owner and counsel to judge.
Keep the rest of the setup healthy while you wait: keep your SSL valid, avoid changing hosts or nameservers mid-investigation because it clouds the testing, and keep the nameserver records documented so you can show nothing changed on your side.
HostBible's DNS checker shows what DNS returns for your domain, which helps you compare against what one ISP gives you. It reports what DNS returns; it cannot remove an ISP block.
Run a DNS lookup