zlacker

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.

>>ttctci+(OP)
>I've had infrequently occurring arcane cert/SSL issues <> Same error page as https://1.1.1.7/ ?

captcha is CF

Related: Does Cloudflare’s 1.1.1.1 DNS Block Archive.is? (2019)

HN Discussion (209-comments 2023-08-02) >>36970702

I just snapshot this page for a test : https://archive.is/MUhAP = >>37009598

Edit of formatting for readability.

>>ttctci+(OP)
Who is your ISP's DNS provider?

Do they run their own resolver, or rely on an extant service?

>>dredmo+M3
I do Not use my ISP's DNS!

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.

>>Troubl+h5
I have just checked 8.8.8.8 and they are serving the correct response now. (incorrect earlier)

Edit

I have just checked 9.9.9.9 and they are serving the correct response now. (incorrect earlier)

>>ttctci+(OP)
Archive.* sabotages their DNS records when Cloudflare queries for them. They don't like that Cloudflare doesn't do EDNS forwarding so they broke their service for people using 1.1.1.1.

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?

>>jeroen+un
If you use an Apple device and have iCloud Private Relay turned on, one of their providers is Cloudflare and that will cause the same issue.

>>jeroen+un
This just helped me realize why I couldn't get to archive.today anymore -- however, for me, both Google DNS (8.8.8.8) and CloudFlare DNS (1.1.1.1) resulted in either infinite captcha loop or timeout.

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.

>>Troubl+k6
Incorrect response here with 9.9.9.10 (unfiltered version of 9.9.9.9) As well as the corresponding Quad9 DOH