5 ms·
We actually didn't talk about WHOIS Privacy because it's becoming less and less of a relevant feature in the post-GDPR world. We do support it, free of charge.
by zackbloom 8y ago
We actually didn't talk about WHOIS Privacy because it's becoming less and less of a relevant feature in the post-GDPR world. We do support it, free of charge.
Cloudflare is also the largest authoritative DNS deployment in the world, and changes propagate in closer to 15 seconds than 15 minutes.
- nickjj 8y agoThanks for the confirmation. Sounds promising. Do you happen to also offer free email forwarding with registered domains?
- zackbloom 8y agoI don't have the answer to that yet. On the one hand it's a bit far afield of what we normally do. On the other a lot of people seem to get it from their registrar and rely on it. The ideal situation would be if we could find a way to do email forwarding which wasn't just as good as what they do, but was exciting and meaningful. We'll keep thinking about it and let you know on our blog.
- nickjj 8y agoIf you want to blow everyone away then I think you should start with giving free real inboxes for everyone (maybe with some sane limit, or a way to pay per month to increase it), and then introduce email forwarding in the future (because I'm sure some people will still want that feature even with real inboxes available). If you GA'd with: ~$8 .com addresses, N real inboxes, free whois guard and a top notch DNS record API. That's a compelling offer and I'd very likely switch from namesilo if that were the case. To be honest, anything less and I'd stay with namesilo because the 15 minute timer can be worked around by using my web host's name servers (digitalocean pushes updates in a few seconds). I couldn't live without either email forwarding or a real inbox.
- zackbloom 8y agoWhen you say real inboxes, are you thinking webmail of some sort? Don't most people prefer to use Google Apps or the like these days?
- JonKF 8y agoMost places and projects I've worked in the past 10 years or so have used GSuite or similar for inboxes, and Amazon SES or similar for programatically sending email. Those that didn't (shared-hosted websites on CPanel installations seemingly do still exist in 2018) had access to webmail in the hosting panel or as an installable application.
- nickjj 8y agoYeah right now I use email forwarding and SES to send emails (which required setting up an address that belongs to my domain, such as user@exampledomain.com). In this case I forwarded that email to my gmail account and it all works, but it's not perfect. In either case, having at least email forwarding or an inbox is essential for a lot of common things you'd want to do on a domain. Forwarding works ok to avoid $60 / year for Google's offerings but has some limitations. This is coming at it from the POV of just setting up a VPS to host some sites and wanting to accept email from your domain name without paying any more than what the domain cost to register. I think this use case is super common, especially on HN. No one thought Let's Encrypt would step up and offer a top tier free SSL solution. If it can be done for SSL, it can be done for real inboxes. :)
- nickjj 8y agoI 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.
- 8y ago
- WordSkill 8y agoZack, please DON'T waste time on email, focus on security. The category of customer who consider the flaky email solutions provided by registrars to be worth using, and who are unaware of how to hook their domains up to free forwarding at services such as Mailgun, are unlikely to ever buy your higher-margin services. Your introduction of at-cost domain registration will already blow everyone away, you do not need email for that, but high-value domain owners will worry that the service will not be sufficiently-resourced to protect their domains. Those are precisely the domain owners you want because they are more likely to end up paying for your other services. So, try to finally get U2F support in place before you spread your legs for mass domain registration. Real, proper U2F support that encourages users to associate TWO different hardware tokens with their account will save you from the tsunami of domain jacking attempts you are about to experience. The point of having two different hardware tokens, kept in separate locations, is that it becomes far more unlikely that your support will ever have to deal with them. As long as they can continue to access their account with one, they will have time to buy and associate a replacement. Meanwhile, any hacker attempting to socially engineer your support would be left with the tough job of having to explain how they managed to lose both tokens at the same time - they won't bother, they will move on to some other registrar that is too dumb to implement U2F. You save your staff a world of hassle, you protect your reputation from a potential PR nightmare, and the high-value domain owners will be more than happy to bear the $95 cost of two Yubikeys. You just have to make it possible and gently encourage users in that direction.
- deleted 8y ago[deleted]
- silverwind 8y agoStill got to factor in the minimum allowed TTL of 120 seconds, thought. I wish the API would allow less.
- haboutnnah 8y agoSorry to bother you, but do you offer changing nameservers after registration?