kasperdkasperd@westergaard.social
Oct 20, 2026, 6:24 PMSame problem regardless of whether I visit the site in Chromium or Firefox.
Replies
Cats Who Code (cursed)CatsWhoCode@twoot.siteOct 20, 2026, 6:27 PM- kasperdkasperd@westergaard.socialOct 20, 2026, 6:34 PMIt does try to access each URL. But they fail before it gets to the TLS handshake, so it never reaches the validation it's intended to test.
And then it reports the browser is safe. I presume they report every failure as a success and not only those where it fails during certificate validation.
A correct output would be:
- A successful connection is reported as unsafe
- A connection failed due to the TLS certificate is reported as safe
- A connection failed for any other reason is reported as inconclusive - Cats Who Code (cursed)CatsWhoCode@twoot.siteOct 20, 2026, 6:45 PM
- kasperdkasperd@westergaard.socialOct 20, 2026, 6:56 PMHere is what I get in Firefox.
I tried with and without DNS64 to see if there was a difference. The final output is identical in both cases.
Without DNS64 it reports success instantly without conducting the tests.
With DNS64 there is a noticeable delay while the test is running before the results are displayed. I think it is performing the actual test in that case, but the network tab doesn't show a useful error code in Firefox like it does in Chromium.
