.eat

Launch phasesApplication API commandsExtensionsRestrictions

The launch of .eat is currently in progress.

As soon as .eat is generally available the standard commands will be shown instead.

Launch Phases

The following launch phases are currently available:

Non-refundable EAP Applications.

Please note that the fees for EAP-applications of this TLD are non-refundable.

EAT-SUNRISE AddDomainApplication

Command

Command

command         = AddDomainApplication
class           = EAT-SUNRISE
domain          = yourdomain.eat
period          = 1
ownercontact0   = (CONTACT)
admincontact0   = (CONTACT)
techcontact0    = (CONTACT)
billingcontact0 = (CONTACT)
smdfile0 = [Line 1 of your SMD file] - REQUIRED
smdfile1 = [Line 2 of your SMD file] - REQUIRED
smdfile2 = [Line 3 of your SMD file] - REQUIRED
smdfile3 = [Line 4 of your SMD file] - REQUIRED
...
trademark = [Your token(instead of smdfile), if Key-Systems is the trademark agent] - REQUIRED

Features

TMCH Enabled

Application

Start: 2026-09-01 16:00:00 UTC End: 2026-11-09 15:00:00 UTC

Launch

2026-11-09 15:00:00 UTC

EAT-EAP-DAY-1 AddDomainApplication

Command

Command

command         = AddDomainApplication
class           = EAT-EAP-DAY-1
domain          = yourdomain.eat
period          = 1
ownercontact0   = (CONTACT)
admincontact0   = (CONTACT)
techcontact0    = (CONTACT)
billingcontact0 = (CONTACT)

Features

TMCH claims period

Application

Start: 2026-09-01 16:00:00 UTC End: 2026-11-11 15:00:00 UTC

Launch

2026-11-11 15:00:00 UTC

EAT-EAP-DAY-2 AddDomainApplication

Command

Command

command         = AddDomainApplication
class           = EAT-EAP-DAY-2
domain          = yourdomain.eat
period          = 1
ownercontact0   = (CONTACT)
admincontact0   = (CONTACT)
techcontact0    = (CONTACT)
billingcontact0 = (CONTACT)

Features

TMCH claims period

Application

Start: 2026-09-01 16:00:00 UTC End: 2026-11-12 15:00:00 UTC

Launch

2026-11-12 15:00:00 UTC

EAT-EAP-DAY-3 AddDomainApplication

Command

Command

command         = AddDomainApplication
class           = EAT-EAP-DAY-3
domain          = yourdomain.eat
period          = 1
ownercontact0   = (CONTACT)
admincontact0   = (CONTACT)
techcontact0    = (CONTACT)
billingcontact0 = (CONTACT)

Features

TMCH claims period

Application

Start: 2026-09-01 16:00:00 UTC End: 2026-11-13 15:00:00 UTC

Launch

2026-11-13 15:00:00 UTC

EAT-EAP-DAY-4-5 AddDomainApplication

Command

Command

command         = AddDomainApplication
class           = EAT-EAP-DAY-4-5
domain          = yourdomain.eat
period          = 1
ownercontact0   = (CONTACT)
admincontact0   = (CONTACT)
techcontact0    = (CONTACT)
billingcontact0 = (CONTACT)

Features

TMCH claims period

Application

Start: 2026-09-01 16:00:00 UTC End: 2026-11-15 15:00:00 UTC

Launch

2026-11-15 15:00:00 UTC

EAT-EAP-DAY-6-7 AddDomainApplication

Command

Command

command         = AddDomainApplication
class           = EAT-EAP-DAY-6-7
domain          = yourdomain.eat
period          = 1
ownercontact0   = (CONTACT)
admincontact0   = (CONTACT)
techcontact0    = (CONTACT)
billingcontact0 = (CONTACT)

Features

TMCH claims period

Application

Start: 2026-09-01 16:00:00 UTC End: 2026-11-17 15:00:00 UTC

Launch

2026-11-17 15:00:00 UTC

EAT-GOLIVE AddDomainApplication

Command

Command

command         = AddDomainApplication
class           = EAT-GOLIVE
domain          = yourdomain.eat
period          = 1
ownercontact0   = (CONTACT)
admincontact0   = (CONTACT)
techcontact0    = (CONTACT)
billingcontact0 = (CONTACT)

Features

TMCH claims period

Application

Start: 2026-09-01 16:00:00 UTC End: 2026-11-17 15:00:00 UTC

Launch

2026-11-17 15:00:00 UTC

Application API Commands

AddDomainApplicationModifyDomainApplicationDeleteDomainApplicationStatusDomainApplication

Domain Registration

(API Command reference » AddDomainApplication)

Command

command         = AddDomainApplication
class           = SUNRISE|EAP-DAY-1|EAP-DAY-2|EAP-DAY-3|EAP-DAY-4-5|EAP-DAY-6-7|GOLIVE
domain          = YOURDOMAIN.eat
period          = 1
ownercontact0   = (CONTACT)
admincontact0   = (CONTACT)
techcontact0    = (CONTACT)
billingcontact0 = (CONTACT)

FOR EAT-SUNRISE:
smdfile0 = [Line 1 of your SMD file] - REQUIRED
smdfile1 = [Line 2 of your SMD file] - REQUIRED
smdfile2 = [Line 3 of your SMD file] - REQUIRED
smdfile3 = [Line 4 of your SMD file] - REQUIRED
...
trademark = [Your token(instead of smdfile), if Key-Systems is the trademark agent] - REQUIRED

Domain Modification

(API Command reference » ModifyDomainApplication)

Command

command     = ModifyDomainApplication
application = INT
class       = Change GTLD-PREORDER to desired launch phase CLASS
pay         = 1        - REQUIRED

Domain Deletion

(API Command reference » DeleteDomainApplication)

Command

command     = DeleteDomainApplication
domain = YOURDOMAIN.eat
class = (TEXT)
application = (INT)

Domain Status

(API Command reference » StatusDomainApplication)

Command

command     = StatusDomainApplication
application = (INT)

Domain Extensions

X-ACCEPT-SSL-REQUIREMENT	1 Confirmation that the process required for the registration is implemented on the reseller side and the respective options are presented to the registrant prior to the registration.

Domain Restrictions

Registrars must provide notification to alert prospective registrants to the requirement of HTTPS on .eat names in order for domains to work in web browsers. This notification must be clearly and conspicuously disclosed as part of the registration flow prior to purchase. It must be distinct and not embedded in other terms of service, nor require the registrant to follow a link to obtain the information.

The following information must be included as part of the notice to all registrants:

• That .eat is a secure namespace;
• The requirement to configure HTTPS serving so that browsers can load .eat websites; and
• Resources about configuring HTTPS and obtaining an SSL certificate
  • Information may be linked as part of an external or internal website or window, and
  • Registrars may provide their own information about configuring HTTPS browsing or link to third party resources

Any registrant of a letter/letter two-character ASCII label represents that it will take steps to ensure against misrepresenting or falsely implying that the registrant or its business is affiliated with a government or country-code manager if such affiliation, sponsorship or endorsement does not exist.

Any registrant of a name on the list of IOC, Red Cross, and IGO reserved names for new gTLDs represents that the registration is on behalf of the respective organization.