Um, yeah, right. (I'm not giving you my registrar login and password!)

[draggar]

One person I did two web sites for is going to professional service. They are asking me for my login and password to "the page where I bought the domain".

Um, yeah, right. That is NOT going to happen. I can send them the authorization codes, I can point the DNS to a place where they'd like but there is no way they are going to get my login and password.

Honestly, do web developers really ask for this kind of information? Personally I think it is extremely fishy.

 

[DomainMagnate]

I usually give my developers passwords to the hosting, but why would they need access to domains

 

[south]

Ask the domain owner to create an account at the registrar, then push the name to the account.

 

[Sonny Banks]

Don't give your login details...never.

 

[draggar]

Ask the domain owner to create an account at the registrar, then push the name to the account.

Thay was my suggestion to the person. I would point the DNS to where they want it then push the domains to her account. I highly recommended her not send the domains to them since people like this usually (way) overcharge for registration and she would still have control over the domains (they cannot "hold them hostage"). It could be a big legal mess.

Don't give your login details...never.

Aww, but I want to! :smilewinkgrin: :smilewinkgrin: I've offered (other than above):
- Pointing the DNS to where they want it
- Giving them FTP access to the folders where the sites are currently hosted

I even offered the authorization code, as a last resort, but I highly recommended against that.

 

[south]

Thay was my suggestion to the person. I would point the DNS to where they want it then push the domains to her account. I highly recommended her not send the domains to them since people like this usually (way) overcharge for registration and she would still have control over the domains (they cannot "hold them hostage"). It could be a big legal mess.

Ask the person that OWNS the name, do not give it to anyone else, unless directed to by the owner of the name.

Do not make the push an option. It's their name. You were kind enough to grab it for them, now it's time for them to take ownership. What if you dropped dead, or someone hacked your account, etc? You or your estate would be responsible. Absolve yourself of the responsibility.

 

[draggar]

Ask the person that OWNS the name, do not give it to anyone else, unless directed to by the owner of the name.

Do not make the push an option. It's their name. You were kind enough to grab it for them, now it's time for them to take ownership. What if you dropped dead, or someone hacked your account, etc? You or your estate would be responsible. Absolve yourself of the responsibility.

Technically, I "own" the domain, I registered it for her (perfect fit for her needs) but there is the agreement that if she wanted it, I would push it to an account for her.

She, like many of my clients, are just very new and don't know much about domains and what they truly mean.

 

[Sonny Banks]

I use a reseller account so I open a client account and push the domain there.

 

[south]

Technically, I "own" the domain, I registered it for her (perfect fit for her needs) but there is the agreement that if she wanted it, I would push it to an account for her.

She, like many of my clients, are just very new and don't know much about domains and what they truly mean.

True, most people do not have a clue. However, you need to decide if you want to retain ownership or abide by your agreement with her. If she is a regular client in other areas, or just wants to do hosting with you, I'd push the name to her. Hosting is much easier money then developing. And favors don't pay the bills.

 

[draggar]

True, most people do not have a clue. However, you need to decide if you want to retain ownership or abide by your agreement with her. If she is a regular client in other areas, or just wants to do hosting with you, I'd push the name to her. Hosting is much easier money then developing. And favors don't pay the bills.

She is a member of my wife's dog training club (how she got to know me), so nothing really "professional". I would prefer if she had ownership of the domain so I don't have to think about them (and bug her for renewal costs) but I don't want her to get screwed like other people I've known.

 

[jdk]

edit below

 

[draggar]

If you are transferring the domain to her, make sure you have a contract so you can get the domain back at any time you wish. I handle clients domains who I host and when requested the domains are transferred back to a registrar of their choice, or kept at the current one. At no time is a domain kept that is not mine.

I have no interest in the domains other than her websites, I got them for her to develop into sites for her (I got both for reg fee). I made it quite clear that they were her domains and I would transfer them to an account for her if she ever wished (not uncommon with my clients).

I just don't want her to get screwed so I want her to fully understand what the potential is if she does give the domains to someone else.

 

[jdk]

Oops nevermind - just woke up and read your initial post wrong

 

[loredan]

Why don't you just set up another account at your registrar in your client name, push the domain and give her the details of the account?

 

[draggar]

They got my email address (either though WhoIs or the client) saying that they need my login and password to the registrar, again.

Um, no, again.

Luckily they includes the nameservers so I did change those and let the client that the sites that I made and the email addresses will no longer work until it is set up with the new company.

I also recommended to her, again, to set up an account w/ GoDaddy so i can push the domains to her.