Web Hosting Talk : Web Hosting Main Forums : Domain Names : Safest place to register?

[avocado]

What would you consider the safest place to register a domain name and know that it will be secure there? (price doesn't matter.)

[Fulk]

I would say Moniker, but do some search before you decide.

[Stan Marsh]

I second Fulk. Moniker is known for being the most secure registrar.

[onefortruth]

Go Daddy is quite secure.

You need a code just to talk to customer service..or a credit card number that's on file. They don't hand out info like candy and I'm willing to bet the transfer theft is low...their transfer feature requires much confirmation.

[Stan Marsh]

Originally Posted by onefortruth

Go Daddy is quite secure.

I think this post is a joke.

GD can suspend your domain for a single spam complaint. Enough said?

[KGIII]

I'm pretty fond of Namecheap actually. I've never had a problem with them at all. I'm not sure if, well, they're actually an official registrar or not now? Either way the process is pretty easy and I've never had any issues with them.

KGIII

[avocado]

Thanks for the responses, everyone.

about Moniker: is there anything in particular that makes it more secure than other registrars?

[twhiting9275]

GoDaddy is secure allright, in fact, they're so secure they won't even inform you that your account is locked after 3 (yes, only 3) password failures. Seems like something's wrong there.

As far as them locking domains, it's possible they do this, I haven't (personally) witnessed it, but it's entirely possible that they do this. If the domain is a known issue, then , what, they should just leave it alone and continue to allow the user to spam from it?

[Stan Marsh]

Originally Posted by linux-tech

If the domain is a known issue, then , what, they should just leave it alone and continue to allow the user to spam from it?

As the (supposingly) specialist in Linux and networks, you MUST be aware that it's NOT domains that are spamming (the first ones to close then must be yahoo and hotmail). And it is NOT registrars that should fight spam.

[twhiting9275]

it is NOT registrars that should fight spam.

Spam is just one example of the crazy nastyness that can come from a domain, and yes, in the end it is the registrar, and only the registrar that can fight this and put an end to it. Look at it logically here.

The domain is hosted on server A
Rightful owner of Server A is contacted and notified that said domain is spamming, leading to phishing, illegal content, whatever

Rightful owner of server A notifies client they have been notified and they must comply within x days (or hours) or be shut down

Client receives notification. Instead of complying, they move along to another provider.

Rinse, wash, repeat . Over, and over, and over again. The only TRULY effective way to stop this? Kill the domain at the registrar. This way the user can not login to their registrar and change anything.

Is that saying that I support them doing this without notification? Not at all. In fact, given their policy of not notifying customers about stuff like this, I do not support it one bit. However, it's their policy, and part (note: part) of the reason I'm transferring everything away from them.

If you look at this logically, you will see that really, there is no other solution. The ISP can only do so much, and ISPs can be changed left and right. The only other alternative is to attack the problem @ it's core, the registrar, and it'll go away (until they register a new domain). Yes, this is a last ditch effort, and should only be used as such, but , in some cases, it's the only method.

[Stan Marsh]

Originally Posted by linux-tech

Look at it logically here.

The domain is hosted on server A
Rightful owner of Server A is contacted and notified that said domain is spamming, leading to phishing, illegal content, whatever

You yourself made this clear enough. It's *server* who's spamming, *NOT* a domain. I can easily setup and 'host' yahoo.com on my server with open relay. Will this get yahoo.com blacklisted and suspended? No. And it should NOT. It will get my server's IP backlisted and (possibly) suspended. Because it's IP who's responsible for the spamming, NOT domain.

BTW, domains nowadays are 60 cents apiece. I think every spammer could afford that, if some kind of self-proclaimed internet policeman ala GoDaddy will suspend his account.

[Stan Marsh]

Originally Posted by avocado

about Moniker: is there anything in particular that makes it more secure than other registrars?

I would point you to DaveZan's blog for at least some answers: http://davezan.com/

Have a good reading!

[steveabraham]

Originally Posted by onefortruth

Go Daddy is quite secure.

You need a code just to talk to customer service..or a credit card number that's on file. They don't hand out info like candy and I'm willing to bet the transfer theft is low...their transfer feature requires much confirmation.

You have to admit, Go Daddy is secure when it comes to transfers - you can't even transfer a domain if you own it, that's what I call secure!

[twhiting9275]

You yourself made this clear enough. It's *server* who's spamming, *NOT* a domain. I can easily setup and 'host' yahoo.com on my server with open relay. Will this get yahoo.com blacklisted and suspended? No. And it should NOT. It will get my server's IP backlisted and (possibly) suspended. Because it's IP who's responsible for the spamming, NOT domain.

Correct, but, and, I did state this as well, you just chose to ignore it.

Spam is but ONE of the problems facing domains here. We also have phishing attempts, fraud , copyright violations, and a host of other goodies. Why focus on just one (easily resolvable) problem?

In the end, the registrar is responsible for ensuring that the client follows the rules and regulations of ICANN and others. In addition, the registrar is the ONLY one that can effectively suspend (turn off) a domain properly, in the event of phishing, copyright violations, whatever. As I said, this is a last resort, and should never be used unless all contact methods have been exhausted.

You have to admit, Go Daddy is secure when it comes to transfers - you can't even transfer a domain if you own it, that's what I call secure!

Yeah, a bit too secure, but that's how they want it. Personally, I don't need it, but that's just me

[avocado]

Originally Posted by Stan Marsh

I would point you to DaveZan's blog for at least some answers: http://davezan.com/

Um... as far as I can tell, the review basically just makes an unsupported claim that there's a bunch of security features he won't tell anyone about... am I missing something?