Live data from Hacker News

Ask HN: Archive.is Captcha Problems Lately?

news.ycombinator.com

1–10 of 21 posts

Ask HN: Archive.is Captcha Problems Lately?

#1
Anyone else having problems lately with archive.is taking you to a captcha, you solve it and then it just keeps redirecting you back to the captcha over and over. Happens to me in chromium, a friend just tried in firefox and had same problem.

Today is happening to me on a link from another thread which was to https://archive.is/gwuFp

Re: Ask HN: Archive.is Captcha Problems Lately?

#6
In case anyone comes back to this. I noticed I get redirected to the archive.is domain and that's when I wind up in a captcha loop.

When I get captcha'd, the archive.is resolves to 198.23.187.186

I cleared my DNS server cache and got new IPs for archive.today and archive.ph but the same address for archive.is. I tried the OPs link, got redirected to .is and got captchas.

I cleared DNS server cache again and got 89.253.237.217 for .is (along with more new IPs for .ph and .today). No captchas.

Re: Ask HN: Archive.is Captcha Problems Lately?

#8
post #7

Captcha loop here as well. Both from FF and an ungoogled Chromium with no add ons that I keep just for these situations. DNS is the unsecured quad9 9.9.9.10 Secure DNS is likewise https://dns10.quad9.net/dns-query Console shows error 429

And sure enough, if I disable secure DNS and change the DNS server to my ISP's, it works.

Assholes.

Re: Ask HN: Archive.is Captcha Problems Lately?

#9
post #5

Check your DNS, there are issues using Cloudflare to reach archive.{is | li | today | etc } Google DNS and others work where Cloudflare does not.

Interesting ...

Using Cloudflare (1.1.1.1) vs. Google (8.8.8.8) I get different IP resolution:

  for u in archive.ph archive.is archive.li archive.vn archive.fo archive.md;
  do
      echo ">>> ${u} 
Results:

  >>> archive.ph >> archive.is >> archive.li >> archive.vn >> archive.fo >> archive.md 
Cloudflare: Fix your shit.

Re: Ask HN: Archive.is Captcha Problems Lately?

#10
post #5

Check your DNS, there are issues using Cloudflare to reach archive.{is | li | today | etc } Google DNS and others work where Cloudflare does not.

Interesting ... Using Cloudflare (1.1.1.1) vs. Google (8.8.8.8) I get different IP resolution: for u in archive.ph archive.is archive.li archive.vn archive.fo archive.md; do echo ">>> ${u} Results: >>> archive.ph >> archive.is >> archive.li >> archive.vn >> archive.fo >> archive.md Cloudflare: Fix your shit.

Nothing to fix. We are responding with what archive.* sends to us. They choose to send us incorrect data.

See: https://news.ycombinator.com/item?id=19828702

Post reply on HN