Earlier quoted context omitted.
This happens if you use 1.1.1.1 as your DNS resolver, the result of a long-running dispute between Cloudflare and Archive.is[1]; searching HN for “archive cloudflare” will get you lots of discussion. As I understand it: the technical cause is that the Archive.is authoritative DNS server refuses to respond correctly to requests without EDNS subnet information, and Cloudflare’s resolver refuses to send requests with it…
Sooooo the weird thing for me is that I never actually used 1.1.1.1, and it's not in my DNS. archive.today loads correctly in Chrome without a problem so I suspect Firefox is just using 1.1.1.1 over DoH or something.
https://developers.cloudflare.com/1.1.1.1/privacy/cloudflare...
> To counter such threats, Mozilla has partnered with Cloudflare to provide direct DNS resolution from within the Firefox browser using the Cloudflare Resolver for Firefox. What this means is that whenever you select or type a web address in the Firefox browser your DNS lookup request will be sent over a secure channel to the Cloudflare Resolver for Firefox rather than to an unknown DNS resolver, significantly decreasing the odds of any unwanted spying or man in the middle attacks.