5 ms·
Same for me. I do get an DNS_PROBE_FINISHED_NXDOMAIN in Chrome, but other archive domains like https://archive.vn/f7HSw https://archive.vn/f7HSw works.
by runarb 6y ago
Same for me. I do get an DNS_PROBE_FINISHED_NXDOMAIN in Chrome, but other archive domains like https://archive.vn/f7HSw https://archive.vn/f7HSw works.
- driverdan 6y agoTheir domain doesn't work with Cloudflare DNS because they use non-standard records.
- runarb 6y agoI use Googles dns 8.8.8.8, so this must be something else.
- driverdan 6y agoGoogle may have issues too, I don't know. It's a DNS problem that has existed for a while.
- dylz 6y agoThey don't use non-standard records; if your resolver protects your privacy by not sending them your IP, they will intentionally return bad records specifically to fuck with you.
- thatlongthrow1 6y agoThis is the correct comment, they purposefully block Cloudflare traffic due to them not forwarding user data. They stated they need it to stay in line with the law but they can do that with things like the user's IP. To go that far to insist on getting a specific type of user data is sketchy.
- dylz 6y agoThey do quite a bit worse on top of that, ctrl-f pixel.archive.is in view source when you visit any archived page.
- chihuahua 6y agoIt's odd that every other website I've ever tried works with Cloudflare, but not archive.is. Does anyone have an idea what's so special about them?
- dylz 6y agoarchive.is _intentionally_ is blocking Cloudflare for not letting them track users. See https://news.ycombinator.com/item?id=21308564 https://news.ycombinator.com/item?id=21308564 and https://news.ycombinator.com/item?id=23316085 https://news.ycombinator.com/item?id=23316085
- deleted 6y ago[deleted]