Can't access 1.1.1.1

I can’t even visit the site 1.1.1.1. pinging 1.0.0.1 works.
I saw many threads about this issue, and I am going to provide all the information requested here Have problems with 1.1.1.1? *Read Me First*

Okay, first the diagnostic tool (1.1.1.1 — the Internet’s Fastest, Privacy-First DNS Resolver) doesn’t open just like 1.1.1.1, browser says unable to connect.
dig example.com 1.1.1.1

; <<>> DiG 9.16.25 <<>> example.com 1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27624
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;example.com.			IN	A

;; ANSWER SECTION:
example.com.		35975	IN	A	93.184.216.34

;; Query time: 210 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Tue Feb 01 21:15:14 IST 2022
;; MSG SIZE  rcvd: 56

;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 62485
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;1.1.1.1.			IN	A

;; AUTHORITY SECTION:
.			862	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2022020100 1800 900 604800 86400

;; Query time: 120 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Tue Feb 01 21:15:14 IST 2022
;; MSG SIZE  rcvd: 111

dig example.com 1.0.0.1

; <<>> DiG 9.16.25 <<>> example.com 1.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4453
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;example.com.			IN	A

;; ANSWER SECTION:
example.com.		35928	IN	A	93.184.216.34

;; Query time: 0 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Tue Feb 01 21:16:01 IST 2022
;; MSG SIZE  rcvd: 56

;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 39971
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;1.0.0.1.			IN	A

;; AUTHORITY SECTION:
.			1061	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2022020100 1800 900 604800 86400

;; Query time: 363 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Tue Feb 01 21:16:02 IST 2022
;; MSG SIZE  rcvd: 111


; <<>> DiG 9.16.25 <<>> example.com 8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11435
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;example.com.			IN	A

;; ANSWER SECTION:
example.com.		35911	IN	A	93.184.216.34

;; Query time: 0 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Tue Feb 01 21:16:18 IST 2022
;; MSG SIZE  rcvd: 56

;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 38463
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;8.8.8.8.			IN	A

;; AUTHORITY SECTION:
.			449	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2022020100 1800 900 604800 86400

;; Query time: 350 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Tue Feb 01 21:16:18 IST 2022
;; MSG SIZE  rcvd: 111

The next dig commands just dont return anything.

traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 60 byte packets
 1  _gateway (192.168.1.1)  1.349 ms  1.440 ms  1.557 ms
 2  1.128.16.172 (1.128.16.172)  3.173 ms  3.288 ms  3.384 ms
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
traceroute 1.0.0.1
traceroute to 1.0.0.1 (1.0.0.1), 30 hops max, 60 byte packets
 1  _gateway (192.168.1.1)  0.659 ms  0.769 ms  0.921 ms
 2  1.128.16.172 (1.128.16.172)  2.757 ms  2.861 ms  2.959 ms
 3  103.88.221.181 (103.88.221.181)  3.094 ms  5.713 ms  5.131 ms
 4  * * *
 5  as13335.bom.extreme-ix.net (103.77.108.118)  7.280 ms  6.289 ms  6.553 ms
 6  162.158.226.17 (162.158.226.17)  7.667 ms  7.533 ms *
 7  one.one.one.one (1.0.0.1)  123.944 ms  1.779 ms  2.978 ms
dig +tcp @1.1.1.1 id.server CH TXT

; <<>> DiG 9.16.25 <<>> +tcp @1.1.1.1 id.server CH TXT
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOTIMP, id: 47060
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;id.server.			CH	TXT

;; Query time: 3 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Tue Feb 01 21:20:29 IST 2022
;; MSG SIZE  rcvd: 38



dig +tcp @1.0.0.1 id.server CH TXT

; <<>> DiG 9.16.25 <<>> +tcp @1.0.0.1 id.server CH TXT
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOTIMP, id: 30090
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;id.server.			CH	TXT

;; Query time: 0 msec
;; SERVER: 1.0.0.1#53(1.0.0.1)
;; WHEN: Tue Feb 01 21:20:23 IST 2022
;; MSG SIZE  rcvd: 38
openssl s_client -connect 1.0.0.1:853
140075653096832:error:0200206F:system library:connect:Connection refused:crypto/bio/b_sock2.c:110:
140075653096832:error:2008A067:BIO routines:BIO_connect:connect error:crypto/bio/b_sock2.c:111:
connect:errno=111
openssl s_client -connect 1.1.1.1:853
140643597018496:error:0200206F:system library:connect:Connection refused:crypto/bio/b_sock2.c:110:
140643597018496:error:2008A067:BIO routines:BIO_connect:connect error:crypto/bio/b_sock2.c:111:
connect:errno=111

kdig: Unknown command.

curl -H 'accept: application/dns-json' 'https://cloudflare-dns.com/dns-query?name=cloudflare.com&type=AAAA'
curl: (7) Failed to connect to cloudflare-dns.com port 443 after 550 ms: Connection refused

Looks like your network provider or a local application is intercepting the DNS queries on port 53 and blocking access to https://cloudflare-dns.com.

This can happen with tools like ZScaler’s Zero Trust Client or a SWG.

Sorry, I don’t understand you. My isp is intercepting the dns queries on port 53? What can I do about it?

What country and city are you located in, or doing this test from?

India, Mumbai. Sorry for the late reply, I was out of town.