What is .eat?
ICANN's records put the delegation of .eat on August 30, 2014. Like most of the newer endings, it was applied for in the 2012 New gTLD Program round and its registry agreement was signed on January 23, 2014.
Charleston Road Registry Inc. operates a large portfolio of 46 TLDs, including .ads, .android, .app, .boo and .cal.
Under the hood, the root zone points to 5 name servers for .eat, every one of them reachable over IPv6. The delegation is DNSSEC-signed, so resolvers can verify that answers for .eat haven't been tampered with on the way. Registration data is published over RDAP.
Same registry, other endings
45 other TLDs share this operator.
.eat FAQ
What does .eat mean?
.eat is a generic top-level domain named for the word "eat", and it's aimed at food & drink. It doesn't belong to any country.
What is .eat used for?
.eat is mostly used for food & drink. Like most gTLDs, it's a label of intent rather than a guarantee — check the site, not just the ending.
What country is .eat?
None. .eat is a generic top-level domain, so it isn't tied to any country.
Who owns the .eat domain extension?
Charleston Road Registry Inc. operates .eat as its registry, under a registry agreement with ICANN.
When was .eat created?
.eat was delegated to the DNS root zone on August 30, 2014.
Is .eat a valid domain?
Yes. .eat is an active top-level domain in the DNS root zone, delegated in 2014, so .eat addresses work in every browser.
Can I buy a .eat domain?
.eat names are sold through ICANN-accredited registrars. Some gTLDs restrict who can register, so read Charleston Road Registry Inc.'s policy if you're unsure.
Is .eat DNSSEC-signed?
Yes, the root zone holds a DS record for .eat.
Sources
Data from IANA root zone version 2026102000. Last changed April 11, 2025. Spotted something wrong? Tell us.
