He datamines the connections and sells it. When he can't datamine it (making the data worthless) he throws up a google captcha that can't be solved. https://jarv.is/notes/cloudflare-dns-archive-is-blocked/ >In other words, Archive.is’s nameservers throw a hissy fit and return a bogus IP when Cloudflare doesn’t leak your geolocation info to them via the optional EDNS client subnet feature. The owner of Archive.is has plainly admitted this with a questionable claim (in my opinion) about the lack of EDNS information causing him “so many troubles.” >He’s even gone as far as replying to support requests by telling people to switch to Google’s DNS, which — surprise! — offers your location to nameservers with pleasure. >I wrote the following reply to Matthew, praising his team’s focus on the big picture: > >Honestly, Cloudflare choosing not to hastily slap a band-aid on a problem like this just makes me feel more compelled to continue using 1.1.1.1. > >I hesitate to compare this to Apple calling themselves “courageous” when removing the headphone jack, but in this case, I think the word is appropriate. I’ll happily stand behind you guys if you take some PR hits while forcing the rest of the industry to make DNS safer — since it is understandable, admittedly, for users to conclude that “Cloudflare is blocking websites, sound the alarms!” at first glance. >Sure, it’s annoying that I’ll need to use a VPN or change my DNS resolvers to use a pretty slick (and otherwise convenient) website archiver. But I’m more happy to see that Cloudflare is playing the privacy long-game, even at the risk of their users concluding that they’re blocking websites accessible to everyone else on the internet.