Domain control after registrations?

[John]

While planning a strategy to include domain registration as an additional service, I thought of a scenario which I need help rightfully preventing and/or fighting.

How would I go about preventing fraudulent orders related domain transfers/registrations? I'd like to think that I have complete control of all the domains that I have registered through RWI but it doesn't look like I have much control once the domain is registered.

Scenario:

Customer orders a domain from us, we register it via the RWI manually or whatever and provide the customer their user/pass to manage their domain. From this point on, the only thing I can do is to lock the domain and prevent them from unlocking it from their domain manager.

Other than that, what prevents them from transferring this domain to another registrar and once completely transferred, doing a chargeback?

I think there is a 60 day window after registering a new domain where you can't transfer it elsewhere but some banks allow chargebacks for up to 90 days after the charge.

I am looking for some input or information whether or not this kind of action can be thwarted.

Thanks.

[Jeff]

As I understand it, this was a fundamental problem that EV1 too faced and was unable to overcome at the $6.49 pricepolint when selling domains individually to unknown users - hence the birth of ResellOne where they've solved it with a larger initial deposit / setup fee and more heavily validated process to signup and pay.

I think a lot of us will use resellone to provide domains as an additional service to web hosting, web design, etc., so we'll be taking in larger payments for hosting and thus our domain customers will be known/trusted customers with an ongoing payment relationship with us already.

[John]

Is there anyway for us to take ownership of a domain from RWI without having to know the user/pass required to log into the domain manager?

[Alex]

Yes, but you need to fax this contract amendment to ResellOne: http://www.resellone.net/legal/agreements/pdf/un_pass.pdf

[John]

Thanks Alex, didn't even know this amendment existed. :)

[Laurie-Resell1]

While planning a strategy to include domain registration as an additional service, I thought of a scenario which I need help rightfully preventing and/or fighting.

How would I go about preventing fraudulent orders related domain transfers/registrations? I'd like to think that I have complete control of all the domains that I have registered through RWI but it doesn't look like I have much control once the domain is registered.

Scenario:

Customer orders a domain from us, we register it via the RWI manually or whatever and provide the customer their user/pass to manage their domain. From this point on, the only thing I can do is to lock the domain and prevent them from unlocking it from their domain manager.

Other than that, what prevents them from transferring this domain to another registrar and once completely transferred, doing a chargeback?

I think there is a 60 day window after registering a new domain where you can't transfer it elsewhere but some banks allow chargebacks for up to 90 days after the charge.

I am looking for some input or information whether or not this kind of action can be thwarted.

Thanks.


If a domain is newly registered it cannot be transferred until 60 days have passed. When a domain is transferred, if it is transferred within the first 60 days to another new registrar, the EU would lose the additional year of service that was part of the initial transfer. In addition to the ammendment to the contract which will allow you access to domain login information, setting up the domains under individual profiles will allow your clients access to their domains without compromising the security of other names. If you have any further questions please email us at support@resellone.net and we will be happy to assist you. In addition there is a ton of information to be found at ICANN.

[yurtesen]

I have found this information about OpenSRS/Tucows
http://www.mail-archive.com/domains-gen@discuss.tucows.com/msg00781.html

If the domain name is not paid for then Tucows may hold/lock the name.

Essentially we ask that the reseller provide 'proof' of the non-payment
usually by way of a chargeback.
Once the chargeback information is received, Compliance will lock the name
so that the DNS does not resolve, the name cannot be transferred nor can the
whois be updated - the name is pretty much placed in a state of limbo. The
registrant is notified of this and told to contact their reseller if they
have any questions - the reseller is bcc'd.

Can resellone do the same?

Thanks,
Evren