Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

In order to reduce risk I really wouldn't recommend running any service that hosts any user content on the same domain and TLD you host your personal stuff.


I've sometimes wondered if it would be worth getting something like 4e4eee247a69fab841ec36eabc95eee9.com [1] and only using it for email hosting to host my contact emails and for my other services.

The idea is:

1. By having no other services on it that minimizes the chances that it could get hacked and used for nefarious purposes that might get it seized by law enforcement.

2. By using a meaningless name like 4e4eee247a69fab841ec36eabc95eee9 there is no chance someone will come along with a trademark claim or an accusation that I'm squatting on a name that they have a better claim to.

[1] dd if=/dev/urandom bs=1 count=16 | xxd -g 16


I have a domain name like that, I primarily break login forms with it but that was the initial idea, yes.


If it's just for a non public contact for a domain registrar and/or strictly similar functions I personally believe so.


Same domain I get but a new TLD? I like to keep stuff in '.com'


The point was to avoid having all your eggs in one basket, basket being a jurisdiction in this case.


I think "domain and TLD" is a single clause in that sentence.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: