Both Chrome (with uBlock, even after turning on 3rd party cookies) and Firefox (vanilla, but always set to private browsing) are just in infinite loop of captchas on archive.ph for me - most don’t even result in a photo-square, but even those that do just loop back to the blocked page.
That’s so strange. I don’t see the captcha and I’d never heard anyone mention this before (I’ve been posting archive.ph links for months), but you’re now the second person in the last couple of days to say this.
It appears that it’s a DNS issue, since I use either cloudflare or google as my DNS
From reddit:
archive.today (and its aliases: .is .fo .il .md .ph .vn) actively sabotages DNS queries coming from Cloudflare (1.1.1.1, etc.), Quad9 (9.9.9.9, etc.), and possibly others (I didn’t check but there were reports that Google’s 8.8.8.8 is affected as well). The inconsistent results can be due to DNS cashing.
Obviously, switching to your ISPs DNS server or to a third party one that isn’t affected will fix the issue, but people have legitimate reasons for using those DNS servers and since archive.today is the only site that refuses to play the most plausible explanation is asshattery, and a better approach would be give them the finger and advocate the use of archive.org instead.
The odd bit is that flags anyone going through those DNS lookups by implying that it’s your computer or your corporate network which is infected with malware.
Why do I have to complete a CAPTCHA?
Completing the CAPTCHA proves you are a human and gives you temporary access to the web property.
What can I do to prevent this in the future?
If you are on a personal connection, like at home, you can run an anti-virus scan on your device to make sure it is not infected with malware.
If you are at an office or shared network, you can ask the network administrator to run a scan across the network looking for misconfigured or infected devices.
It does look like the DNS is the issue, as I just threw on the VPN - which doesn’t use the local DNS configuration - and it loaded up (after the capcha).
Well, that’ just leads to an uncompleteable captcha and a litany of 3rd party cookies. How about this one:
https://webcache.googleusercontent.com/search?q=cache:yX-xGMeS41QJ:https://www.ft.com/content/a6f50b7c-f78f-469d-b3f2-c6f505edaa9c&hl=en&gl=us
You got a captcha? That sucks. I didn’t.
Both Chrome (with uBlock, even after turning on 3rd party cookies) and Firefox (vanilla, but always set to private browsing) are just in infinite loop of captchas on archive.ph for me - most don’t even result in a photo-square, but even those that do just loop back to the blocked page.
That’s so strange. I don’t see the captcha and I’d never heard anyone mention this before (I’ve been posting archive.ph links for months), but you’re now the second person in the last couple of days to say this.
It appears that it’s a DNS issue, since I use either cloudflare or google as my DNS
From reddit:
The odd bit is that flags anyone going through those DNS lookups by implying that it’s your computer or your corporate network which is infected with malware.
It does look like the DNS is the issue, as I just threw on the VPN - which doesn’t use the local DNS configuration - and it loaded up (after the capcha).