3 ms·
Change your DNS - Cloudflare doesn't play nice with archive.today - (think, David vs Goliath) 2023:'public-dns' You may also try an archive.today mirror; h
by archo 3y ago
Change your DNS - Cloudflare doesn't play nice with archive.today - (think, David vs Goliath)
2023:'public-dns'
You may also try an archive.today mirror;
https://archive.vn/SlDEe https://archive.vn/SlDEe
https://archive.li/SlDEe https://archive.li/SlDEe
https://archive.md/SlDEe https://archive.md/SlDEe
https://archive.ph/SlDEe https://archive.ph/SlDEe
https://archive.fo/SlDEe https://archive.fo/SlDEe
https://archive.today/SlDEe https://archive.today/SlDEe
However, changing your DNS is the answer to the problem.
- tsimionescu 3y agoHow would my choice of DNS server affect what CAPTCHAs I see on a site served over HTTPS?
- archo 3y agoIf you check my comments, https://news.ycombinator.com/threads?id=archo https://news.ycombinator.com/threads?id=archo You will see I do not have any problem accessing archive.is The Cloudflare vs. Archive.today is a years old problem, thoroughly discuses on HN: And for the record; I use Firefox with uBlock-Origin and Steven Black's hosts file on a Debian flavored Linux. Of course I no longer use Cloudflare DNS
- baq 3y agoCloudflare DNS routing you to cloudflare HTTPS terminator serving you cloudflare CAPTCHAs
- tsimionescu 3y agoSo, is archive.today served exclusively by Cloudflare, optionally by Cloudflare where you can access directly, or has Cloudflare stolen their TLS private keys? Cloudflare can't point me to their own servers when I access https://archive.today https://archive.today unless my browser confirms that the server it's talking to (the one serving the CAPTCHAs) has archive.today's certificate's private keys.
- archo 3y agoTo find many of the threads on the subject, Search; '"cloudflare" vs "archive.is"' site:news.ycombinator.com One of the more current threads; Does Cloudflare’s 1.1.1.1 DNS Block Archive.is? HN Discussion - (210-comments - 2023-08-02) : https://news.ycombinator.com/item?id=36970702 https://news.ycombinator.com/item?id=36970702 However, All our comments regarding DNS have really derailed this thread. (sorry mods)
- tsimionescu 3y agoI did read about that, and it has nothing to do with the problem the OP was raising. If you try to resolve archive.is with 1.1.1.1, you get a bogus IP and don't reach any HTTP server at all. This doesn't explain why some would see a huge amount of CAPTCHA served by archive.is or archive.today if they do reach an IP that serves the right TLS certs, but only if they got that IP from 1.1.1.1 instead of getting it from 8.8.8.8 or wherever.
- archo 3y agoThe information you seek is included in the search and URL(|s) I provided.