Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alexa method assigned some ICANN TLDs to wrong parties #10

Open
dnsguru opened this issue Jun 16, 2020 · 0 comments
Open

Alexa method assigned some ICANN TLDs to wrong parties #10

dnsguru opened this issue Jun 16, 2020 · 0 comments

Comments

@dnsguru
Copy link

dnsguru commented Jun 16, 2020

tl;dr: The .WEB and .SPA allocations were missed in the bootstrap development and were caught by the Alexa 100k approach, but were assigned to the wrong parties.

.WEB ended up with Verisign, but Handshake.org's assigned it as claimable by 1&1 IONOS
.SPA ended up assigning it to the Malaysian Government

From #6

Names that are already reserved:

name target (who can claim on HNS) ICANN App Issue
merck merck.com Contested/On Hold It is Complicated
spa spa.gov.my 1-1309-81322 (In PDT) Different: MY Govt?
web web.de 1-1296-36138 (In Contracting) Different: HNS 1&1 Ionos, DNS Verisign
webs webs.com 1-1033-73917 (In Contracting) Same/OK : Vistaprint

Names that are already owned on HNS by auction winners:

idn, music, xn--jlq480n2rg (.AMAZON in Chinese)

The only remaining names that could be soft-forked to prevent future auctions are:

name rollout block Application Info
hotel 45360 HOTEL Top-Level-Domain S.a.r.l
kids 26208 DotKids Foundation Limited
xn--cckwcxetd 51408 Amazon

Originally posted by @pinheadmz in #6 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant