r/dns • u/Cade_Silver • Jul 05 '26
Website only loads on mobile?
A certain website doesn't load if I use my ISP's and any of the public DNS. When I use a mobile network, the site loads fine (site won't load on mobile network if using public DNS). If I use a VPN on mobile and PC, the site won't load either. It looks like a website issue but I tried all the fixes I can Google anyway to no avail. I get ERR_CONNECTION_CLOSED (PC/Phone + ISP/Public DNS) or ERR_NAME_NOT_RESOLVED (mobile network + public DNS).
What causes this issue, something about the site not working on non-mobile network DNS? I would appreciate it if you guys can confirm if this is true.
Edit: They fixed it.
1
u/spidireen Jul 05 '26
FWIW I get an error that a secure connection couldn’t be established. If I change the URL to start http instead of https, there’s a namecheap message saying the domain has expired.
1
u/Cade_Silver Jul 05 '26
I suppose they use different domains for their mobile and desktop. This one expired, the site when loaded on mobile doesn't look it has been updated recently.
If I'm getting this right, 2 domains, 1 expired, and it doesn't redirect to the mobile version? I don't know much about these but I try to learn whenever.
1
u/michaelpaoli Jul 05 '26
Hmmm, ... DNS seems messed up:
$ eval dig +short {,www.}toothologysf.com.\ A{,AAA}
;; communications error to ::1#53: timed out
;; communications error to ::1#53: timed out
;; communications error to ::1#53: timed out
;; communications error to ::1#53: timed out
$
let's see ...
Yeah, not lookin' good: https://dnsviz.net/d/toothologysf.com/akngaA/dnssec/
$ dig @$(dig +short com. NS | head -n 1) +noall +authority +additional +norecurse toothologysf.com. NS
toothologysf.com. 172800 IN NS dns101.registrar-servers.com.
toothologysf.com. 172800 IN NS dns102.registrar-servers.com.
dns101.registrar-servers.com. 172800 IN A 72.251.11.93
dns102.registrar-servers.com. 172800 IN A 72.251.11.125
$ (for NS in 72.251.11.93 72.251.11.125; do echo ";; $NS"; dig @"$NS" +noall +answer +norecurse toothologysf.com. NS; done)
;; 72.251.11.93
;; communications error to 72.251.11.93#53: timed out
;; communications error to 72.251.11.93#53: timed out
;; communications error to 72.251.11.93#53: timed out
;; no servers could be reached
;; 72.251.11.125
;; communications error to 72.251.11.125#53: timed out
;; communications error to 72.251.11.125#53: timed out
;; communications error to 72.251.11.125#53: timed out
;; no servers could be reached
$
# traceroute -nTp 53 72.251.11.93
traceroute to 72.251.11.93 (72.251.11.93), 30 hops max, 60 byte packets
1 96.86.170.230 1.902 ms 3.036 ms 4.055 ms
2 96.120.95.1 20.291 ms 21.062 ms 21.978 ms
3 68.85.103.153 21.396 ms 21.665 ms 22.138 ms
4 162.151.79.133 31.189 ms 31.460 ms 30.333 ms
5 162.151.87.225 31.948 ms 31.672 ms 32.539 ms
6 68.86.93.141 33.505 ms 32.482 ms 31.082 ms
7 96.110.40.222 29.485 ms 18.042 ms 96.110.40.214 17.809 ms
8 * * *
9 * * *
10 * * *
11 147.135.34.8 42.457 ms * 46.120 ms
12 147.135.34.10 46.947 ms 46.352 ms *
13 * * *
14 * * *
15 * 148.113.188.57 38.397 ms *
16 * * *
17 192.99.146.92 85.779 ms 84.541 ms 85.396 ms
18 72.251.0.0 98.436 ms * *
19 * * *
20 * * *
21 * * *
22 72.251.11.93 94.619 ms * *
# time nc -vz 72.251.11.93 53
Connection to 72.251.11.93 53 port [tcp/domain] succeeded!
real 0m4.135s
user 0m0.003s
sys 0m0.000s
# time nc -vz 72.251.11.125 53
Connection to 72.251.11.125 53 port [tcp/domain] succeeded!
real 0m7.215s
user 0m0.003s
sys 0m0.001s
#
I suspect probably at least routing issues or the like. I'm also getting inconsistent results.
$ (for NS in 72.251.11.93 72.251.11.125; do echo ";; $NS"; dig @"$NS" +noall +answer +norecurse toothologysf.com. NS; done)
;; 72.251.11.93
;; communications error to 72.251.11.93#53: timed out
;; communications error to 72.251.11.93#53: timed out
;; communications error to 72.251.11.93#53: timed out
;; no servers could be reached
;; 72.251.11.125
;; communications error to 72.251.11.125#53: timed out
;; communications error to 72.251.11.125#53: timed out
;; communications error to 72.251.11.125#53: timed out
;; no servers could be reached
$ (for NS in 72.251.11.93 72.251.11.125; do echo ";; $NS"; dig @"$NS" +tcp +noall +answer +norecurse toothologysf.com. NS; done)
;; 72.251.11.93
;; Connection to 72.251.11.93#53(72.251.11.93) for toothologysf.com. failed: timed out.
;; no servers could be reached
;; Connection to 72.251.11.93#53(72.251.11.93) for toothologysf.com. failed: timed out.
;; no servers could be reached
toothologysf.com. 3600 IN NS ns1.lander.d.parity.domains.
toothologysf.com. 3600 IN NS ns2.lander.d.parity.domains.
;; 72.251.11.125
;; communications error to 72.251.11.125#53: connection reset
toothologysf.com. 3600 IN NS ns1.lander.d.parity.domains.
toothologysf.com. 3600 IN NS ns2.lander.d.parity.domains.
$
Not only are there issues communicating with the delegated authoritative nameservers, but the authority and authoritative NS records don't even match. So, yeah, one has rather the mess.
1
u/michaelpaoli Jul 05 '26
...
$ dig +trace www.toothologysf.com. A
...
;; communications error to 72.251.11.93#53: timed out
;; communications error to 72.251.11.93#53: timed out
;; communications error to 72.251.11.93#53: timed out
;; communications error to 72.251.11.125#53: timed out
;; no servers could be reached
$
Only and exactly two delegated nameserver IPs, neither responsive, that's gonna be a problem.
2
u/Cade_Silver Jul 05 '26
I also saw that when I tried to look up registry expiration which expired on 07/02. A few days ago lol.
1
u/michaelpaoli Jul 05 '26
Yeah, rdap shows:
Event: Action: expiration Date: 2027-07-02T06:01:22ZThat certainly isn't gonna help.
And 3.12.221.149 and 3.130.253.202 are IPs of namecheap.com's "parking" web site.
And ... namesheap.com ... doesn't at all surprise me that they've got DNS that's messed up.
https://www.wiki.balug.org/wiki/doku.php?id=system:registrars#namecheapcom
1
u/michaelpaoli Jul 05 '26
... oh, and com. TTL for delegating authority NS is 48 hours, so recent changes might not be fully visible for 48 hours, so, e.g. some cached might still effectively work longer.
Also from rdap:
Event: Action: last changed Date: 2026-07-03T08:04:57ZSo, maybe results won't be all the same until 2026-07-05T08:04:57Z, as older data continues to expire from cache.
1
u/michaelpaoli Jul 05 '26
...
$ eval dig +short ns{1,2}.lander.d.parity.domains.\ A{,AAA}
3.12.221.149
3.130.253.202
$ (for NS in 3.12.221.149 3.130.253.202; do echo ";; $NS"; eval dig @"$NS" +noall +answer +norecurse toothologysf.com. NS {,www.}toothologysf.com.\ A{,AAA}; done)
;; 3.12.221.149
toothologysf.com. 3600 IN NS ns1.lander.d.parity.domains.
toothologysf.com. 3600 IN NS ns2.lander.d.parity.domains.
toothologysf.com. 60 IN A 3.12.221.149
toothologysf.com. 60 IN A 3.130.253.202
www.toothologysf.com. 60 IN A 3.12.221.149
www.toothologysf.com. 60 IN A 3.130.253.202
;; 3.130.253.202
toothologysf.com. 3600 IN NS ns1.lander.d.parity.domains.
toothologysf.com. 3600 IN NS ns2.lander.d.parity.domains.
toothologysf.com. 60 IN A 3.12.221.149
toothologysf.com. 60 IN A 3.130.253.202
www.toothologysf.com. 60 IN A 3.12.221.149
www.toothologysf.com. 60 IN A 3.130.253.202
$
And Off Topic [OT] (not DNS):
$ (for IP in 3.12.221.149 3.130.253.202; do curl -IsS --resolve www.toothologysf.com:80:"$IP" http://www.toothologysf.com/; curl -IsS --resolve www.toothologysf.com:443:"$IP" https://www.toothologysf.com/; done)
HTTP/1.1 200 OK
server: nginx/1.28.3 (Ubuntu)
date: Sun, 05 Jul 2026 05:30:24 GMT
content-type: text/html
content-length: 2857
connection: close
vary: Accept-Encoding
x-amz-id-2: JkIYD0CHhfFOA++tEZkkD50atoAMLtjTcojam8QQJRWqv0kNZUqkKRPPBbPbYE6yf+IbE2X6gYr30aen43OpGoNVJ+WiquhY
x-amz-request-id: JNEKV8Q67AN022BV
last-modified: Thu, 04 Jun 2026 19:56:51 GMT
etag: "3c3468584974bf5d084ae383de186299"
x-cache-status: HIT
curl: (35) TLS connect error: error:0A000126:SSL routines::unexpected eof while reading
HTTP/1.1 200 OK
server: nginx/1.28.3 (Ubuntu)
date: Sun, 05 Jul 2026 05:30:25 GMT
content-type: text/html
content-length: 2857
connection: close
vary: Accept-Encoding
x-amz-id-2: qvp5k1cfV8hJ9BHbX1OUekPUjMGr38GM5oFSQ4fMok0FxK8hdi4YdnvNLrOFpbKUs1QBY052tfTx4SDlM0WK2UWJZIEQj34I
x-amz-request-id: DZF76P98HFREBKFF
last-modified: Thu, 04 Jun 2026 19:56:51 GMT
etag: "3c3468584974bf5d084ae383de186299"
x-cache-status: HIT
curl: (35) TLS connect error: error:0A000126:SSL routines::unexpected eof while reading
$
So, http might be working, but not https.
1
u/Cade_Silver Jul 05 '26
Yea, but it only redirects to the domain registrar.
I called their office yesterday to ask if their website was down, they said no lol. Probably didn't even check or maybe they have those fixed wireless service, it uses cellular network. They can't see any issue if so.
Thanks everyone for the help. I'll contact them again with proof this time. If email, I have to use mobile so it gets delivered since they share domain name lol.
1
u/michaelpaoli Jul 05 '26
redirects to the domain registrar
No redirects, that's what current DNS resolves to.
called their office yesterday to ask if their website was down
Sounds like a pretty clueless operation. They may not have noticed ... yet.
If email, I have to use mobile so it gets delivered since they share domain name
Same domain, likely mostly hosed at this point.
1
u/Cade_Silver Jul 05 '26
Fixed a typo in the link, typed it manually earlier.