Ask HN: Archive.is Captcha Problems Lately? 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 |
Seems like an OTT security config.
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.
DNS is the unsecured quad9 9.9.9.10
Secure DNS is likewise https://dns10.quad9.net/dns-query
Console shows error 429
Assholes.
Firefox ETP strict, CenturyLink residential
Google DNS and others work where Cloudflare does not.
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} <<<";
host -t A $u 1.1.1.1;
host -t A $u 8.8.8.8;
done
>>> archive.ph <<<
Using domain server:
Name: 1.1.1.1
Address: 1.1.1.1#53
Aliases:
archive.ph has address 192.210.214.166
Using domain server:
Name: 8.8.8.8
Address: 8.8.8.8#53
Aliases:
archive.ph has address 23.137.248.133
>>> archive.is <<<
Using domain server:
Name: 1.1.1.1
Address: 1.1.1.1#53
Aliases:
archive.is has address 198.23.187.186
Using domain server:
Name: 8.8.8.8
Address: 8.8.8.8#53
Aliases:
archive.is has address 23.137.248.133
>>> archive.li <<<
Using domain server:
Name: 1.1.1.1
Address: 1.1.1.1#53
Aliases:
archive.li has address 192.210.214.166
Using domain server:
Name: 8.8.8.8
Address: 8.8.8.8#53
Aliases:
archive.li has address 23.137.248.133
>>> archive.vn <<<
Using domain server:
Name: 1.1.1.1
Address: 1.1.1.1#53
Aliases:
archive.vn has address 192.210.214.166
Using domain server:
Name: 8.8.8.8
Address: 8.8.8.8#53
Aliases:
archive.vn has address 23.137.248.133
>>> archive.fo <<<
Using domain server:
Name: 1.1.1.1
Address: 1.1.1.1#53
Aliases:
archive.fo has address 192.210.214.166
Using domain server:
Name: 8.8.8.8
Address: 8.8.8.8#53
Aliases:
archive.fo has address 23.137.248.133
>>> archive.md <<<
Using domain server:
Name: 1.1.1.1
Address: 1.1.1.1#53
Aliases:
archive.md has address 192.210.214.166
Using domain server:
Name: 8.8.8.8
Address: 8.8.8.8#53
Aliases:
archive.md has address 23.137.248.133
I'd suggest you kick your "integrity of DNS" principle in the interest of "rough consensus, working code". And yes, you can do that without passing on user-specific EDNS to AT, who're quite likely to obtain just that information through the subsequent HTTP GET request in any event.