Jake Jarvis

archive.is is not the best choice for cloudflare users. If you are using cloudflare then archive.is links does not work anyway :D https://jarv.is/notes/cloudflare-dns-archive-is-blocked/

Thanks. As a non-expert, I found the blog post a bit easier to follow: https://jarv.is/notes/cloudflare-dns-archive-is-blocked/

Great overview. If anyone's interested, I wrote a guide a while ago on adding these headers via Cloudflare Workers, which can be helpful if you're hosting a static site on S3, GitHub Pages, etc. where you can't add these headers directly: https://jarv.is/notes/security-headers-cloudflare-workers/

Sort of: https://jarv.is/notes/cloudflare-dns-archive-is-blocked

There is a long-standing conflict between archive and cloudflare https://jarv.is/notes/cloudflare-dns-archive-is-blocked

Do you use Cloudflare DNS (1.1.1.1)? https://jarv.is/notes/cloudflare-dns-archive-is-blocked

I will say that today, for the first time in a long time, I seem to be able to click this link and actually get the page to load... But it has been an issue for a long time. But, as an explanation: https://jarv.is/notes/cloudflare-dns-archive-is-blocked/ > ... Archive.is’s owner is actively refusing to resolve their own website for 1.1.1.1 users because Cloudflare’s DNS offers too much privacy.

Add an entry for it in /etc/hosts https://jarv.is/notes/cloudflare-dns-archive-is-blocked/ TL;DR Operator of archive.is blocks DNS requests from providers who don't pass ECS information to them resulting in issues like the redirect loop.

https://archive.is/ is serving a fake captcha page. Cloudflare hasn't used Google Captcha in years, they have their own in-house captcha https://www.cloudflare.com/en-gb/products/turnstile/ "Archive.is’s owner is intentionally blocking 1.1.1.1 users." https://jarv.is/notes/cloudflare-dns-archive-is-blocked/ edit: sorry, to answer your question: I see the same

This happens if you're using Cloudflare DNS: https://jarv.is/notes/cloudflare-dns-archive-is-blocked/ (Sounds like iCloud private relay may do the same for the same reasons).

No. The archive.is folks intentionally poison dns results for certain resolvers. They have a vendetta against cloudflare for not giving location data to them for dns lookups. https://jarv.is/notes/cloudflare-dns-archive-is-blocked/

Archive.is owner blocks Cloudflare DNS because Cloudflare doesn't leak private information. https://jarv.is/notes/cloudflare-dns-archive-is-blocked/

If you’re using Cloudflare DNS (1.1.1.1) that’ll be why: https://jarv.is/notes/cloudflare-dns-archive-is-blocked/

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 refuses to send requests with it. (Cloudflare says this is for privacy reasons, and I believe Archive.is says their response is for legal reasons.) The captcha loop seems to be a recent development; apparently[2] it’s not actually from Cloudflare, just styled to look like it. [1] https://jarv.is/notes/cloudflare-dns-archive-is-blocked/ [2] https://news.ycombinator.com/item?id=38174302

Are you using cloudflare's DNS? https://jarv.is/notes/cloudflare-dns-archive-is-blocked/

Are you using Cloudflare's DNS? Archive.is purposefully gives bad results to Cloudflare's DNS resolvers as they do not respect and pass along EDNS subnet information which Archive wants to run their own CDN. https://jarv.is/notes/cloudflare-dns-archive-is-blocked/

Cloudflare DNS stopped resolving Archive Today (.is) a few weeks ago. Probably related to this disagreement from 2019. https://jarv.is/notes/cloudflare-dns-archive-is-blocked/

It may be DNS, the operator of the archive.today sites intentionally blocks certain DNS providers: https://jarv.is/notes/cloudflare-dns-archive-is-blocked/

It's a long story! https://jarv.is/notes/cloudflare-dns-archive-is-blocked/ In short if you use Cloudflare's 1.1.1.1 DNS then some archive.is domains won't load so you should perhaps use another DNS server.

Correct - archive.is doesn't like not getting EDNS from Cloudflare (https://jarv.is/notes/cloudflare-dns-archive-is-blocked/), so Cloudflare sends you to 1.1.1.7 to indicate a problem.

Archive.is requests EDNS information about the subnet that your system is on. Cloudflare doesn't pass this information along since it can be used to determine your location in part. So when archive.is doesn't get the subnet info, it sends bogus dns results back and you get that error. See https://jarv.is/notes/cloudflare-dns-archive-is-blocked/ for all the details.

If you're using Cloudflare DNS, archive.is etc will fail to resolve. https://jarv.is/notes/cloudflare-dns-archive-is-blocked/

Cloudflare doesn't block them, Archive.is intentionally refuses to resolve DNS queries from 1.1.1.1 due to lack of geo information. See explanation here: https://jarv.is/notes/cloudflare-dns-archive-is-blocked/

I would guess that it's not intentional based on what I know about the relationship between archive.is and Cloudflare's DNS. 1. https://jarv.is/notes/cloudflare-dns-archive-is-blocked/

> I don't particularly care what the details are, whose fault it is, etc. https://jarv.is/notes/cloudflare-dns-archive-is-blocked/

Are you using Cloudflare DNS? https://jarv.is/notes/cloudflare-dns-archive-is-blocked/

Sounds about right given Archive.is has this feud going on with Cloudflare. https://jarv.is/notes/cloudflare-dns-archive-is-blocked/

> DNS resolution error. archive.is has a beef with some DNS resolvers: https://jarv.is/notes/cloudflare-dns-archive-is-blocked/

It's some feud between the 1.1.1.1 operators and the archive.is operator. I never really cared enough to figure out who was at fault. Probably both of them. edit; here you go: https://jarv.is/notes/cloudflare-dns-archive-is-blocked/

Archive.is is also not available for users with 1.1.1.1 (Cloudflare DNS): https://jarv.is/notes/cloudflare-dns-archive-is-blocked/ Long shot: those two are related. But hijacking requests like that is a big no-no.