Well it wasn't obvious what security reasons there would be for DNS over HTTPS to cause archive.today to shit itself, but I did some digging and found this:
"Archive.is’s owner is intentionally blocking 1.1.1.1 users."
It appears archive.today doesn't like Cloudflare DNS because Cloudflare doesn't allow archive.today to geolocate users. So maybe solving a captcha is a compromise, but then it's just an infinite loop of captcha. That's shit.
chrimony 3 points 1.5 years ago
Well it wasn't obvious what security reasons there would be for DNS over HTTPS to cause archive.today to shit itself, but I did some digging and found this:
"Archive.is’s owner is intentionally blocking 1.1.1.1 users."
https://jarv.is/notes/cloudflare-dns-archive-is-blocked/
It appears archive.today doesn't like Cloudflare DNS because Cloudflare doesn't allow archive.today to geolocate users. So maybe solving a captcha is a compromise, but then it's just an infinite loop of captcha. That's shit.