News for hackers. Stuff that matters.

A comment on Cloudflare doesn’t have to cut off copyright-infringing websites, judge rules. Parent comment

Re:Cloudflare doesn’t have to cut off copyright-infringing w... by Abishek_Muthian on Friday October 08, 2021 @02:34AM (#28796351)
> we can't see who registered the domain or who hosts the site (since Cloudflare masks the IPs.)

TIL Cloudflare is also a registrar[1], Might be even the cheapest. I was wondering why the parent wasn't able to find who the site belonged to through just WHOIS and sending a abuse request to the registrar, Still Cloudflare should be forwarding the abuse report not sure what's the case here.

Can anyone tell share their experience with Cloudflare registrar? When compared to something like Namecheap? Also can different Cloudflare accounts for separate products use same credit cards for using the registration service?

[1] https://www.cloudflare.com/products/registrar/

[ Parent | on HN ]
Re:Cloudflare doesn’t have to cut off copyright-infringing w... by fragmede on Friday October 08, 2021 @03:31AM (#28796638)
In particular, the cloudflare registrar forces you to use their nameservers, which is totally fine if you understand the ramifications going in.
[ Parent | on HN ]
Re:Cloudflare doesn’t have to cut off copyright-infringing w... by Abishek_Muthian on Friday October 08, 2021 @06:06AM (#28797495)
That's a good point. I guess those who already have cloudflare nameservers wouldn't have an issue with it unless there are some issues with transferring the domain to cloudflare which already acts as your reverse proxy.
[ Parent | on HN ]