DNS error page throws no-cypher-overlap error

It is known that currently trying to resolve archive.is via 1.1.1.1 throws a DNS resolver error.

image

And now even the error page cannot be accessed when using HTTPS because of TLS error:

image

So the problem seems to be that archive.is isn’t supposed to use a Cloudflare name server, but that domain must have been set up at Cloudflare at some point. Other resolvers get the correct IP address.

Now the trick is to find out if Cloudflare can stop locally resolving that domain. @cs-cf?

They’ve intentionally poisoned their DNS response.

1 Like

They’ve intentionally poisoned their DNS response.

They seem so, but my point here is the cypher error shouldn’t happen. I should still be able to see the Error 1016 page.

We don’t host archive.is and have no SSL certificate for them, so I wouldn’t expect to be able to see it.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.