Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Introducing Cloudflare Registrar

blog.cloudflare.com

Post reply on HN
Print view View original

41–50 of 257 posts

Re: Introducing Cloudflare Registrar

#41

Post by rk249 »

ksec wrote: post #24

I wouldn't have cared much about Domain Name Register just a week ago, but after what happen at Zoho, and all the horror story in the comments section from namecheap and others, Cloudflare Registar couldn't come at a better time. I really wish Cloudflare at least made $1 or $2 Gross Profits per domain. Who paids for Domain Register Support? I would much rather be a "customer" than I am not sure where they are making…

I though namecheap was one of the better ones around? I'm looking for a domain registrar. Could share the link with namecheap horror stories? Thanks

Re: Introducing Cloudflare Registrar

#42

Post by nickjj »

x13 wrote: post #39
nickjj wrote: post #22

Earlier quoted context omitted.

I mean being able to set up zackbloom@cloudflare.com as a proper inbox that can send and receive mail without forwarding to another email. Having a web interface for it would be cool but I think a lot of people could also configure existing email clients to access it (at least at the start). Google Suite is something like $5 / month per domain name so offering that as a free feature would be a pretty big deal.

Google Suite starts at $5 per email address per month; I think asking for free email accounts is beyond the product offering of domain registration/renewal. And they probably want to reserve usage of their domain for email so you know it's a staff member you're dealing with, which is why google gives away gmail.com addresses, not google.com addresses. Here are three less expensive email options for you: 1. get a VM a…

To be fair he was asking for exciting and meaningful ways to make it better.

> And they probably want to reserve usage of their domain for email so you know it's a staff member you're dealing with, which is why google gives away gmail.com addresses, not google.com addresses.

These inboxes would be for your custom domain that you registered, not @cloudflare.com for everyone. I used that for his because it sounds like he works there.

Yours would be x13@whateverdomainyouregistered.com.

Re: Introducing Cloudflare Registrar

#43

Post by [deleted] »

zackbloom wrote: post #17
johnklos wrote: post #14

While Cloudflare appears to be doing things that are meant to help everyday people, I can't help but be suspicious. This is an organization that sticks with the "we don't host" bullshit line when web sites serve up Trojans which pretend to be Adobe Flash installers. While there's more subjectivity involved with dealing with hosting the content of spammers, there is zero subjectivity involved with clear and obvious ph…

I appreciate that these decisions can seem easy, but broadly do you want a private company deciding what can be on the internet, or do you want that decision made by a judge with due process?

[deleted]

Re: Introducing Cloudflare Registrar

#45

Post by SamWhited »

judge2020 wrote: post #28
johnklos wrote: post #14

While Cloudflare appears to be doing things that are meant to help everyday people, I can't help but be suspicious. This is an organization that sticks with the "we don't host" bullshit line when web sites serve up Trojans which pretend to be Adobe Flash installers. While there's more subjectivity involved with dealing with hosting the content of spammers, there is zero subjectivity involved with clear and obvious ph…

So if Google accidentally caches random JS malware, they suddenly become at fault for "hosting" it?

If someone points it out and they refuse to remove it and infect people who don't know better and trust Google, then the answer is "yes".

Re: Introducing Cloudflare Registrar

#46

Post by daxorid »

zackbloom wrote: post #17
johnklos wrote: post #14

While Cloudflare appears to be doing things that are meant to help everyday people, I can't help but be suspicious. This is an organization that sticks with the "we don't host" bullshit line when web sites serve up Trojans which pretend to be Adobe Flash installers. While there's more subjectivity involved with dealing with hosting the content of spammers, there is zero subjectivity involved with clear and obvious ph…

I appreciate that these decisions can seem easy, but broadly do you want a private company deciding what can be on the internet, or do you want that decision made by a judge with due process?

Matt Prince already decided "what can be on the internet" when he banned Daily Stormer. As far as Cloudflare is concerned, that ship already sailed.

Re: Introducing Cloudflare Registrar

#49

Post by kodablah »

johnklos wrote: post #14

While Cloudflare appears to be doing things that are meant to help everyday people, I can't help but be suspicious. This is an organization that sticks with the "we don't host" bullshit line when web sites serve up Trojans which pretend to be Adobe Flash installers. While there's more subjectivity involved with dealing with hosting the content of spammers, there is zero subjectivity involved with clear and obvious ph…

On the contrary, decisions by not-my-actual-server-host to get involved in content disputes is what would drive me away as a customer. What having the tiniest modicum of common sense would tell you is that holding each middleman responsible for content they pass through is ridiculous. It is definitely a way to enforce a level of censorship that didn't work when you went to the true source of the data. Hosting someone's DNS, passing their data over your pipes, building the keyboard they type with, registering their domain, etc is not the same as supporting the content. I think you're intentionally confusing the issue by equating hosting one type of service with another.

Re: Introducing Cloudflare Registrar

#50

Post by zackbloom »

c487bd62 wrote: post #23

Awesome! I hope you don't mind me ranting a bit about custom domains > Custom Domain Protection for Cloudflare Registrar, available on the Enterprise Plan, protects your organization from domain hijacking with exclusively out-of-band verification of any changes to your Registrar account. This is what keeps me locked into Google and other services. I just can't trust my custom domain, if I'm targeted by any semi compe…

I'm sorry to hear that, it sounds horrible. We had a very similar situation several years ago which led to the development of our original Registrar.

All I can tell you is the 'custom' in Custom Domains refers to the idea that you can set whatever security policy you would like. That includes restricting who can change your domain to a list of people you can count on one hand who each have a personal relationship with you. If you want a policy which requires a photo of you with today's newspaper in it to change a domain, that's probably something which can be arranged.

Just to clarify for readers, this is the Custom Domain plan, which is the Enterprise version of the Registrar we are launching today.

Post reply on HN