Aside from not being censored at all, thereby enabling visiting sites which are blocked at DNS-level in some locations, there are several options for adblocking at DNS-level, too. Often eliminating the need for a Proxy or VPN to get access, with optional Adblock as a service.
What do you mean why not? The point is just to use anything other than cloudflare for archive.is, and mullvad is not cloudflare, so seems fine, go ahead.
There is no special reason not to use cloudflare dns in general though.
The problem is only between cloudflare and archive.is (and it's aliases) and it's hard to say if either side is wrong, except for the fact that either or both of them could figure out some special exception where they recognize each other's traffic if they cared to. Cloudflare are not censoring archive.is for example, and are not doing anything wrong.
Yes. I know. It's just that I had these problems too, when I used cf. Which I tried for speed, and some 'lawful' censoring reasons. Thereby running into the exact same problem.
Then I tried Mullvad-DNS, the speed was still there, the 'lawful' censoring was gone, the problems with archive-sites ceased to exist, and somewhat configurable adblocking-as-a-service.
It's a seamless 'plugin'-solution, not degrading anything.
https://mullvad.net/en/help/dns-over-https-and-dns-over-tls/
No issues with any archive-sites.
Aside from not being censored at all, thereby enabling visiting sites which are blocked at DNS-level in some locations, there are several options for adblocking at DNS-level, too. Often eliminating the need for a Proxy or VPN to get access, with optional Adblock as a service.
For free.
It's nice.