Generic Top-Level Domain (gTLD) Registry Agreements

gTLD Registry Agreements establish the rights, duties, liabilities, and obligations ICANN requires of registry operators to run gTLDs.

Alternate Path to Delegation Report for .xyz

Eligibility for Alternate Path to Delegation

TLD "xyz" is eligible for the Alternate Path to Delegation as described in the ICANN New gTLD Collision Occurrence Management plan. [1]

Second Level Domains (SLDs)

A total of 20817 unique applicable SLDs were detected in the eight DNS-OARC "Day In The Life" ("DITL") datasets [2] collected in 2006-2013, and the 2010 DNSSEC rollout datasets; hereafter "input datasets." Pursuant to the ICANN New gTLD Collision Occurrence Management plan, if the Registry Operator chooses to block [3] all of these strings, its proposed TLD may proceed to delegation in advance of the forthcoming Collision Occurrence Assessment.

The list of SLD Strings that must be blocked is available here.

Strings appearing in the input datasets that are not valid hostnames as defined in RFC 1123 ("LDH Rule") and are not valid A-labels as defined in RFC 5890 were not included in the block list. Furthermore, the contractually required SLD "nic" will not appear in the block list.

The block list was determined as follows:
  1. List all unique strings at the SLD position in DNS requests where the applied-for string is in the TLD position in all input datasets;
  2. Filter the SLD query position as described above;
  3. Remove the "Chrome 10" strings at the leftmost query position on a best effort basis (see Methodology section below);

The remaining SLD strings comprise the block list.


Data and Source Code

DNS-OARC data was re-processed from the raw PCAP [4] files provided by participating DNS Root Server Operators as a part of the "Day In The Life," and 201