Are you suggesting the cert problem is DNS related or the new captcha issue?
DNS was ISP, not 1.1.1.1, and I get the same behaviour after switching to 8.8.8.8.
DNS was ISP, not 1.1.1.1, and I get the same behaviour after switching to 8.8.8.8.
That said, I have the same problem. Even hard coding the IP address I resolved through Google doesn't seem to work. I'm guessing their sabotage may have backfired and is causing issues beyond their intentional scope?
I had to switch back to my ISP DNS to have connection successful.
I did not realize that choice of DNS resolver could effect access to a website like this. I thought DNS was boring stable technology. The error conditions weren't even DNS failure (which I would also find surprising from Google or Cloudflare), but that server timeout, or weirder infinite captcha loop.
captcha is CF
Related: Does Cloudflare’s 1.1.1.1 DNS Block Archive.is? (2019)
HN Discussion (209-comments 2023-08-02) https://news.ycombinator.com/item?id=36970702
I just snapshot this page for a test : https://archive.is/MUhAP = https://news.ycombinator.com/item?id=37009598
Edit of formatting for readability.
Do they run their own resolver, or rely on an extant service?
I'm reticent to disclose my current DNS provider,
given that I am able to access archive.is and many are not at this point of time.
Edit
I have just checked 9.9.9.9 and they are serving the correct response now. (incorrect earlier)