System Status
System Status

Claims Period

The following section outlines the format of the EPP Claims commands required to process applications during the Claims Period that have a prior right associated with the domain.

The Claims Period is a total of 90 consecutive days from the start of General Availability.

Domain Check Command

Domain Check Command

1. The Check command may include multiple domain names

2. The <launch:check> extension must be used

3. The attribute “type” for the <launch:check> element must be “claims”

4. The claims phase must be specified in the <launch:phase> element

  • All results are within the child elements of the <launch:chkdata> element
  • If the “exist” attribute in the response has a value of “0” it means that there is no prior claim to the name. This means that the domain name may be registered using the General Create Method outlined below
  • If the “exist” attribute in the response has a value of “1” it means that there is a prior claim to the name. This means that the domain name may not be applied for until a Claims Notice has been issued to the Applicant, and the Claims Notice acknowledged. The registrar must use the value provided in the <launch:claimKey> element to obtain a Claims Notice from the Validator as well as a Notice ID that must be used for the application of the domain.
  • The <launch:claimKey validatorID> element will contain the name of Validator from which the Claims Notice must be retrieved.

Domain Create Command

Domain Create Command

1. The <launch:create> extension must be used

2. The claims phase must be specified in the <launch:create> element

3. The domain period may be specified with a value between 1 (one) and 10 (ten) years.. If it is not, the registry will default the registration period to 1 (one) year

4. All 3 (three) associated contacts must be specified, including the Admin, Technical and Billing. An OPTIONAL Reseller contact may be specified

5. The <launch:notice> element must be used to specify the information retrieved from the Claims Notice, if a Claims Notice was issued. The Claims Notice would have been acquired using the Claims Key from the Domain Check command

6. The <launch:create> element may include the attribute “type”. Registrars that include this element must assign a value of “application”.

  • The response will contain confirmation that the domain has been created in the claims period through the <launch:phase> element
  • Applications that return a result code of “1000” will be included in the next zone publication
  • The returned UniqueApplicationID has no use
  • The registry will perform integrity checks on the provided contacts

Additional Responses

The following are additional responses from the Domain Create command.

2004: Claims Notice Errors

A response code of 2004 means that the information provided in the <launch:notice> element is incorrect. The associated messages are as follows:

1. “Notice application past expiry date ‘DATE'” means that the date provided in the <launch:notAfter> element is either incorrect or does not correspond to that specific Notice ID. Please review the <launch:notAfter> element value.

2. “Notice application before accepted ‘DATE'” means that the date provided in the <launch:acceptedDate> element is either incorrect or does not correspond to that specific Notice ID. Please review the <launch:acceptedDate> element value.

2202: Validation of notice ID failed, expecting 'X', received 'Y'

A response code of 2002 means that the notice ID provided in the <launch:noticeID> element does not coincide with the rest of the information provided in the <launch:notice> element. Please ensure that the notice ID is correctly provided in the <launch:noticeID> element and that the rest of the required 2 elements are correct in accordance to the retrieved notice ID.