This may be a DNS issue. I had the same problem with NextDNS. After switching my DNS servers to Cloud Flare DNS (1.1.1.1, 1.0.0.1), it works fine.

When this happens to me, it's either because I'm connected to a VPN, or I'm using Cloudflare's public DNS server.

Archive blocks VPNs. If you're on one, that could be why.

I've also found that archive.ph is significantly less accessible than archive.is despite hosting the same content. Pausing my VPN for a few minutes and then changing the .ph to .is fixed a similar captcha loop for me, though I still did need to solve a captcha for it.

I was having this problem earlier with different URLs I was searching for but the link above actually worked for me.

are you using a VPN? that happens often to me. might be a combo of that and ublock origin. I'm guessing archive gets a ton of attacks from VPN so they probably just have rules to captcha any VPN address. I have a local proxy on rpi setup and then a container in firefox that lets me use that to quickly swap to a proxy that uses my real IP. very handy for shit like this.

Try this: https://wapo.st/4qqatnA

Yeah never use Cloudflare DNS. They refuse to fix this issue. Use quad9 or Google DNS.

You have some extension issues going on, maybe. Seems to work fine in FF and chrome.

Anecdata: When it happens to me, disabling the VPN helps.

I bet all the downvoting helped with that.