Page History

...

Change of Registrant (aka Owner Change/COR)

Notification about changes

Typically the registrant asks its reseller to change the owner related data, if something needs to be changed. The reseller does obtain such information from the change of contractual data with the registrant, and updates the  RDDS automatically via the registar interface. In the case, the losing registrant want's to transfer the ownership of a domain to a different enitiy (gaining registrant), the process is initiated by the losing registrant itself.

Notification about changes

If RDDS of the domain is changed, the registrant will not notice the change without explicit notification by the reseller. Especially private, single domain registrants will not and can not understand the messages from a registry or registar. They consider those unknown and unexpected sources as spam. Only the well known reseller has the ability to reach the attention of the registrant. So an impersonation of the domain may be stay for a long time. Most common examples are web developers or small IT companies, who register the customer domains to themselves. How can the registry inform the registrant about an owner change effectively? May the registrant need to respond actively?

Of course, larger registrants are much more able to do their own domain managementt.b.d.

Verify of correct current data

t.b.d.ICANN requires a regular check of the accuracy of RDDS. The emails send to the registrants are designed to be accepted by not responding. Because most of them are considered as spam, the whole process is broken by design. How can the registry get in touch with the registrant in order to actively validate the accuracy of registration data regularly?

Loss of domain due to fraudulent change of ownership by the reseller

Because the registrant is often uninformed and ignorant to its own domain ownership, a fraudulent change of ownership is easily successful. Registrants will not notice the loss of their own domain as long as the typical operations are still working. Even a change of MX to intercept communication will not be noticed by the registrant but only by the operator of the mail services. How can the we raise the awareness of the registrant about domain ownership?t.b.d.

60 day lockdown period

t.b.d.If a domain is transferred or the ownership was changed, the 60-day lock is enabled to protect the registrant from fraudulent changes. We at AtLarge do not understand the thread model behind this lock clearly enough, so how should the innocent registrant understand the reasoning to slow down the process of updating a domain to a new situation. In many cases the information provided by the registrant is incomplete and erroneous, so that the reseller has to update the domain several times. The 60-day lock actively stops him from setting the correct data. What is the reasoning behind the 60-day lock and how can it be explained to the registrant?

• Survey responses and data provided by ICANN’s Global Support Center indicate that registrants do not understand the 60-day lock and express frustration when it prevents them from completing an inter-registrar transfer. (Information given in the Charter)

COR of Privacy-/proxy registrations

If a registrant uses a privacy/proxy services, they simply don't .b.d.want to be found their contact details (provided on the website anyway) publically available in the net. They do not even understand the implications of using a privacy/proxy service: Does the privacy/proxy service factually own the domain? How can a privacy/proxy service be stopped from transferring the domain to a different owner? Who is responsible in the case of such fraud?