3 ms·

This is a separate issue from the previous Cloudflare issue and it manifests differently. Getting Captcha'd happens with non-cloudflare resolvers as well, tho

This is a separate issue from the previous Cloudflare issue and it manifests differently. Getting Captcha'd happens with non-cloudflare resolvers as well, tho not universally nor consistently. I forced all of Archive domains to query against Quad9 and started getting unskipable Captchas months ago - when I was local(US). When I placeshifted to overseas, Quad9 resolved to different IPs and those were usable.

bombcar 3y ago
The technical reasons behind it are that the archive.today guy wants any takedown notices to be cross-border, so he wants to know what country you are in so he can redirect you to a server outside it. Cloudflare doesn't support a DNS extension that allows this (eDNS maybe?) and so it fails.
- WarOnPrivacy 3y ago
  Captcha pages are being served at IPs that don't come from CloudFlare. ex: Users who exclusively resolve thru Quad9 are getting Captcha pages. Any inference that the Captcha issue is limited to CloudFlare users is incorrect.