3 ms·

> This means we are now just using Cloudflare for DNS. But it's possible to hit this button again and re-enable Cloudflare forwarding temporarily if we find our

> This means we are now just using Cloudflare for DNS. But it's possible to hit this button again and re-enable Cloudflare forwarding temporarily if we find ourselves under attack, so I figure this is a good option. Without this enabled, attackers know what your backend IP address is, so even if you enabled it later, they could continue to DDOS your IP directly, without doing a DNS lookup. You'd only get what you want if you both re-enabled this and switched to different IP addresses.

eloff 6y ago
Also the Cloudflare cookie is clearly for technical purposes, not marketing. So no consent is needed under GDPR, in my understanding. Getting rid of it didn't accomplish anything useful.
- calcifer 6y ago
  > Also the Cloudflare cookie is clearly for technical purposes, not marketing. How do you know that? Because they say so?
  - edoceo 6y ago
    Here's what they say for anyone who's looking https://www.cloudflare.com/en-gb/gdpr/introduction/ https://www.cloudflare.com/en-gb/gdpr/introduction/
mattrick 6y ago
You could firewall off non-Cloudflare requests: https://support.cloudflare.com/hc/en-us/articles/201897700-Allowing-Cloudflare-IP-addresses https://support.cloudflare.com/hc/en-us/articles/201897700-A...
- Okx 6y ago
  A software firewall is useless against a DDoS attack. It will only serve to help your IP not get discovered in the first place.