Comment by codetrotter

This makes a lot of sense, and this comment should be higher.

The other comments that only present the Cloudflare side of the situation make it sound like the archive.is owner was being unreasonable, but as we see there is more to it!

I personally tried to use 1.1.1.1 as my resolver a couple of years ago but I use archive.is a lot.

Regardless of who is “at fault”, not being able to access archive.is is a dealbreaker for me so I quickly stopped using 1.1.1.1

But Cloudflare has a lot of other things that work well for me.