Thank you for testing.
When I use the same Saumsung S22 phone on 5G data or VPN while connected to my router, I don't have issues.
I tried to go to:
Then click shieldsup, but same result. Blank page for the scanner.
-
DNS Benchmark v2 is Finished and Available! Guest:
That's right. It took an entire year, but the result far more accurate and feature laden than we originally planned. The world now has a universal, multi-protocol, super-accurate, DNS resolver performance-measuring tool. This major second version is not free. But the deal is, purchase it once for $9.95 and you own it — and it's entire future — without ever being asked to pay anything more. For an overview list of features and more, please see The DNS Benchmark page at GRC. If you decide to make it your own, thanks in advance. It's a piece of work I'm proud to offer for sale. And if you should have any questions, many of the people who have been using and testing it throughout the past year often hang out here.
/Steve. -
Be sure to checkout “Tips & Tricks” Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!
/Steve. -
BootAble – FreeDOS boot testing freeware
To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.
GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.
The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.
You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.
(You may permanently close this reminder with the 'X' in the upper right.)
Thank you for testing.
When I use the same Saumsung S22 phone on 5G data or VPN while connected to my router, I don't have issues.
I tried to go to:
Have you tried to see what path your traffic to ShieldsUp is taking using Traceroute or similar? That might show whether your ISP connection is using Google Web Accelerator.
Same here, computer (Firefox) connected to my Ubiquity router, I tried both wired and wireless. Same with my phone when I'm connected to the wifi (and which I did not use to test ports). However, when I'm on Verizon LTE, or when I'm using a VPN it works fine. My guess is that checking too many ports makes the ISP or maybe router freak out.
Traceroute:
192.168.1.1
209.33.***.1
10.36.0.230
10.32.0.172
10.32.0.202
4.53.42.165 (et-1-0-16.bar3.SaltLakeCity1.Level3.net)
4.69.210.33 ( ae1.3505.ear1.LosAngeles1.net.lumen.tech)
4.79.142.202 (www.grc.com)
The iamroot port scan works fine.
Update:
The next day things worked fine again. Maybe it just takes a bit to reset.
Traceroute:
192.168.1.1
209.33.***.1
10.36.0.230
10.32.0.172
10.32.0.202
4.53.42.165 (et-1-0-16.bar3.SaltLakeCity1.Level3.net)
4.69.210.33 ( ae1.3505.ear1.LosAngeles1.net.lumen.tech)
4.79.142.202 (www.grc.com)
The iamroot port scan works fine.
Update:
The next day things worked fine again. Maybe it just takes a bit to reset.
Last edited:
Those 10.*.*.* addresses look as if they might be internal in your ISP's network. Who knows what they are doing.
#1
- IP Address: 192.168.1.1
#2
- IP Address: 100.92.xxx.2
#3
- IP Address: 96.216.26.61
#4
- IP Address: 24.153.88.178
#5
- IP Address: 24.153.88.94
#6
- IP Address: 162.151.45.109
#7
- IP Address: 96.216.150.118
#8
- not listed by Traceroute
#9
- IP Address: 4.69.210.37
#10
- IP Address: 4.79.142.202
Last edited:
@AlanD @cart1443 @ObiWan @EdwinG @PHolder @Tazz @DanR
The issue is resolved.
I waited about 5 days before trying to access the website grc.com
Once I turned off safe browsing and pre-loading in chrome, my IP address was listed accurately.
Open the browser, go to "settings" and "privacy and security", then click on "preload pages" and select "no preloading", then go to "safe browsing" and click on "no protection". I also turned off Secure DNS on my phone.
Summary: Combination of just waiting 5 days and turning off some settings in chrome worked for my android phone connected to my home network with Xfinity as ISP. I was able to run a scan this morning
Thank you all very much for your help.
Moderator, you may close this post if required.
The issue is resolved.
I waited about 5 days before trying to access the website grc.com
Once I turned off safe browsing and pre-loading in chrome, my IP address was listed accurately.
Open the browser, go to "settings" and "privacy and security", then click on "preload pages" and select "no preloading", then go to "safe browsing" and click on "no protection". I also turned off Secure DNS on my phone.
Summary: Combination of just waiting 5 days and turning off some settings in chrome worked for my android phone connected to my home network with Xfinity as ISP. I was able to run a scan this morning
Thank you all very much for your help.
Moderator, you may close this post if required.
It's been a while since I checked my firewall using Shields Up. First time I did I had tested my FreeBSD ipfw firewall at the time.
I wonder what the rationale behind checking the first 1056 ports instead of the first 1024 is?
I also think that 2049 should also be in the common ports test.
I wonder what the rationale behind checking the first 1056 ports instead of the first 1024 is?
I also think that 2049 should also be in the common ports test.