Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The gaining reseller tells the registrant to contact the losing reseller, ask for an authinfo-code, switch the domain into an transferable state: ACTIVE instead of LOCKED, and to hand over zone file data. If the losing registrar finds reasons to deny the authinfo code, the regsistrant is in a bad position. How can the registrant enforce an handover of the authinfo code, even if the reseller is unwilling or unable to help? A typical example is a reseller, which was going out of business or try to get some disputed invoices paid.

Gaining FOA

In order to start the transfer, the registrant has to formally start the process (for a paper trail), but reseller does not have access to the RDDS data and therefore can not verify this formal document (called gaining FOA). The only information, the reseller needs to know is the authinfo code, which is sufficient to start the process at the registry by the registrar (commanded by the reseller). So, can the gaining FOA be removed at all? Most registrants are not aware of the gaining FOA either.

Losing FOA

If an transfer process is started by the gaining registrar, the registry sends an losing FOA directly or via the losing registrar to the registarnt. This way the registrant could check, that the process is legitimate and started by the correct parties. Unfortunatly the losing FOA does only mention the gaining registrar, which is mostly unknown to the registrant. Can the losing FOA mention the gaining reseller, too?

Risk of lost authinfo-codes

Transfer to wrong registrar (content of losing FOA)

Change of Registrant (aka Owner Change/COR)

Notification about changes

Verify of correct current data

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

60 day lockdown period

  • 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