|
| ▲ | zamadatix 2 days ago | parent | next [-] |
| Sorry if I wasn't clear, when reading Taggart's post and subsequent chained comments and didn't see any explanation of what Cloudflare's involvement was. Am I missing something on how to see more of the original post perhaps? As a sanity check I did a ctrl+f on "hosts" on the page and didn't get a match but I suppose that wouldn't help if I'm not in the right place to see the rest of the content. |
|
| ▲ | gruez 2 days ago | parent | prev [-] |
| >cloudflare hosts the attackers. No, they provide DDoS protection, but the actual servers are likely hosted on some random VPS somewhere. |
| |
| ▲ | zamadatix 2 days ago | parent [-] | | When I do a lookup on beamed.st I get an IP in 2606:4700::/32 which is currently advertised from AS13335 "Cloudflare, Inc." Edit: I now realize gruez meant the beamed.st site itself is behind Cloudflare DDoS, completing the loop to explaining what Cloudflare's involvement was :). | | |
| ▲ | two_handfuls 2 days ago | parent [-] | | Yes that looks the same whether they provide DDoS protection or host. | | |
| ▲ | zamadatix 2 days ago | parent [-] | | Ahhh, I completely misread who the DDoS protection was being provided to. Must be a slow day for me :). Thanks! |
|
|
|
