-
-
Notifications
You must be signed in to change notification settings - Fork 384
✨ Feature Suggestion | Domain Registrar #1996
Comments
I am not sure how the domain registration rules work in the GDPR era, but for Gandi it used to depend on the TLD rules. I don't know what I think about this issue, but GDPR may have made the private domain registration services obsolete (excluding those that own the domain for you such as Njalla). |
There was a reddit discussion about this a while ago. Personally, I've used njal.la and had no issues, though I've heard Porkbun is good (they offer free whois privacy protection) along with Namecheap (who now 'power ThinkPrivacy'). As of now, I don't think this is worth its own category, seeing as njal.la is the only real privacy focused option and it is already listed under hosting providers... |
Tbh I wouldn't really recommend Gandi after seeing some of their amazing https://i.imgur.com/s3R1VVc.png And prices are not amazing, you can get the same ¯\_(ツ)_/¯ |
Njalla is not GDPR compliant. That's suspicious. |
I would not recommend domaindiscount24. |
I was a bit surprised that there wasn't (as far as I could tell) a domain registrar recommendation. Maybe there is a reason for this such as the fact that there aren't that many privacy implications if you harden your WHOIS info or the suggestion might just be to use a registrar proxy service, etc. However, since there is a section for hosting, I thought it might be nice to at least have a nod to the registration process, especially because some might want to self-host.
I haven't done a ton of research on this myself (clearly), but I thought I would open the issue to brainstorm.
From this topic, I see some others as well:
From this topic, I see the following:
I also see quite a few suggestions about non-clearnet hosting (esp. for static websites). Maybe the whole hosting section could be redone with an eye towards integrating options from some self-contained networks as well and maybe domain registration as a subsection.
The text was updated successfully, but these errors were encountered: