http://composition-for-the-infinite-scroll-14.66ghz.com/ but also multiple others using the same domain.
Have tested in Firefox and Chrome, desktop and mobile on two separate networks - page never loads and I get “The Connection was reset”.
Testing on the command line with nslookup I get:
“server can’t find http://composition-for-the-infinite-scroll-14.66ghz.com/: NXDOMAIN”
echoing what Frank419 said, seems to be working. Can you access 66ghz.com?
Hi Thanks for your replies. I had a colleague in the US test it this morning and it works from there. Good to see that another UK based user (Frank419) can access it.
I have many subdomains at 66ghz e.g.
http://composition-for-the-infinite-scroll-1.66ghz.com/
http://composition-for-the-infinite-scroll-2.66ghz.com/
(change the number at the end there are more)
and they are all inaccessible from here. It’s not my browser, it’s not a browser extension, it’s not my operating system (have now also tested from a Ubuntu machine) and it’s not my provider as I have rule all of these out in testing. The site have been up and working since April - working with no issues so it’s not a newly uploaded issue. I did notice at one point in June that Google was blacklisting the a few of my sites so I filled out the requests to remove it from the blacklist and this never happened again. At a loss as to what might be causing the issue.
Screenshot of http://composition-for-the-infinite-scroll-14.66ghz.com/ failing to load.
I might be wrong, but I dont think Frank based in the UK. I’m in the UK and can access your site fine.
Have you tried a VPN (such as the proton VPN) to see if that allows you to access it?
Just trying to track down where in the process the issue is occouring.
opps sorry, copied the wrong name - it was your profile I was referring to. I tried through Tor a few hours ago and it would not load. I’ve just tried through another VPN and the same, connection reset. Everything points to something local here but beyond browsers/extensions/OS/computers/network I’m stumped as to what it could be.
If you used the actual Tor browser, then that’s expectable. It’s built in NoScript functionality prevents the security system from recognizing you as using an actual web browser.
It’s also not unheard of for some websites and networks to block inbound connections from Tor exit nodes because of abuse rates, though I don’t know if InfinityFree’s provider does this or not.
What regular VPNs have you tried? This is very odd, because using any true VPN with a standard web browser should overcome all forms of blocking from your ISP or your local government, but everything points to this not being an issue on InfinityFree’s side.
Do you think you could please try doing a traceroute to your URL and posting the results? It’ll always terminate because InfinityFree’s servers block ping requests, but in this case it would allow us to see where in the chain of events your connection is being blocked.
If you used the actual Tor browser, then that’s expectable.
Yes I used Tor Browser.
What regular VPNs have you tried?
I used Proton VPN to test.
Traceroute from terminal for http://composition-for-the-infinite-scroll-14.66ghz.com/ produces “unknown host”. Traceroute via https://dnschecker.org/ produces:
Start: 2025-08-27T21:00:24+0500
HOST: DNSChecker.org Loss% Snt Last Avg Best Wrst StDev
1.|-- ??? 100.0 3 0.0 0.0 0.0 0.0 0.0
2.|-- 10.74.132.63 0.0% 3 3.5 1.8 0.7 3.5 1.5
3.|-- 138.197.248.254 0.0% 3 0.9 1.1 0.9 1.3 0.2
4.|-- 143.244.192.172 0.0% 3 0.3 0.4 0.3 0.6 0.2
5.|-- 143.244.225.216 0.0% 3 0.9 0.9 0.9 0.9 0.0
6.|-- 143.244.225.143 0.0% 3 3.0 1.5 0.7 3.0 1.3
7.|-- ix-be-11.ecore1.n75-newyork.as6453.net (66.110.100.140) 0.0% 3 1.0 1.1 1.0 1.2 0.1
8.|-- ??? 100.0 3 0.0 0.0 0.0 0.0 0.0
9.|-- ae9.cr13-nyc3.ip4.gtt.net (216.221.156.101) 0.0% 3 0.7 0.8 0.7 0.9 0.1
10.|-- ae7.cr1-nyc2.ip4.gtt.net (89.149.129.218) 0.0% 3 1.9 1.9 1.7 2.1 0.2
11.|-- ??? 100.0 3 0.0 0.0 0.0 0.0 0.0
12.|-- et-0-0-16-3.cr10-lon2.ip4.gtt.net (213.251.24.101) 0.0% 3 75.5 70.9 68.3 75.5 4.0
13.|-- ip4.gtt.net (213.251.24.102) 0.0% 3 70.8 70.8 70.7 71.0 0.1
14.|-- ??? 100.0 3 0.0 0.0 0.0 0.0 0.0
I meant from your own computer, via the terminal or command line. Using DNS Checker won’t help because then it’s doing the check from its own server, instead of your network.
You can find instructions on how to run a traceroute on Windows here:
I did both, one from terminal on OSX and one from that site. The one from terminal:
Another from my Ubuntu machine:
traceroute to composition-for-the-infinite-scroll-14.66ghz.com (185.27.134.165), 30 hops max, 60 byte packets
1 _gateway (192.168.0.1) 2.464 ms 3.565 ms 3.557 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
It terminates after reaching a gateway with internal IP address, which would seem to indicate that something on your network, or your PC itself, is terminating your connection, or your DNS resolver is preventing it from resolving.
That too would seem to indicate a DNS issue. There are other examples of forum members running into this problem.
This happens because, unfortunately, the free hosting gets abused quite a bit and some ISPs and DNS providers will block entire base domains for the free subdomains.
That seems to be exactly what’s happening here, though I admit I’m not sure why using a VPN doesn’t bypass it in your case. This can also be caused by software on the PC, such as an antivirus, preventing the connection for the same reason.
Your website seems to be working fine from here, and I’m not aware of any ongoing issues on our end.
The initial error message you shared and the screenshot you shared later are different errors though: one is a DNS error and the other is a connection error.
The connection reset error can also be DNS related though: if something in the middle is manipulating DNS results, then it’s possible that your browser is trying to connect something other than our hosting to find your website, and unable to do so.
So my money is on this being a DNS level block on your end. I suspect that your ISP or DNS provider may be blocking access to the 66ghz.com domain.
It’s strange though that using a VPN didn’t help, because it should. However, an incorrectly setup VPN connection may result in not all traffic being routed over the VPN. If DNS traffic does not go through the VPN, it would still be blocked by your ISP.
As a first step, I would try to configure your computer or router to use Google DNS (8.8.8.8) or Cloudflare DNS (1.1.1.1) instead of the current nameservers to rule out any blocks.
What did you do exactly to rule out a provider problem?
Contacted my ISP this afternoon and yes indeed they had blocked 66ghz.com domains. No reason why but they seem to have unblocked it now and I have access again so problem solved. Many thanks all for your responses.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.