It may be useful, as DNS poisoning/corruption could make the internet seem to be down.
And I don't see any risk with distributing the IP address greatawakening resolves to. Anybody can see the ip address if they run 'nslookup greatawakening.win' in a command prompt.
Hmmm... http://[2606:4700:3034::6815:4790]/ returns a Cloudflare whine that direct IP access is denied. HTTPS for same whines about an unsupported SSL protocol (with Brave)...
GET /pub/WWW/TheProject.html HTTP/1.1
Host: www.w3.org
...
In your case, the request contains an IP address for the host specifier.
GET /whatever HTTP/1.1
Host: a.b.c.d
So if CloudFlare is blocking any request with an IP address for Host instead of domain name, then that might make all cloudflare sites unusable in the event of DNS poisoning since they would resolve the hostname to the wrong IP.
It may be useful, as DNS poisoning/corruption could make the internet seem to be down.
And I don't see any risk with distributing the IP address greatawakening resolves to. Anybody can see the ip address if they run 'nslookup greatawakening.win' in a command prompt.
It could be useful to make note of them just in case.
Hmmm... http://[2606:4700:3034::6815:4790]/ returns a Cloudflare whine that direct IP access is denied. HTTPS for same whines about an unsupported SSL protocol (with Brave)...
(And yes, I have a public IPV6 setup)
Maybe a workaround exists, if the Host header could be modified manually or would that simply result in the poisoned dns ip being returned...
Found this: https://serverfault.com/questions/1008522/what-enables-cloudflare-to-disable-direct-ip-address-access
So if CloudFlare is blocking any request with an IP address for Host instead of domain name, then that might make all cloudflare sites unusable in the event of DNS poisoning since they would resolve the hostname to the wrong IP.