1
thebonaldwin 1 point ago +1 / -0

I don't think even that's the case. The non-cloudflare IP can just cancel direct requests.

4
thebonaldwin 4 points ago +4 / -0

It doesn't matter. The furry found nothing interesting. If Cloudflare doesn't deny service, no reason the ISP would. Even if it did, it takes seconds to move back up to another VPS provider.

1
thebonaldwin 1 point ago +1 / -0

If Cloudflare isn't going to deny service, then why would the ISP? Even if they do, it would take no time for them to move to another hosting provider.

Edit: you're the retard who made the blog post, aren't you? I own multiple virtual private servers. I wouldn't give a shit if you knew their IPs because I have backups for all of them and can easily transfer the software to a different VPS from another provider. Try again, furry.

2
thebonaldwin 2 points ago +2 / -0

Just connect to https://104.26.8.222. Not exactly a secret TDW uses cloudflare. When traffic to TDW is high, you often get the Cloudflare DDOS protection browser check or Cloudflare captcha. Just a retarded furry who thinks it's talented.

4
thebonaldwin 4 points ago +5 / -1

These are more TDW IPs.

104.26.8.222 172.67.73.6

I thought it was impossible to hide this info? A website's servers' IP addresses are public knowledge. Can someone explain what I'm missing here?