Live data from Hacker News

Is Something Going on with Archive.ph?

news.ycombinator.com

1–10 of 21 posts

Re: Is Something Going on with Archive.ph?

#2
Are you by chance using Cloudflare for DNS? If so that would be the answer. Archive.is gives CF their own IP's back to them rather than the correct DNS answer on purpose. Some people will get endless captchas and some will get errors.

Re: Is Something Going on with Archive.ph?

#4

'One more step. Please complete the security check to access' Except I have JS disabled and can't complete the CAPTCHA interstitial.

That is what one would see if using Cloudflare DNS. It's cloudflare's captcha but archive.is is not on of their customers so it will just be a never-ending captcha.

Re: Is Something Going on with Archive.ph?

#8
post #6

I switched Archive domains from Cloudflare DNS to Mullvad DNS on my unbound, haven’t had issues since. I also would recommend quad9 as a dns resolver, it doesn’t have an issue.

I think Archive doesn’t work with Apple’s private relay browsing feature due to them using Cloudflare for that capability, although I have not had time to test. Absolutely know it doesn’t work when using Cloudflare public DNS servers though.

Re: Is Something Going on with Archive.ph?

#9
It resolves for me but shows a captcha loop as others said, strangely the captcha page I'm getting seems to be some mockup of the Cloudflare one, using reCAPTCHA which Cloudflare publicly spoke about switching from.

Seems to be doing something odd, code of the page includes some XmlHttpRequest to a blog site with randomized query string (see end of https://pastebin.com/W21Au8RK), along with some fingerprint library (though commented out)

That blog site loads very slow for me if I go there manually - maybe some kind of DoS being directed to it?

Seen this same faux-cloudflare page used on btdig.com too, with the same strange XmlHttpRequest & fingerprint code, pretty weird.

Re: Is Something Going on with Archive.ph?

#10

'One more step. Please complete the security check to access' Except I have JS disabled and can't complete the CAPTCHA interstitial.

That is what one would see if using Cloudflare DNS. It's cloudflare's captcha but archive.is is not on of their customers so it will just be a never-ending captcha.

Why would cloudflare DNS work that way? Why don't they cache the authoritative DNS server?
Post reply on HN