Hi Friends,

I have question about securing a important domain name at network solutions.

The domain is much critical. I have already protected it. That is the domain registrar is already locked.

Now still there are chances that somebody else in my letter pad, can submit fax authorisation in my name to network solutions, stating the loss of email access listed in the admin contact, then networksolutions can transfer it to a new account, if the whois info and the fax info matches.

I need to protect the domain, and want that this does not happen.

for that i think network solutions have a add on called Domain Private Registeration, wherein our actual whois information is hidden with them, and the details about networksolutions as a P.O. are displayed with their email address.

Now has anybody tried with the same, and can let me know whether this can stop the illegal fax authorisation to stop.

As for example if i took the domain private registeration, what about if somebody still sends the fax authorisation with my details ?

Please suggest me the best way to protect it.

Thanking you,

There are a lot of domains being stolen at netsol. I suggest you get yourself a reseller account (Enom for instance) and transfer your domain out. Don't forget to lock it afterwards of course. Besides Namecheap is a Enom reseller and also offers private registrations, so that might be an option.

There are ALWAYS chances that your valuables will be stolen, be it your car, ring or domain name. Yes, Network Solution may not be the best place to securely register a domain name, but don't even THINK that eNom (or anywhere else) will be 100% safe. Moreover, using those so-called private registration does NOT help in that respect.

Then which one do u suggest. ?

NetSol created a "primary user" who isn't necessarily shown in
WHOIS. In turn, that primary user can create 2 sets of contacts: 1
for WHOIS (who don't really have any permissions to the account)
and another for the domain's "inside account".

Those inside the account aren't shown in WHOIS unless that very
same contact is also chosen to be a WHOIS contact. If you can
assign another set of contact data strictly for WHOIS purposes,
ideally it'll "fool" potential troublemakers yet keep your primary
user contact info safe.

Thank you very very much for the info.