ICANN87: What Makes a ccTLD Harder to Hand Over With a Website?

[NiceNIC_COM]

As ICANN87 wraps up in Bali, ccTLD participation includes .pt, .uk, .id, .nl, .br, .fr, .ca, .lk and .ke. The registries behind .jp, .au and .pr have also supported the ccNSO networking event as sponsors.

When a website changes hands, the domain has to follow. With a country-code extension, the new owner may need to meet eligibility requirements or supply documents before the handover can be completed.

What would you ask a registry to make easier for that situation? Clearer requirements for the incoming owner or a more predictable ownership-change process? Which extension have you dealt with?

ICANN87 ccNSO programme:

ccNSO at ICANN Public Meetings

Discover current and upcoming ccNSO sessions at ICANN public meetings, with schedules, materials, and participation details, plus access a full archive of presentations from past ccNSO meetings.

www.icann.org

 

[majorphones]

clearer requirements upfront for sure. worst part of a .au or .fr handover is finding out after payment that the buyer cant actually hold the name. a pre check the buyer could run before the deal would save a lot of escrow drama

 

[NiceNIC_COM]

clearer requirements upfront for sure. worst part of a .au or .fr handover is finding out after payment that the buyer cant actually hold the name. a pre check the buyer could run before the deal would save a lot of escrow drama

Learning the buyer isn't eligible after they've paid is a headache for both sides. A simple eligibility checklist before the deal would save a lot of trouble.