3 ms·
What are you trying to secure it against? This is always the first step to think about, also known as "threat assessment" or similar. Are you trying to secure
by chockchocschoir 5y ago
What are you trying to secure it against? This is always the first step to think about, also known as "threat assessment" or similar.
Are you trying to secure it against someone transferring the domains out of your account? Make sure you have all the account security up to date and correct (2FA on the account + the email account that has the ownership), and that all the "transfer locks" are setup (EPP codes and so on)
Are you trying to secure your DNS setup against various DNS attacks? Read up on DNS and various security patterns you can implement like DNSSEC and so on.
You're trying to prevent issues regarding DNS uptime (in case the main domain stops resolving, or other system problems)? In that case, setup DNS over multiple TLDs (and registrars) and have a process for failing over.
In short, it depends on what you're trying to protect against, and who you are trying to protect it against.
- davidkuennen 5y agoMost importantly securing against account termination and being unable to recover that account (like it happens a lot with Google).
- chockchocschoir 5y agoThe only thing that would help you in that case is having an account at another registrar, with a similarly named domain (maybe different TLD, or added word in front of the domain name) that is established as a alternative but rightful domain in case of failure. Test the fail-over process and make sure your documentation describe what domains are legitimate fail-over domains for your users. Also, chose a registrar that won't just terminate your account over nothing (like Google is famous to do). I've had good luck with DNSimple over the years. Sign up for their enterprise plan and make sure to stay up-to-date on their policies. If you see that they start acting "googley", start thinking about moving to another one.