For years, archive.is has famously [0] not loaded when using Cloudflare DNS servers, due to refusal by Cloudflare to send the last /24 of the client’s subnet to the upstream resolver, which insisted on it for eDNS.

But recently I’ve been able to use the site even while browsing via Cloudflare WARP.

Either my DNS is misconfigured (leaking) or the issue is resolved. Does anyone know the details? Did archive.is back down on their eDNS requirements, or did Cloudflare start sending the client subnet?

[0] https://en.wikipedia.org/wiki/Archive.today#Cloudflare_DNS_availability