And they don't have to provide DNS services to neo-Nazis.
And they don't have to provide DNS services to neo-Nazis.
Cloudflare rejects IP-only requests. The IP address is 104.20.30.134, but using that in the browser address bar won't work.
curl --verbose --insecure --header "Host:stormfront.org" https://104.20.30.134/forum/
ought to work, but it doesn't. It gets stuck at Cloudflare's NGINX server.It's still available on the Internet Archive.[1] Runs vBulletin, so the posts didn't get archived, just the titles.
Stormfront has been around for decades, getting little traction. It's partly David Duke's site, or was. Now it's just a forum. It's about as nutty as the usual white militia crowd, with which there's some overlap. Compare "vdare.com", which is somewhat white supremacist and pro-Trump. There's a whole spectrum of groups like that.
This was a bad decision by Network Solutions. If registrars start censoring everybody the ADL and the Southern Poverty Law Center don't like, they're going to run head-on into the Trump supporters. That won't end well.
[1] https://web.archive.org/web/20170818020428/stormfront.org/fo...
I agree that it was a bad decision, however I think it's going to be revealed that the decision has more to do with the connections to violence that the forum apparently had, rather than the "speech" content.
Still, they (NS) are going to have to work really hard to convince people that they didn't just make a power grab.
I'm actually surprised it works, because I thought headers need a space after the colon.
Changing the host header to www.stormfrom.org gets me html.
curl --verbose --insecure --header "Host:www.stormfront.org" https://104.20.30.134/forum/
works. So Cloudflare hasn't cut them off. It's just DNS.