I did read about that, and it has nothing to do with the problem the OP was raising. If you try to resolve archive.is with 1.1.1.1, you get a bogus IP and don't

I did read about that, and it has nothing to do with the problem the OP was raising. If you try to resolve archive.is with 1.1.1.1, you get a bogus IP and don't reach any HTTP server at all. This doesn't explain why some would see a huge amount of CAPTCHA served by archive.is or archive.today if they do reach an IP that serves the right TLS certs, but only if they got that IP from 1.1.1.1 instead of getting it from 8.8.8.8 or wherever.